MicrosoftDocs · openpublishbuild · Feb 25, 2020 · Feb 25, 2020 · Feb 26, 2020 · Feb 27, 2020
diff --git a/articles/TOC.md b/articles/TOC.md
@@ -18,7 +18,10 @@
 ## [Managing state](v4sdk/bot-builder-concept-state.md)
 ## [Dialogs library](v4sdk/bot-builder-concept-dialog.md)
 ## [Middleware](v4sdk/bot-builder-concept-middleware.md)
-## [User authentication](v4sdk/bot-builder-concept-authentication.md)
+## Authentication
+### [Bot authentication](v4sdk/bot-builder-concept-authentication.md)
+### [Identity providers](v4sdk/bot-builder-concept-identity-providers.md)
+### [Single sign on](v4sdk/bot-builder-concept-sso.md)
 ## [Manage bot resources](v4sdk/bot-file-basics.md)
 ## [How bots for Microsoft Teams work](v4sdk/bot-builder-basics-teams.md)
 ## [About skills](v4sdk/skills-conceptual.md)
@@ -31,15 +34,15 @@
 ### [Enterprise Productivity bot](bot-service-scenario-enterprise-productivity.md)
 ### [Information bot](bot-service-scenario-informational.md)
 ### [Internet of Things bot](bot-service-scenario-internet-things.md)
-# How-To 
+# How-To
 ## [Design](design/TOC.md)
 ## Develop
 <!-- ## [Best practice for welcoming the user](v4sdk/bot-builder-welcome-user.md) -->
 ### [Send and receive text message](v4sdk/bot-builder-howto-send-messages.md)
 ### [Add media to messages](v4sdk/bot-builder-howto-add-media-attachments.md)
 ### [Add buttons to guide user action](v4sdk/bot-builder-howto-add-suggested-actions.md)
-### [Save user and conversation data](v4sdk/bot-builder-howto-v4-state.md) 
-### [Prompt users for input](v4sdk/bot-builder-primitive-prompts.md) 
+### [Save user and conversation data](v4sdk/bot-builder-howto-v4-state.md)
+### [Prompt users for input](v4sdk/bot-builder-primitive-prompts.md)
 ### [Send welcome message to users](v4sdk/bot-builder-send-welcome-message.md)
 ### [Send proactive notifications to users](v4sdk/bot-builder-howto-proactive-message.md)
 ### [Implement sequential conversation flow](v4sdk/bot-builder-dialog-manage-conversation-flow.md)
@@ -51,7 +54,7 @@
 <!--#### [Implement a greeting dialog](v4sdk/bot-builder-dialogs-greeting.md)--TODO: Add once there's a sample.-->
 ### [Handle user interruptions](v4sdk/bot-builder-howto-handle-user-interrupt.md)
 ### [Write directly to storage](v4sdk/bot-builder-howto-v4-storage.md)
-### [Add authentication to your bot](v4sdk/bot-builder-authentication.md)
+### [Add authentication to a bot](v4sdk/bot-builder-authentication.md)
 ### [Implement custom storage for your bot](v4sdk/bot-builder-custom-storage.md)
 ### Skills
 #### [Implement a skill](v4sdk/skill-implement-skill.md)

diff --git a/articles/bot-builder-deploy-az-cli.md b/articles/bot-builder-deploy-az-cli.md
@@ -7,7 +7,7 @@ ms.author: kamrani
 manager: kamrani
 ms.topic: conceptual
 ms.service: bot-service
-ms.date: 08/06/2019
+ms.date: 03/23/2020
 monikerRange: 'azure-bot-service-4.0'
 ---
 
@@ -33,57 +33,51 @@ In this article we will show you how to deploy a basic bot to Azure. We will exp
 
 [!INCLUDE [deploy az subscription](~/includes/deploy/snippet-az-set-subscription.md)]
 
-
 ### 3. Create the application registration
 
 [!INCLUDE [deploy create app registration](~/includes/deploy/snippet-create-app-registration.md)]
 
