MicrosoftDocs / msteams-docs

Source for the Microsoft Teams developer platform documentation.
https://aka.ms/teamsdev
Creative Commons Attribution 4.0 International
287 stars 509 forks source link

Reason for Application ID in Web Resource #11421

Open Wajeed-msft opened 3 months ago

Wajeed-msft commented 3 months ago

Discussed in https://github.com/MicrosoftDocs/msteams-docs/discussions/7008

Originally posted by **AFK-Python** September 21, 2022 Is there a reason why the following is recommended on this [doc page](https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/tab-sso-manifest)? Specifically including the Azure AD AppId in this line: `"resource": "api://{Subdomain}.example.com/{Azure AD AppId}"`. ``` "webApplicationInfo": { "id": "{Azure AD AppId}", "resource": "api://{Subdomain}.example.com/{Azure AD AppId}" } ``` It seems a bit redundant to me and this is causing self reference/cyclical definition problems while I am attempting to use Pulumi/Terraform. Furthermore, in my testing without it, everything in my application seems to be working fine. Would greatly appreciate an explanation for this standard.
Meghana-MSFT commented 3 months ago

@AFK-Python - The doc has been updated after this issue was raised on September 21, 2022. Could you please let us know if you still have any queries?

AFK-Python commented 3 months ago

@Meghana-MSFT

The update still does not answer my original question. The update only renamed the variable, there is still no explanation as to why that standard exists, especially when it causes issues in automation. Two years for an answer to this, and still no explanation or example addressing the automation issue I raised.

We were able to figure out our own solution, but the docs should really be updated to explain why the standard exists and how to use tools like Terraform with that resource (b/c the standard causes problems).

Meghana-MSFT commented 3 months ago

@AFK-Python - We are checking this internally; we will get back to you.

Meghana-MSFT commented 3 months ago

Could you please let us know what issue are you facing with automation?

Please know that the Azure AD AppId does not need to be part of the app's URLs. When it comes to the URLs we embed in Teams, we only require that the domain matches.