[Dev-Docs AI Improvement]: Enable SSO for Adaptive Cards Universal Actions in your bot #13663
Conversation
…s-for-adaptive-cards/enable-sso-for-your-adaptive-cards-universal-action.md by yashy797
Acrolinx ScorecardsWe currently enforce a minimum score of 80. Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:
More info about Acrolinx Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 45f9f15:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/enable-sso-for-your-adaptive-cards-universal-action.md | View | Details |
msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/enable-sso-for-your-adaptive-cards-universal-action.md
- Line 1, Column 1: [Warning: title-missing - See documentation]
Missing required attribute: 'title'. Add a title string to show in search engine results. - Line 1, Column 1: [Warning: ms-topic-missing - See documentation]
Missing required attribute: 'ms.topic'. - Line 20, Column 1: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/microsoftteams/platform/assets/images/authentication/sso-runtime-seqd-adaptivecard.png' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 1, Column 1: [Suggestion: ms-date-missing - See documentation]
Missing required attribute: 'ms.date'. - Line 1, Column 1: [Suggestion: description-missing - See documentation]
Missing required attribute: 'description'. - Line 20, Column 1: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/microsoftteams/platform/assets/images/authentication/sso-runtime-seqd-adaptivecard.png' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
| # Enable SSO for Adaptive Cards Universal Actions in your bot | ||
|
|
||
| With Single sign-on (SSO) in Teams, app users have the advantage of using Teams to access Adaptive Cards Universal Actions in a bot. After logging in to Teams using Microsoft or Microsoft 365 account, app users can use your app without the need to sign in again. Your app is available to app users on any device with access granted through Microsoft Entra ID. | ||
| With Single sign-on (SSO) in Teams, app users use Teams to access Adaptive Cards Universal Actions in a bot. After logging in to Teams using Microsoft or Microsoft 365 account, app users can use your app without needing to sign in again. Your app is available to app users on any device with access granted through Microsoft Entra ID. |
There was a problem hiding this comment.
The phrasing “have the advantage of using” is more aligned with the Microsoft Writing Style Guide’s preference for natural, user-focused language.
“Without the need to sign in again” aligns with the “use plain language” guidance in the Writing Style Guide.
Please retain original version
|
|
||
| ## Next step | ||
|
|
||
| > [!div class="nextstepaction"] |
There was a problem hiding this comment.
We will need this to be retained for the developers to click next step. Please do not delete.
| The following image shows how SSO works when a Teams app user attempts to access the Adaptive Cards Universal Actions in a bot: | ||
|
|
||
| :::image type="content" source="../../../assets/images/authentication/sso-runtime-seqd-adaptivecard.png" alt-text="Screenshot shows SSO flow for Adaptive Cards Universal Actions in a bot." lightbox="../../../assets/images/authentication/sso-runtime-seqd-adaptivecard.png"::: | ||
|  |
There was a problem hiding this comment.
Dont remove the path. As part of the Acrolinx, you cant use en-us website, so we include path as shown in the original content
| | 1 | Teams client → Bot service | Teams sends an invoke `Action.Execute` request to the bot. <br> If the app user has previously signed in, a token is saved in the Bot Framework Token Store. The bot calls the Bot Framework Token Service that checks for an existing token for the app user in the Bot Framework Token Store. <br> • If the token exists, the app user is given access. <br> • If the token isn't available, the bot triggers the auth flow. | | ||
| | 2 | Microsoft Entra ID → Teams client | For the app user who's using the Adaptive Cards Universal Actions in a bot for the first time, the token exchange can occur only after the app user gives the consent. Teams client displays a message to the app user for giving consent. <br> In case the consent fails: <br> 1. The authentication falls back to the sign-in prompt and the app user must sign in to use the bot app. The sign-in button appears in Teams client and when the app user selects it, the Microsoft Entra sign-in page appears. <br> 2. The app user signs in and grants access to the Bot service. | | ||
| | 1 | Teams client → Bot service | Teams sends an invoke `Action.Execute` request to the bot. <br> If the app user has previously signed in, a token is saved in Bot Framework Token Store. The bot calls Bot Framework Token Service that checks for an existing token for the app user in Bot Framework Token Store. <br> • If the token exists, the app user is given access. <br> • If the token isn't available, the bot triggers the auth flow. | | ||
| | 2 | Microsoft Entra ID → Teams client | For the app user who's using Adaptive Cards Universal Actions in a bot for the first time, the token exchange can occur only after the app user gives consent. Teams client displays a message to the app user for giving consent. <br> In case the consent fails: <br> 1. The authentication falls back to the sign-in prompt and the app user must sign in to use the bot app. The sign-in button appears in Teams client and when the app user selects it, the Microsoft Entra sign-in page appears. <br> 2. The app user signs in and grants access to Bot service. | |
There was a problem hiding this comment.
Retain The app user signs in and grants access to the Bot service.
This reads more natural, aligns with Microsoft’s preference for clarity and consistency, and treats “Bot service” as the specific service the user is granting access to.
| @@ -1,24 +1,14 @@ | |||
| --- | |||
There was a problem hiding this comment.
Do not delete these. These are mandatory elements of the article.
This PR updates the content of the file: msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/enable-sso-for-your-adaptive-cards-universal-action.md.
Submitted by: @yashy797