we tested the installation process of our app Tweelin in a new organization and were able to find an issue that the call is not working. Except for the calling feature, we were able to use all other features of the app. Here are some steps we performed to debug: Checked the console log of the Bot that says internal server error due to lack of permissions. A log can be found here in paste bin and screenshot . We compared the permission of both apps. a. Tweelin app for Teams, b. Tweelin-aad: which is getting reflected on a new org after installation. The installation process is followed the same as provided in the Tweelin installation doc. The app was reflected in the Teams app. We installed Tweelin and created a wish then the call failed. We compared the latest manifest.dev.zip data with the one we submitted 5 months back. After going through the process, taking notes, and analyzing each parameter involved, here are our findings In the local development, we tested the credentials and ID involved. Tweelin app for teams on Tweelin Azure and App package > manifest.json . In this case, the app id of the Tweelin app for Teams matches with the bot id in the manifest. On installation in the new org, earlier when we created our first submission it used to create 2 apps in customer's organization Azure > Enterprise Apps. Screenshot of what we used to see. But now when we install it in an organization we can find only one app entry in the Enterprise App list. Current screenshot from other org Enterprise app list. On comparing both of them, there is a mismatch in ID and other parameters involved, and our app "Tweelin app for teams" that is attested with our MPIN Id is not reflected. We even tried with the manifest that we submitted 6 months back as our first submission for publishing but the situation remains the same. Our analysis raises 2 possibilities, Some things got changed in the publishing process during migration from Bot framework versions 4 to 5 (from the Microsoft side ) because of which we are not seeing the same flow even on having the old manifest. A possibility is that we now need only 1 app instead of 2 (Bot and Tab aad). There might be some issues in ID mismatch or manifest configuration update and our primary " manifest.json " is not reflecting there. Our app details (not even name), privacy policy, or logo are not getting reflected correctly in the Enterprise Apps list of Target organization. We would need help from Microsoft dev who can verify the issue. Why do we even bother about these things? The reason is that all permission for calls and other management stuff is given to the "Tweelin app for teams" and our bot uses the same credentials and permissions. If this app is not getting added to the Target /customer organization then permission to bot is not granted. Due to this bot will not be able to perform graph api related tasks. We can say that our bot is not getting installed properly because if it did, an app with the correct name, logo, website, and other parameters would have been created. A reference to this is attached in the screenshots above. We tried to find documentation/solutions to this but nothing worked for us. We request you to provide us clarification/resources about the current workflow of each step or if there is a known issue, please share some info with us and let us know the expected time to get it fixed.

App is not getting installed properly on other organization, what is the correct way to build with correct manifest configuration in Bot framework version 5?

SANDEEP KUMAR 25

we tested the installation process of our app Tweelin in a new organization and were able to find an issue that the call is not working. Except for the calling feature, we were able to use all other features of the app.

Here are some steps we performed to debug:

Checked the console log of the Bot that says internal server error due to lack of permissions. A log can be found here in paste bin and screenshot.
We compared the permission of both apps. a. Tweelin app for Teams, b. Tweelin-aad: which is getting reflected on a new org after installation. The installation process is followed the same as provided in the Tweelin installation doc.
The app was reflected in the Teams app. We installed Tweelin and created a wish then the call failed.
We compared the latest manifest.dev.zip data with the one we submitted 5 months back.

After going through the process, taking notes, and analyzing each parameter involved, here are our findings

In the local development, we tested the credentials and ID involved. Tweelin app for teams on Tweelin Azure and App package > manifest.json. In this case, the app id of the Tweelin app for Teams matches with the bot id in the manifest.
On installation in the new org, earlier when we created our first submission it used to create 2 apps in customer's organization Azure > Enterprise Apps. Screenshot of what we used to see. But now when we install it in an organization we can find only one app entry in the Enterprise App list. Current screenshot from other org Enterprise app list.
On comparing both of them, there is a mismatch in ID and other parameters involved, and our app "Tweelin app for teams" that is attested with our MPIN Id is not reflected. We even tried with the manifest that we submitted 6 months back as our first submission for publishing but the situation remains the same.
Our analysis raises 2 possibilities,
1. Some things got changed in the publishing process during migration from Bot framework versions 4 to 5 (from the Microsoft side ) because of which we are not seeing the same flow even on having the old manifest. A possibility is that we now need only 1 app instead of 2 (Bot and Tab aad).
2. There might be some issues in ID mismatch or manifest configuration update and our primary "manifest.json" is not reflecting there. Our app details (not even name), privacy policy, or logo are not getting reflected correctly in the Enterprise Apps list of Target organization. We would need help from Microsoft dev who can verify the issue. Why do we even bother about these things? The reason is that all permission for calls and other management stuff is given to the "Tweelin app for teams" and our bot uses the same credentials and permissions. If this app is not getting added to the Target /customer organization then permission to bot is not granted. Due to this bot will not be able to perform graph api related tasks. We can say that our bot is not getting installed properly because if it did, an app with the correct name, logo, website, and other parameters would have been created. A reference to this is attached in the screenshots above. We tried to find documentation/solutions to this but nothing worked for us. We request you to provide us clarification/resources about the current workflow of each step or if there is a known issue, please share some info with us and let us know the expected time to get it fixed.

