[Doc Improvement][Feedback avenue fixes][4516128]

msteams-platform/TOC.yml

@@ -191,6 +191,8 @@
           displayName: application, endpoint
         - name: Add SSO to Teams app
           href: toolkit/add-single-sign-on.md
+        - name: Enable SSO for Teams app
+          href: toolkit/develop-single-sign-on-experience-in-teams.md
         - name: Use Microsoft Entra app in TeamsFx
           href: toolkit/use-existing-aad-app.md
         - name: Use certificate or MSI for app authentication

msteams-platform/bots/how-to/authentication/bot-sso-register-aad.md

@@ -276,6 +276,9 @@ The scope and permissions are now configured. Next, you must configure the autho
     >
     > * The Microsoft 365 client IDs for mobile, desktop, and web applications for Teams, Microsoft 365 app, and Outlook are the actual IDs that you must add.
     > * If your app has a tab app, you'll need either web or SPA, as you can't have a mobile or desktop client application in Teams.
+    > * While it's recommended to use same App ID, you can use a different App Registration ID in the webApplicationInfo section of your Teams app manifest that's not same as the Azure bot App ID. This is a valid and supported configuration.
+    >    * The `botId` in the bots section refers to the Azure Bot registration used for messaging and interaction.
+    >    * The `webApplicationInfo.id` refers to the Microsoft Entra App Registration used for authentication such as SSO, token acquisition, Graph API access.
 
 1. Select one of the following client IDs:
 
@@ -660,6 +663,9 @@ The scope and permissions are now configured. Next, you must configure the autho
     >
     > * The Microsoft 365 client IDs for mobile, desktop, and web applications for Teams, Microsoft 365 app, and Outlook are the actual IDs that you must add.
     > * If your app has a tab app, you'll need either web or SPA, as you can't have a mobile or desktop client application in Teams.
+    > * While it's recommended to use same App ID, you can use a different App Registration ID in the webApplicationInfo section of your Teams app manifest that's not same as the Azure bot App ID. This is a valid and supported configuration.
+    >    * The `botId` in the bots section refers to the Azure Bot registration used for messaging and interaction.
+    >    * The `webApplicationInfo.id` refers to the Microsoft Entra App Registration used for authentication such as SSO, token acquisition, Graph API access.
 
 1. Select one of the following client IDs:
 

msteams-platform/toolkit/develop-single-sign-on-experience-in-Teams.md

@@ -471,7 +471,7 @@ To include additional API permissions to access your desired APIs, see [edit Mic
 
 To view your Microsoft Entra app in Azure portal, see [edit Microsoft Entra manifest](AAD-manifest-customization.md).
 
-## Next step
+## See also
 
-> [!div class="nextstepaction"]
-> [Add single sign-on to Teams app](add-single-sign-on.md)
+* [Enable SSO for tab app](../tabs/how-to/authentication/tab-sso-overview.md)
+* [Enable SSO for your bot and message extension](../bots/how-to/authentication/bot-sso-overview.md)