-
 ### 4. Create the bot application service
 
 When creating the bot application service, you can deploy your bot in a new or in an existing resource group. Choose the option that works best for you.
 
-Make sure that you have the correct path to your bot project ARM deployment templates directory `DeploymentTemplates`, you need it to assign the value to `template-file`.
-
-
-> [!NOTE]
+> [!IMPORTANT]
 > Python bots cannot be deployed to a resource group that contains Windows services/bots.  Multiple Python bots can be deployed to the same resource group, but create other services (LUIS, QnA, etc.) in another resource group.
 
+Make sure that you have the correct path to your bot project ARM deployment templates directory `DeploymentTemplates`, you need it to assign the value to `template-file`.
 
 #### **Deploy via ARM template (with **new** Resource Group)**
 
 <!-- ##### Create Azure resources -->
-[!INCLUDE [ARM with new resourece group](~/includes/deploy/snippet-ARM-new-resource-group.md)]
+[!INCLUDE [ARM with new resource group](~/includes/deploy/snippet-ARM-new-resource-group.md)]
 
 
 #### **Deploy via ARM template (with **existing**  Resource Group)**
 
-[!INCLUDE [ARM with existing resourece group](~/includes/deploy/snippet-ARM-existing-resource-group.md)]
+[!INCLUDE [ARM with existing resource group](~/includes/deploy/snippet-ARM-existing-resource-group.md)]
 
 ---
 
 ### 5. Prepare your code for deployment
 
+[!INCLUDE [Work around for .NET Core 3.1 SDK](~/includes/deploy/samples-workaround-3-1.md)]
+
 #### 5.1 Retrieve or create necessary IIS/Kudu files
 
 [!INCLUDE [retrieve or create IIS/Kudu files](~/includes/deploy/snippet-IIS-Kudu-files.md)]
 
-
 #### 5.2 Zip up the code directory manually
 
 [!INCLUDE [zip up code](~/includes/deploy/snippet-zip-code.md)]
 
-
 ## Deploy code to Azure
 
 [!INCLUDE [deploy code to Azure](~/includes/deploy/snippet-deploy-code-to-az.md)]
 
-
 ## Test in Web Chat
 
 [!INCLUDE [test in web chat](~/includes/deploy/snippet-test-in-web-chat.md)]
 
