Creating a Microsoft Teams Manifest

Once the .env file is completely configured, a bot manifest can be created. This is the file users will use to install the bot into their local Microsoft Teams environments.

To create a manifest, use the private POST endpoint, which is provided with the service code, to generate the manifest. This endpoint requires information from the .env file as input. When executed, the endpoint generates a manifest zip file in the <BOT_HOME> location.

The response also includes the contents of the manifest.json file (as included in manifest zip file).

https://<private IP>:<private port>/util/manifest

Input: {"tenant_id" : "xxxxxxxx", "app_id" : "yyyyyyy"}

Output: {"status" : "success", "manifest" : {……}}

After a successful post to the manifest endpoint, a zip file named identityiqbot-<version>-manifest.zip.is created in <BOT_HOME>.

The manifest zip file contains the manifest.json file, as well as some configuration options such as color and outline logos.

Once the manifest is generated, it doesn't need to be generated again unless there are changes to the bot configuration in the .env file – for example, due to Azure portal changes.

If there is trouble generating a manifest, verify the tenant_id and app_id are correct.

For more information on the service code, see Installing and Configuring the IdentityIQ Service Code.