ChetanSharmamsft 1,031 Reputation points Microsoft Vendor

2023-10-12T04:51:29.1966667+00:00

Thanks for raising your query.
We will investigate your query and let you know.
Sayali-MSFT 3,141 Reputation points Microsoft Vendor

2023-10-13T11:22:12.6866667+00:00

@SANDEEP KUMAR- It seems like, this exception is caused by the token acquired using the client credentials flow. In this flow, there is no context for Me.

To fix this issue, you need to provide the delegate-token.
The delegate-token is need to users interactive to enter their username and password. For example, we can use the **Authorization Code Grant flow ** to get the delegate-token( refer here for this flow).
SANDEEP KUMAR 25 Reputation points

2023-10-30T15:22:25.32+00:00
Hi @Sayali-MSFT ,

We have gone through your solution but is not exactly relevant to our problem.
https://learn.microsoft.com/en-us/graph/api/application-post-calls?view=graph-rest-1.0&tabs=http
Please refer this document that explains how we can create a call and it clearly states in the permission section that we cannot create call using delegated permission.

Creation of a call in a way that our application (where a Bot can call user and create group calls) aims need Application based permission.

Moreover our main issue is that when we install /deploy an app or sideload it, we do not see the aad.manifest.json for the bot app even if we create a new app from scratch.

@ChetanSharmamsft to regenerate the issue, you can follow the steps listed below:

Create an Bot from Teams Toolkit in VS Code

Try provisioning the app, it will create the local and dev ".env" parameters.

Find creds for the dev environment and copy the app id from the list of env parameters.

Go to azure entra id and navigate to App registrations, in the section of all apps find the app id you have using search input.

Open the app and in the api permission, grant permissions to calling and cross tenant profile sharing.

Grant admin consent for the app to successfully use those permissions.

Without any changes in local code, zip the bot to be deployed / sideloaded in other org using the option of .

In teams admin center> Teams App > Manage apps > upload new app, upload the manifest created.

After uploading navigate to the app details page of the same app

Inside it we expect the Org wide permissions, but in the current we have that specific option blank.

Questions:

How will the admin of XYZ org can grant permissions to the app if the button/ option is not available?

Why the app is not listed in Enterprise application list of XYZ org?

In our research we found that the bot doesn't have the aad.manifest.json, is it a intentional configuration or a bug?

If all app (including standalone BOT ) needs aad.manifest.json, how can we add it?

Our app contains bot and tab together, what is the correct and official way to integrate?
Sayali-MSFT 3,141 Reputation points Microsoft Vendor

2023-11-02T13:18:39.7533333+00:00

Hello @SANDEEP KUMAR--Thanks for providing the information. We will check this with internally and let you know the update once we have any.
Sayali-MSFT 3,141 Reputation points Microsoft Vendor

2023-11-29T10:02:00.7033333+00:00
How will the admin of XYZ org can grant permissions to the app if the button/ option is not available?

If the option to grant permissions is not available, it could be due to insufficient privileges. You need to ensure that the user has the necessary permissions to grant consent. If the user is not an admin, they may not have the necessary permissions to grant consent for the app. You can refer to the Azure AD documentation for more information on how to grant permissions.

Why the app is not listed in Enterprise application list of XYZ org?

If the app is not listed in the Enterprise application list, it could be because the app has not been registered in the Azure AD of the XYZ organization. You need to ensure that the app is registered in the Azure AD of the organization where you want it to be listed.

In our research we found that the bot doesn't have the aad.manifest.json, is it a intentional configuration or a bug?

The aad.manifest.json file is automatically created when you create a project with Teams Toolkit that comes with single sign-on (SSO) support. If your bot doesn't have this file, it could be because the bot was created without built-in SSO. You can add SSO to your bot using Teams Toolkit, which will create the aad.manifest.json file.

If all app (including standalone BOT ) needs aad.manifest.json, how can we add it?

You can add the aad.manifest.json file to your bot by adding SSO to your bot using Teams Toolkit. Teams Toolkit will automatically create the aad.manifest.json file when you add SSO to your bot.

Our app contains bot and tab together, what is the correct and official way to integrate?

If your app contains both a bot and a tab, you can integrate them using Teams Toolkit. You can create a project with Teams Toolkit that includes both a bot and a tab. Teams Toolkit will automatically create or update the Azure AD application during local development or while you move the application to the cloud. You can refer to the Teams Toolkit documentation for more information on how to integrate a bot and a tab in a Teams app.

Share via

App is not getting installed properly on other organization, what is the correct way to build with correct manifest configuration in Bot framework version 5?

Your answer