Improved quality of articles about Bot Powered ACEs and updated TOC

Author: PaoloPia

docs/spfx/viva/bot-powered/AuthN-and-AuthZ-in-Bot-Powered-ACEs-Entra.md

@@ -22,7 +22,7 @@ Following picture you can see how the Adaptive Card Extension looks like in the
 From a developer point of view, you build the ACE once and you benefit of it in both desktop and mobile experiences.
 The whole source code of the .NET sample is available in the following GitHub repository: [Welcome User Bot Powered ACE SSO](https://github.com/pnp/viva-dev-bot-powered-aces/tree/main/samples/dotnet/WelcomeUserBotPoweredAce-SSO).
 
-## Developing a Secured Bot Powered ACE with Microsoft .NET
+## Developing a Secured Bot Powered ACE with Microsoft .NET and Microsoft Entra ID SSO
 
 First of all, you should create a Bot Powered ACE following the guidance provided in article ["Building your first Bot Powered Adaptive Card Extension,"](./Building-Your-First-Bot-Powered-ACE.md) stopping before the section ["Implement the actual Bot Powered ACE."](./Building-Your-First-Bot-Powered-ACE.md#implement-the-actual-bot-powered-ace)
 For the sake of simplicity, assume that the Bot Powered ACE project name is "WelcomeUserBotPoweredAce" and register the Azure Bot accordingly to the guidance. 
@@ -506,8 +506,8 @@ To properly support authentication, you need to add a `webApplicationInfo` secti
 
 The `id` property is the actual Client ID of the Microsoft App behind the scenes of your Azure Bot. The `resource` property is the unique URI that you configured for that Microsoft App.
 
-You're now ready to package the solution, deploy it on the SharePoint Online App Catalog, and play with it. You can follow the instructions provided in section ["Run and test the solution"](./Building-Your-First-Bot-Powered-ACE.md#run-and-test-the-solution) of the reference article ["Building your first Bot Powered Adaptive Card Extension."](./Building-Your-First-Bot-Powered-ACE.md)
-
 Now, consider a Bot Powered ACE configured for multitenant and deployed on a target tenant. The first time users run it, they need to grant consent to your Azure Bot application to access Microsoft Graph with delegated permissions. The user's consent is collected through a custom dialog provided by Microsoft Entra ID. In the following picture, you can see the user's consent dialog in action.
 
 ![The popup dialog of Microsoft Entra ID to collect the user's consent to access specific resources based on the current Azure Bot application permissions.](./images/Bot-Powered-ACE-Secured-Consent-Multitenant.png)
+
+You're now ready to package the solution, deploy it on the SharePoint Online App Catalog, and play with it. You can follow the instructions provided in section ["Run and test the solution"](./Building-Your-First-Bot-Powered-ACE.md#run-and-test-the-solution) of the reference article ["Building your first Bot Powered Adaptive Card Extension."](./Building-Your-First-Bot-Powered-ACE.md)

docs/spfx/viva/bot-powered/AuthN-and-AuthZ-in-Bot-Powered-ACEs-Magic-Code.md

@@ -31,7 +31,7 @@ In both scenarios (desktop and mobile), there are:
 From a developer point of view, you build the ACE once and you benefit of it in both desktop and mobile experiences.
 The whole source code of the .NET sample is available in the following GitHub repository: [Welcome User Bot Powered ACE](https://github.com/pnp/viva-dev-bot-powered-aces/tree/main/samples/dotnet/WelcomeUserBotPoweredAce).
 
-## Developing a Secured Bot Powered ACE with Microsoft .NET
+## Developing a Secured Bot Powered ACE with Microsoft .NET and Magic Code
 
 First of all, you should create a Bot Powered ACE following the guidance provided in article ["Building your first Bot Powered Adaptive Card Extension,"](./Building-Your-First-Bot-Powered-ACE.md) stopping before the section ["Implement the actual Bot Powered ACE."](./Building-Your-First-Bot-Powered-ACE.md#implement-the-actual-bot-powered-ace)
 For the sake of simplicity, assume that the Bot Powered ACE project name is "WelcomeUserBotPoweredAce" and register the Azure Bot accordingly to the guidance. 
@@ -537,8 +537,8 @@ To properly support authentication, you need to add a `webApplicationInfo` secti
 
 The `id` property is the actual Client ID of the Microsoft App behind the scenes of your Azure Bot. The `resource` property is the unique URI that you configured for that Microsoft App.
 
-You're now ready to package the solution, deploy it on the SharePoint Online App Catalog, and play with it. You can follow the instructions provided in section ["Run and test the solution"](./Building-Your-First-Bot-Powered-ACE.md#run-and-test-the-solution) of the reference article ["Building your first Bot Powered Adaptive Card Extension."](./Building-Your-First-Bot-Powered-ACE.md)
-
 Consider a Bot Powered ACE configured for multitenant and deployed on a target tenant. The first time users run it, they need to grant consent to your Azure Bot application to access Microsoft Graph with delegated permissions. The user's consent is collected through a custom dialog provided by Microsoft Entra ID. In the following picture, you can see the user's consent dialog in action.
 
 ![The popup dialog of Microsoft Entra ID to collect the user's consent to access specific resources based on the current Azure Bot application permissions.](./images/Bot-Powered-ACE-Secured-Consent-Multitenant.png)
+
+You're now ready to package the solution, deploy it on the SharePoint Online App Catalog, and play with it. You can follow the instructions provided in section ["Run and test the solution"](./Building-Your-First-Bot-Powered-ACE.md#run-and-test-the-solution) of the reference article ["Building your first Bot Powered Adaptive Card Extension."](./Building-Your-First-Bot-Powered-ACE.md)

docs/spfx/viva/bot-powered/Building-Your-First-Bot-Powered-ACE-TTK-TS.md

@@ -528,3 +528,9 @@ Right after that, your Azure Bot is fully configured and ready to be used.
 ![The panel to configure channels for the Azure Bot. There are now three pre-selected channels: "Direct Line", "Web Chat", and "Microsoft 365.](./images/Azure-Portal-Create-Azure-Bot-12-TTK.png)
 
 You're now ready to run and test your Bot Powered ACE built with Microsoft Teams Toolkit and TypeScript.
+
+## Additional readings
+
+Now that you have built your first Bot Powered ACE with Microsoft Teams Toolkit and TypeScript, you are ready to dig into additional details reading the following articles. 
+ 
+* [Authentication and Authorization in Bot Powered Adaptive Card Extensions](./AuthN-and-AuthZ-in-Bot-Powered-ACEs.md)

docs/toc.yml

@@ -668,10 +668,16 @@
       href: spfx/viva/bot-powered/Overview-Bot-Powered-ACEs.md
     - name: Understanding Bot Powered Adaptive Card Extensions
       href: spfx/viva/bot-powered/Understanding-Bot-Powered-ACEs.md
-    - name: Building your first Bot Powered Adaptive Card Extension
+    - name: Building your first Bot Powered ACE with .NET
       href: spfx/viva/bot-powered/Building-Your-First-Bot-Powered-ACE.md
+    - name: Building your first Bot Powered ACE with Microsoft Teams Toolkit and TypeScript
+      href: spfx/viva/bot-powered/Building-Your-First-Bot-Powered-ACE-TTK-TS.md
     - name: Authentication and Authorization in Bot Powered ACEs
       href: spfx/viva/bot-powered/AuthN-and-AuthZ-in-Bot-Powered-ACEs.md
+    - name: Building Bot Powered ACEs with Microsoft Entra ID and Single Sign-on (SSO)
+      href: spfx/viva/bot-powered/AuthN-and-AuthZ-in-Bot-Powered-ACEs-Entra.md
+    - name: Building Bot Powered ACEs with Magic Code authentication
+      href: spfx/viva/bot-powered/AuthN-and-AuthZ-in-Bot-Powered-ACEs-Magic-Code.md
     - name: Bringing Bot Powered ACEs to the market place
       href: spfx/viva/bot-powered/publish-to-marketplace-overview.md
   - name: Tutorials