How to Download and Modify Your Manifest JSON File

1. Download and Extract the ZIP File

1. Click on this link to download the Zip file.

2. Extract the contents of the ZIP file. You will find three files inside

3. Download the manifest.json file from your Sendent for MS Teams hosted solution. For example: https://msteams.sendent.dev/manifest.json.

4. Replace the manifest.json file from the extracted ZIP and overwrite it with your downloaded manifest.json file from your hosted solution.

Please make sure that your ZIP file only contains the 3 files. That means that no folder can be present nor it can be encapsulated in a folder.

✅ Correct situation ZIP contents:

icon-color.png
icon-outline.png
manifest.json

❌ Wrong situation ZIP contents:

Folder XXX
   |--- icon-color.png
   |--- icon-outline.png
   |--- manifest.json

Alternatively

1. Open the manifest.json from the ZIP file in a text editor.

2. Replace every occurrence of <MS_BOT_ID> with the Microsoft App ID of your Azure Bot. Please refer to this article for more details on how you can obtain this ID.

It appears in five places: id, the botId under bots, the botId under composeExtensions, the id under webApplicationInfo, and inside the resource value under webApplicationInfo. Your editor's Find & Replace can replace them all at once.

3. Replace <HOST> in the resource value under webApplicationInfo with your MS Teams hosting domain, without the protocol.

For instance, if your domain for MS Teams is https://teams-installation.example.com, the value becomes api://teams-installation.example.com/<your App ID>.

4. Under staticTabs, replace <BASE_URL> in contentUrl and websiteUrl with the full address of your MS Teams hosting, including https and without a trailing slash. For instance: https://teams-installation.example.com/index.html?page=explorer .

5. Scroll towards the bottom of the file to the section named validDomains. Replace <BASE_URL> there with your domain only, without the protocol. For instance: teams-installation.example.com.

If you used Find & Replace for <BASE_URL>, remove the https:// from this entry afterwards.

Once edited, those parts of your manifest.json should look like this (other fields left out):

{
    "version": "3.0.0",
    "id": "11111111-2222-3333-4444-555555555555",
    ...
    "bots": [
        {
            "botId": "11111111-2222-3333-4444-555555555555",
            ...
        }
    ],
    "composeExtensions": [
        {
            "botId": "11111111-2222-3333-4444-555555555555",
            ...
        }
    ],
    "staticTabs": [
        {
            ...
            "contentUrl": "https://teams-installation.example.com/index.html?page=explorer",
            "websiteUrl": "https://teams-installation.example.com/index.html?page=explorer",
            ...
        }
    ],
    "validDomains": ["teams-installation.example.com"],
    "webApplicationInfo": {
        "id": "11111111-2222-3333-4444-555555555555",
        "resource": "api://teams-installation.example.com/11111111-2222-3333-4444-555555555555"
    }
}

6. Leave the version as it is. If you are updating an existing installation, the version must be higher than the one currently installed, otherwise Teams won't accept the update.

7. Save and close the manifest.json file.

2. Create a New ZIP File

Create a new ZIP file containing the two icons and the updated manifest.json file.

Ensure that these files are at the root level of the ZIP file, without any directories.

Please note that the actual file name of the ZIP file does not matter.

By following these steps, you will have a properly configured manifest ready for deployment with your Microsoft Bot Service on MS Teams. Please refer to this guide on how you can proceed with the deployment of the Sendent Add-in for Teams.