Forum Discussion
Consent popup
Hello Denys-Fokin,
This consent popup appears to be related to Azure AD app registration consent flow, not a bug. The consent popup is expected behavior for multi-tenant apps without proper configuration.
Looking at your manifest, Missing webApplicationInfo in manifest, so Teams can't identify your Azure AD app properly.Add webApplicationInfo in your manifest and declare minimal permissions:
{ // ...existing code... "webApplicationInfo": { "id": "526ebd72-4b57-4c34-b84f-7fb03b6ddeb6", "resource": "api://tatamf.stg.skillscaravan.com/526ebd72-4b57-4c34-b84f-7fb03b6ddeb6" }, "permissions": [ "identity", "messageTeamMembers" ], // ...existing code... }
MicrosoftHello Denys-Fokin,
This consent popup appears to be related to Azure AD app registration consent flow, not a bug. The consent popup is expected behavior for multi-tenant apps without proper configuration.
Looking at your manifest, Missing webApplicationInfo in manifest, so Teams can't identify your Azure AD app properly.
Add webApplicationInfo in your manifest and declare minimal permissions:
{ // ...existing code...
"webApplicationInfo": {
"id": "526ebd72-4b57-4c34-b84f-7fb03b6ddeb6",
"resource": "api://tatamf.stg.skillscaravan.com/526ebd72-4b57-4c34-b84f-7fb03b6ddeb6"
},
"permissions": [
"identity",
"messageTeamMembers"
],
// ...existing code...
}
MicrosoftHello Denys-Fokin,
Glad to hear that your issue is resolved!!
We would appreciate it if you could share your valuable feedback via the Microsoft Teams Developer Community Response Feedback link?
Sorry to revive this, but it seems the issue is not gone, and now appearing again after a while, could you please specify, should we configure bot App Registration somehow? The app does not use SSO.
Also, is the "resource" needed here, if App Registration Expose URI is not configured? Because documentation at https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema says that "resource" is for:Resource URL of app for acquiring auth token for SSO.
NOTE: If you aren't using SSO, ensure that you enter a dummy string value in this field to your app manifest, for example, https://example to avoid an error response. The dummy URL string value mustn't contain domains or URLs that aren't in your control, either directly or through wildcards. For example, yourapp.onmicrosoft.com is valid, but *.onmicrosoft.com isn't valid. The top-level domains are prohibited, for example, *.com, *.org.