-
 ## Additional information
 
 Deploying your bot to Azure will involve paying for the services you use. The [billing and cost management](https://docs.microsoft.com/azure/billing/) article helps you understand Azure billing, monitor usage and costs, and manage your account and subscriptions.

diff --git a/articles/bot-service-build-continuous-deployment.md b/articles/bot-service-build-continuous-deployment.md
@@ -7,7 +7,7 @@ ms.author: kamrani
 manager: kamrani
 ms.topic: article
 ms.service: bot-service
-ms.date: 12/10/2019
+ms.date: 03/23/2020
 monikerRange: 'azure-bot-service-4.0'
 ---
 
@@ -18,53 +18,68 @@ monikerRange: 'azure-bot-service-4.0'
 This article shows you how to configure continuous deployment for your bot. You can enable continuous deployment to automatically deploy code changes from your source repository to Azure. In this topic, we'll cover setting up continuous deployment for GitHub. For information on setting up continuous deployment with other source control systems, see the additional resource section at the bottom of this page.
 
 ## Prerequisites
+
 - If you don't have an Azure subscription, create a [free account](https://portal.azure.com) before you begin.
 - You **must** [deploy your bot to Azure](bot-builder-deploy-az-cli.md) before enabling continuous deployment.
 
 ## Prepare your repository
-Make sure that your repository root has the correct files in your project. This will allow you to get automatic builds from the Azure App Service Kudu build server. 
+
+Make sure that your repository root has the correct files in your project. This will allow you to get automatic builds from the build provider.
 
 |Runtime | Root directory files |
 |:-------|:---------------------|
 | ASP.NET Core | .sln or .csproj |
 | Node.js | server.js, app.js, or package.json with a start script |
 | Python | app.py |
 
-
 ## Continuous deployment using GitHub
+
 To enable continuous deployment with GitHub, navigate to the **App Service** page for your bot in the Azure portal.
 
-Click **Deployment Center** > **GitHub** > **Authorize**.
+1. Click **Deployment Center** > **GitHub** > **Authorize**.
+
+   ![Continous deployment](~/media/azure-bot-build/azure-deployment.png)
 
-![Continous deployment](~/media/azure-bot-build/azure-deployment.png)
+   1. In the browser window that opens up, click **Authorize AzureAppService**.
 
-In the browser window that opens up, click **Authorize AzureAppService**. 
+      ![Azure Github Permission](~/media/azure-bot-build/azure-deployment-github.png)
 
-![Azure Github Permission](~/media/azure-bot-build/azure-deployment-github.png)
+   1. After authorizing the **AzureAppService**, go back to **Deployment Center** in the Azure portal.
 
-After authorizing the **AzureAppService**, go back to **Deployment Center** in the Azure portal.
+1. Click **Continue**.
 
-1. Click **Continue**. 
+        > [!div class="mx-imgBorder"]
+        > ![Continue to build provider](~/media/azure-bot-build/azure-deployment-continue.png)
 
-1. Select **App Service build service**.
+1. On the **Build provider** page, select the build provider you want to use and click **Continue**.
 
-1. Click **Continue**.
+    > [!IMPORTANT]
+    > With the release of the Bot Framework 4.8 SDK, the .NET Bot Framework samples now target the .NET Core 3.1 SDK.
+    > Not all Azure data centers are configured to build such bots.
+    >
+    > See the map of [.NET Core on App Service](https://aspnetcoreon.azurewebsites.net/) for the centers in which you can build .NET Core 3.1 apps using Kudu. (All centers can run .NET Core 3.1 apps.)
+    >
+    > If you you are deploying a bot that targets the .NET Core 3.1 SDK and you are deploying to a center that can't build .NET Core 3.1 apps using Kudu, use either **GitHub Actions (Preview)** or **Azure Pipelines (Preview)** for your build provider.
+
+    > [!div class="mx-imgBorder"]
+    > ![Select build provider](~/media/azure-bot-build/azure-deployment-build-provider.png)
 
-1. Select **Organization**, **Repository**, and **Branch**.
+1. On the **Configure** page, enter the required information and click **Continue**. The information required will depend on which source control service and build provider you chose.
 
-1. Click **Continue**, and then **Finish** to complete the setup.
+1. On the **Summary** page, review the settings and then click **Finish**.
 
-At this point, continuous deployment with GitHub is set up. Whenever you commit to the source code repository, your changes will automatically be deployed to the Azure Bot Service.
+At this point, continuous deployment with GitHub is set up. New commits in the selected repository and branch now deploy continuously into your App Service app. You can track the commits and deployments on the **Deployment Center** page.
 
 ## Disable continuous deployment
 
 While your bot is configured for continuous deployment, you may not use the online code editor to make changes to your bot. If you want to use the online code editor, you can temporarily disable continuous deployment.
 
 To disable continuous deployment, do the following:
-1. In the [Azure portal](https://portal.azure.com), go to your bot's **All App Service settings** blade and click **Deployment Center**. 
+
+1. In the [Azure portal](https://portal.azure.com), go to your bot's **All App Service settings** blade and click **Deployment Center**.
 1. Click **Disconnect** to disable continuous deployment. To re-enable continuous deployment, repeat the steps from the appropriate sections above.
 
 ## Additional resources
-- To enable continuous deployment from BitBucket and Azure DevOps Services, see  [continous deployment using Azure App Service](https://docs.microsoft.com/azure/app-service/deploy-continuous-deployment).
-
 
+- For more information about continuous deployment in Azure, see  [continuous deployment to Azure App Service](https://docs.microsoft.com/azure/app-service/deploy-continuous-deployment).
+- When you use GitHub actions for the build provider, a workflow is created in your repository. You can learn more about using [GitHub Actions](https://help.github.com/en/actions) on the GitHub site.
diff --git a/articles/bot-service-channel-connect-directlinespeech.md b/articles/bot-service-channel-connect-directlinespeech.md
@@ -17,7 +17,7 @@ ms.author: travisw
 
 You can configure your bot to allow client applications to communicate with it through the Direct Line Speech channel.
 
-Once you have built your bot, onboarding it with Direct Line Speech will enable low latency, high reliability connection with client applications using the [Speech SDK](https://aka.ms/speech/sdk). These connections are optimized for voice in, voice out conversational experiences. For more information on Direct Line Speech and how to build client applications, visit the [custom voice-first virtual assistant](https://aka.ms/bots/speech/va) page. 
+Once you have built your bot, onboarding it with Direct Line Speech will enable low latency, high reliability connection with client applications using the [Speech SDK](https://aka.ms/speech-service-docs). These connections are optimized for voice in, voice out conversational experiences. For more information on Direct Line Speech and how to build client applications, visit the [custom voice-first virtual assistant](https://aka.ms/cognitive-services-voice-assistants) page.
 
 ## Add the Direct Line Speech channel
 
@@ -29,9 +29,20 @@ Once you have built your bot, onboarding it with Direct Line Speech will enable
 
     ![selecting direct line speech channel](media/voice-first-virtual-assistants/bot-service-channel-directlinespeech-connectspeechchannel.png "connecting Direct Line Speech")
 
-1. Direct Line Speech Channel requires a Cognitive Services resource. You can either use an existing resource or create a new Cognitive Services resource following the [instructions](https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account). 
+1. Configure the Direct Line Speech as shown in the picture below.
 
-    ![selecting direct line speech channel](media/voice-first-virtual-assistants/bot-service-channel-directlinespeech-cognitivesericesaccount-selection.png "selecting Cogntive Services resource")
+    ![selecting direct line speech channel](media/voice-first-virtual-assistants/bot-service-channel-directlinespeech-cognitivesericesaccount-selection.png "selecting Cognitive Services resource")
+
+    The Direct Line Speech Channel requires a Cognitive Services resource, specifically a **speech** cognitive service resource. You can either use an existing resource or create a new one. To create a new speech resource follow these steps:
+
+    - Go to the [Azure portal create resources](https://ms.portal.azure.com/#create/hub).
+    - Search for *Speech* and select it from the drop-down list. The following is displayed:
+
+        ![create speech cognitive resource](media/voice-first-virtual-assistants/create-speech-cognitive-resource.PNG "Create speech cognitive resource")
+
+    - Follow the wizard steps.
+
+    For additional information, see [Create a Cognitive Services resource](https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account).
 
 1. Once you've reviewed the terms of use, click `Save` to confirm your channel selection.
 
@@ -41,7 +52,7 @@ Once you have built your bot, onboarding it with Direct Line Speech will enable
 
 With the Direct Line Speech channel connected to your bot, you now need to enable Bot Framework Protocol Streaming Extensions support for optimal, low-latency interaction.
 
-1. If you haven't already, open the blade for your bot in the [Azure Portal](https://portal.azure.com). 
+1. If you haven't already, open the blade for your bot in the [Azure Portal](https://portal.azure.com).
 
 1. Click on **Settings** under the **Bot Management** category (right below **Channels**). Click the checkbox for **Enable Streaming Endpoint**.
 

diff --git a/articles/bot-service-channel-connect-facebook.md b/articles/bot-service-channel-connect-facebook.md
@@ -131,7 +131,7 @@ Ensure that the Facebook Page associated with this bot is published. Status appe
 >
 > Facebook will only consider integrations with limited access to Workplace data (low sensitivity permissions) eligible for continued use until December 31, 2020 if such integrations have completed and passed Security RFI and if the developer reaches out before January 15, 2020 via [Direct Support](https://my.workplace.com/work/admin/direct_support) to request continued use of the app.
 >
-> Bot Framework adapters are available for [JavaScript/Node.js](https://aka.ms/botframework-workplace-adapter) and [C#/.NET](https://aka.ms/bf-workplace-csharp) bots.
+> Bot Framework adapters are available for [JavaScript/Node.js](https://aka.ms/npm-botbuilder-adapter-facebook) and [C#/.NET](https://aka.ms/botbuilder-dotnet-facebook-adapter) bots.
 
 Facebook Workplace is a business-oriented version of Facebook, which allows employees to easily connect and collaborate. It contains live videos, news feeds, groups, messenger, reactions, search, and trending posts. It also supports:
 
@@ -176,11 +176,11 @@ Create a [custom integration](https://developers.facebook.com/docs/workplace/cus
 
 ### Update your bot code with Facebook adapter
 
-Your bot's source code needs to be updated to include an adapter to communicate with Workplace by Facebook. Adapters are available for [JavaScript/Node.js](https://aka.ms/botframework-workplace-adapter) and [C#/.NET](https://aka.ms/bf-workplace-csharp) bots.
+Your bot's source code needs to be updated to include an adapter to communicate with Workplace by Facebook. Adapters are available for [JavaScript/Node.js](https://aka.ms/npm-botbuilder-adapter-facebook) and [C#/.NET](https://aka.ms/botbuilder-dotnet-facebook-adapter) bots.
 
 ### Provide Facebook credentials
 
-You will need to update appsettings.json of your bot with **Facebook App ID**, **Facebook App Secret** and **Page Access Token** values copied from the Facebook Workplace previously. Instead of a traditional pageID, use the numbers following the integrations name on its **About** page. Follow these instructions to update your bot source code in [JavaScript/Node.js](https://aka.ms/botframework-workplace-adapter) or [C#/.NET](https://aka.ms/bf-workplace-csharp).
+You will need to update appsettings.json of your bot with **Facebook App ID**, **Facebook App Secret** and **Page Access Token** values copied from the Facebook Workplace previously. Instead of a traditional pageID, use the numbers following the integrations name on its **About** page. Follow these instructions to update your bot source code in [JavaScript/Node.js](https://aka.ms/npm-botbuilder-adapter-facebook) or [C#/.NET](https://aka.ms/botbuilder-dotnet-facebook-adapter).
 
 ### Submit for review
 
@@ -199,7 +199,7 @@ If you receive a notification from Facebook about deprecation of a certain versi
 ## Connect a bot to Facebook using the Facebook adapter
 
 Use the Bot Framework Facebook adapter to connect your bot with Facebook Workplace. To connect to Facebook messenger, you can use the Facebook channel or the Facebook adapter.
-Facebook adapters are available for [JavaScript/Node.js](https://aka.ms/botframework-workplace-adapter) and [C#/.NET](https://aka.ms/bf-workplace-csharp) bots.
+Facebook adapters are available for [JavaScript/Node.js](https://aka.ms/npm-botbuilder-adapter-facebook) and [C#/.NET](https://aka.ms/botbuilder-dotnet-facebook-adapter) bots.
 
 In this article you will learn how to connect a bot to Facebook using the adapter.  This article will walk you through modifying the EchoBot sample to connect it to Facebook.
 

diff --git a/articles/bot-service-channel-connect-skypeforbusiness.md b/articles/bot-service-channel-connect-skypeforbusiness.md
@@ -16,5 +16,5 @@ Skype for Business Online keeps you connected with co-workers and business partn
 
 > [!IMPORTANT]
 > **Skype for Business channel of Bot Framework was deprecated on June 30, 2019.**
-> 
-> Skype for Business channel stopped accepting new bots on June 30, 2019.  Existing bots continued operating through October 31, 2019.  The channel is currently being deprecated, and no production loads should be using it.  Microsoft Teams is the preferred communication tool from Microsoft.  Learn how to [connect your bot to Microsoft Teams](https://msdn.microsoft.com/microsoft-teams/bots).
+>
+> Skype for Business channel stopped accepting new bots on June 30, 2019.  Existing bots continued operating through October 31, 2019.  The channel is currently being deprecated, and no production loads should be using it.  Microsoft Teams is the preferred communication tool from Microsoft.  Learn how to [connect your bot to Microsoft Teams](https://aka.ms/channel-connect-teams).