Updated articles about Bot Powered ACEs in .NET

Author: PaoloPia

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

@@ -1,7 +1,7 @@
 ---
 title: Building your first Bot Powered Adaptive Card Extension
 description: Learn how to build your first Bot Powered Adaptive Card Extension using the Bot Framework for Microsoft .NET.
-ms.date: 02/01/2024
+ms.date: 10/30/2024
 ms.localizationpriority: high
 ---
 # Building your first Bot Powered Adaptive Card Extension
@@ -10,7 +10,7 @@ Bot Powered Adaptive Card Extensions (ACEs) for Microsoft Viva Connections enabl
 
 From a development point of view, a Bot Powered ACE behaves like a regular client-side ACE built with SharePoint Framework (SPFx). As such, you can render Card Views, Quick Views, you can provide properties configurable via a Property Pane, and you can implement specific behaviors to handle actions in the user interface of the ACE. You can learn more about the basics of client-side Adaptive Card Extensions for Microsoft Viva Connections by reading the tutorial ["Build your first SharePoint Adaptive Card Extension."](../get-started/build-first-sharepoint-adaptive-card-extension.md)
 
-In this tutorial, you learn how to build a basic Bot Powered ACE with a step by step approach. You can build Bot Powered ACEs either using C# and .NET or using TypeScript and Node.js.
+You can build Bot Powered ACEs either using C# and .NET or using TypeScript and Node.js. In this tutorial, you learn how to build a basic Bot Powered ACE using C# with a step by step approach.
 
 You can learn more about the architecture of the Bot Powered ACEs by reading the article ["Understanding Bot Powered Adaptive Card Extensions."](./Understanding-Bot-Powered-ACEs.md)
 
@@ -70,7 +70,7 @@ In the automatically scaffolded solution, you find a bunch of autogenerated file
 
 ### Registering the Bot in Azure
 
-Before proceeding with the actual implementation of the Bot Powered ACE, you need to register a Bot in Microsoft Azure. 
+Before proceeding with the actual implementation of the Bot Powered ACE, you need to register a Bot in Microsoft Azure.
 
 Open a web browser and navigate to the [Azure Management Portal](https://portal.azure.com/). From the Azure Management Portal home page, select "Create a resource" and choose to create an "Azure Bot" service.
 
@@ -85,7 +85,7 @@ Provide a handle for your Bot, which must be compliant with the following rules:
 
 The Bot handle becomes the display name of the Bot. However, you can change the display name later, while the Bot Handle is immutable, once registered.
 
-Choose a target subscription and resource group, as well a data residency policy. From a pricing point of view, while you're developing and testing with Bot Powered ACEs, you can select the "F0 - Free" pricing tier. Once you're ready to release your Bot in production, you can upgrade the pricing tier to "S1 - Standard."
+Choose a target subscription and resource group, as well as a data residency policy. From a pricing point of view, while you're developing and testing with Bot Powered ACEs, you can select the "F0 - Free" pricing tier. Once you're ready to release your Bot in production, you can upgrade the pricing tier to "S1 - Standard."
 
 A Microsoft App ID is required to register an Azure Bot. Depending on your solution, you can select a different type of application through the "Type of App" option. You can choose any of the following options:
 
@@ -136,7 +136,7 @@ Once you configured the URL for your Bot, you need to configure few more setting
 
 #### Microsoft App configuration
 
-You're brought to the "Certificates & secrets" configuration page of the Microsoft App registered in Microsoft Entra ID for your Bot. From within this page, you can configure a new client secret. Copy the value of the new client secret in a safe place, you reuse it later in this tutorial.
+You're brought to the "Certificates & secrets" configuration page of the Microsoft App registered in Microsoft Entra ID for your Bot. From within this page, you can configure a new client secret. Copy the value of the new client secret in a safe place, you are going to reuse it later in this tutorial.
 
 Now, select the "Overview" panel and save in a safe place, together with the client secret, the values of the following settings:
 
@@ -667,7 +667,7 @@ The manifest file should look like the following one:
 }
 ```
 
-In the **manifest.json** file, you should replace `<App-Client-ID>` with the actual Client ID of your Microsoft App. You should also configure the actual URL of your Bot in the `validDomains` section of the manifest. Lastly, you should consider providing real values for the settings in the `developer` section.
+In the **manifest.json** file, you should replace `<App-Client-ID>` with the actual Client ID of your Microsoft App. You should also configure the actual URL of your Bot in the `validDomains` section of the manifest. Lastly, you should consider providing real values for the settings in the `developer` section. All of the URLs in the `developer` section need to target addresses under HTTPS.
 
 Notice the `dashboardCards` section that defines the actual settings for your Bot Powered ACEs. In particular, through this section you can configure the `id` of the Microsoft App backing your Azure Bot, the `displayName` and `description` of the ACE, as well as the `icon` as a Fluent UI Icon, the Bot that handles the requests and that must be configured in the `bots` section of the **manifest.json**, and last but not least the `defaultSize` for your ACE in the Viva Connections Dashboard.
 
@@ -676,7 +676,7 @@ You can consider copying and reusing the images and the **manifest.json** templa
 ### Run and test the solution
 
 You're now ready to package and deploy your custom solution. You simply need to package the **manifest.json** file and the two images into a .ZIP file, like you would do with any other Microsoft Teams or Microsoft 365 custom application. Name the .ZIP file with whatever name you like, open the App Catalog of your target SharePoint Online tenant, and upload the .ZIP file as a new application package.
-The SharePoint Online server-side infrastructure recognizes the manifest structure and prompt you to enable and deploy the solution on the tenant.
+The SharePoint Online server-side infrastructure recognizes the manifest structure and prompts you to enable and deploy the solution on the tenant.
 
 ![The UI of the new SharePoint AppCatalog prompting to enable the solution and make it tenant-wide available.](./images/App-Catalog-Package-Publishing.png)