MicrosoftDocs · Kaiqb · Nov 25, 2019 · Jun 28, 2019 · Jul 1, 2019 · Jul 1, 2019
diff --git a/articles/bot-service-channel-connect-cortana.md b/articles/bot-service-channel-connect-cortana.md
@@ -7,7 +7,7 @@ ms.author: kamrani
 manager: kamrani
 ms.topic: article
 ms.service: bot-service
-ms.date: 04/30/2018
+ms.date: 11/22/2019
 ---
 # Connect a bot to Cortana
 
@@ -98,6 +98,8 @@ When you are done filling out the registration form for your Cortana skill, clic
 
 At this point your bot is deployed as a Cortana skill to your account.
 
+Next, you need to enable and authorize the Bot skill to connect to your account. In your Cortana app, say or type "ask *Invocation Name*" where the "Invocation Name" is what you configured in the Cortana Channel in the Azure portal. Cortana will then prompt you to allow your Bot Skill to connect. If you choose "Yes" to allow this, the skill will now work and show up in Cortana's skill list.
+
 ## Next steps
 
 * [Cortana Skills Kit](https://aka.ms/CortanaSkillsKitOverview)

diff --git a/articles/bot-service-overview-introduction.md b/articles/bot-service-overview-introduction.md
@@ -70,7 +70,6 @@ Bots are complex apps, with a lot of different parts working together. Like any
 
 - [Unit Test](https://docs.microsoft.com/azure/bot-service/unit-test-bots?view=azure-bot-service-4.0) your bot with the July update of Bot Framework SDK.
 
-
 ### Publish 
 When you are ready for your bot to be available on the web, publish your bot to [Azure](bot-builder-howto-deploy-azure.md) or to your own web service or data center. Having an address on the public internet is the first step to your bot coming to life on your site, or inside chat channels.
 

diff --git a/articles/bot-service-resources-bot-framework-faq.md b/articles/bot-service-resources-bot-framework-faq.md
@@ -1,12 +1,12 @@
 ---
 title: Bot Service Frequently Asked Questions | Microsoft Docs
 description: A list of Frequently Asked Questions about elements of the Bot Framework and when new features will become available.
-author: DeniseMak
+author: scheyal
 ms.author: kamrani
 manager: kamrani
 ms.topic: article
 ms.service: bot-service
-ms.date: 02/21/2019
+ms.date: 11/21/2019
 ---
 
 # Bot Framework Frequently Asked Questions
@@ -45,43 +45,41 @@ For more information, see:
 - [Deploy the Language Understanding (LUIS) container to Azure Container Instances](https://docs.microsoft.com/azure/cognitive-services/luis/deploy-luis-on-container-instances)
 - [Container support in Azure Cognitive Services](https://docs.microsoft.com/azure/cognitive-services/cognitive-services-container-support)
 
+## Bot Framework SDK Version 3 Lifetime Support and Deprecation Notice
+Microsoft Bot Framework SDK V4 was released in September 2018, and since then we have shipped a few dot-release improvements. As announced previously, the V3 SDK is being retired. Accordingly, there will be no more development in V3 repositories. **Existing V3 bot workloads will continue to run without interruption. We have no plans to disrupt any running workloads**.
 
-## Bot Framework SDK Version 3 Lifetime Support 
-SDK V3 bots continue to run and be supported by Azure Bot Service.  Since the release of Bot Framework SDK V4, as with other frameworks, we continue supporting SDK V3 with security, high priority bug fixes, and connector / protocol layer updates.  Customers can expect v3 support to continue through 2019.
+As mentioned, Bot Builder SDK V3 bots continue to run and be supported by Azure Bot Service. Bot Builder SDK V3 will only be supported  for critical security bug fixes, connector, and protocol layer compatibility updates.  
 
-### What is Microsoft plan for supporting existing V3 bots? What happens to my V3 Bots? Will my V3 bots stop working?
-SDK V3 bots continue to run and be supported by Azure Bot Service.  Since the release of Bot Framework SDK V4, as with other frameworks, we continue supporting SDK V3 with security, high priority bug fixes, and connector / protocol layer updates.  Customers can expect v3 support to continue through 2019.
-- Azure Bot Service and Bot Framework V3 are both GA products and are fully supported. The underlying Bot Framework protocol and connector libraries have not changed and are shared between both V3 and V4 SDKs.  
-- Bots created with Bot Framework (BotBuilder) V3 SDK continue to be supported through 2019. 
-- Customers can continue creating V3 bots using Azure portal or Azure CLI tools.
+All new features and capabilities are developed exclusively on [Bot Framework SDK V4](https://github.com/microsoft/botframework-sdk).  Customers are encouraged to migrate their bots to V4 as soon as possible.
 
-### What happens to my bot written to REST & Bot Framework Protocol 3.1?
-- Azure Bot Service and Bot Framework V3 are both GA products and are fully supported.
-- The Bot Framework protocol has not changed and are shared between both V3 and V4 SDKs.  
+We highly recommend that you start migrating your V3 bots to V4. In order to support this migration we have produced migration documentation and will provide extended support for migration initiatives (via standard channels such as Stack Overflow and Microsoft Customer Support).
 
-### Will there be more updates, additional development for the V3 SDK or just bugfixes?  
-- We will update V3 with minor enhancements, mainly at the connector layer, and with security and high priority bug fixes.  
-- Updates to V3 will be released twice yearly and as needed, based on bug fixes and/or required protocol changes. 
-- Current plan is to publish minor and patch versions of V3 to NuGet and NPM for our C# and JavaScript SDKs.
+For more information please refer to the following references:
+* [Essential Migration Guidance](https://aka.ms/bfv3v4migration)
+* Primary V4 Repositories to develop Bot Framework bots
+  * [Botbuilder for dotnet](https://github.com/microsoft/botbuilder-dotnet)
+  * [Botbuilder for JS](https://github.com/microsoft/botbuilder-js) 
+* QnA Maker Libraries were replaced with the following V4 libraries:
+  * [Libraries for dotnet](https://github.com/Microsoft/botbuilder-dotnet/tree/master/libraries/Microsoft.Bot.Builder.AI.QnA)
+  * [Libraries for JS](https://github.com/Microsoft/botbuilder-js/blob/master/libraries/botbuilder-ai/src/qnaMaker.ts)
+* Azure Libraries were replaced with the following V4 libraries:
+  * [Botbuilder for JS Azure](https://github.com/Microsoft/botbuilder-js/tree/master/libraries/botbuilder-azure)
+  * [Botbuilder for dotnet Azure](https://github.com/Microsoft/botbuilder-dotnet/tree/master/libraries/Microsoft.Bot.Builder.Azure)
 
-### Why V4 is not backwards compatible with V3?
-- At the protocol level, communication between your conversational app (aka your bot) to different channels uses the Bot Framework Activity protocol which is identical between V3 and V4. The same underlying Azure Bot Service (AZURE BOT SERVICE) infrastructure supports both V3 and V4 bots.
-- Bot Framework SDK V4 offers conversational centric development experience with an SDK architecture that is modular and extensible, empowering developers to create robust and sophisticated chat applications. V4 extendable design was based on customer feedback, suggesting SDK V3 dialog models and primitives are too ridged and constraining extendibility.  
+### V3 Status Summary
 
-### What is the general migration strategy? I have a V3 bot, how can I migrate it to V4/ Can I migrate my V3 bot to V4?
+#### ABS Service
+1.	The ABS service side will continue to support running V3 bots with no planned end of life and any running bots will not be disrupted. 
+2.	Channels will remain compatible with V3 with no disruption or end of life plan.
+3.	Creation of new V3 bots is disabled on the portal; however, expert users who wish to deploy their V3 bots independently, not on ABS (e.g. as webapp service) can do so.
 
-- See [Differences between the v3 and v4 .NET SDK](v4sdk/migration/migration-about.md) for information on migrating V3 bots to V4.
-- At this time, migration help for bots created with SDK V3 to SDK V4 will come in the form of documentation and samples. We currently do not have plans to provide any SDK V3 compatibility layer in SDK V4 that would allow V3 build bots to work within a V4 bot.
-- If you already have Bot Framework SDK V3 bots in production, don’t worry, they continue to work as is for the foreseeable future.
-- Bot Framework SDK V4 is an evolution of the very successful V3 SDK. V4 is a major version release which includes breaking changes that prevent V3 bots from running on the newer V4 SDK.
+#### SDK and Tools
 
-### Should I build new a bot using V3 or V4?
-- For new conversational experiences, we recommend you start a new bot using Bot Framework SDK V4.
-- If you are already familiar with Bot Framework SDK V3, you should take the time to learn about the new version and features offered with the new [Bot Framework SDK V4](https://aka.ms/botframeowrkoverview).
-- If you already have Bot Framework SDK V3 bots in production, don’t worry, they continue to work as is for the foreseeable future.
-- You can create Bot Framework SDK V4 and older V3 bots via Azure portal and Azure Command Line. 
+1.	We are not investing in V3 from SDK side, and will only apply critical security fixes to the SDK branches for the foreseeable future (Exception: We plan to add a Skills connector to allow V4 bots to call legacy V3 bots).
+2.	SDKs and tools development is exclusively on V4 with no V3 work done or planned (hence we’re already “there”).
+3.	We do not prevent anyone from running old tools to manage their V3 bots. 
 
-### How can I migrate Azure Bot Service from one region to another?
+## How can I migrate Azure Bot Service from one region to another?
 
 Azure Bot Service does not support region move. It’s a global service that is not tied to any specific region.
 

diff --git a/articles/v4sdk/abs-quickstart.md b/articles/v4sdk/abs-quickstart.md
@@ -6,7 +6,7 @@ ms.author: kamrani
 manager: kamrani
 ms.topic: article
 ms.service: bot-service
-ms.date: 08/15/2019
+ms.date: 11/22/2019
 ---
 
 # Create a bot with Azure Bot Service
@@ -22,11 +22,11 @@ Azure Bot Service provides the core components for creating bots, including the
 
 ## Prerequisites
 
-- [Azure](http://portal.azure.com) account
+- [Azure](https://portal.azure.com) account
 
 ### Create a new bot service
 
-1. Log in to the [Azure portal](http://portal.azure.com/).
+1. Log in to the [Azure portal](https://portal.azure.com/).
 1. Click **Create new resource** link found on the upper left-hand corner of the Azure portal, then select **AI + Machine Learning** > **Web App bot**. 
 
 ![create bot](../media/azure-bot-quickstarts/abs-create-blade.png)
@@ -46,6 +46,7 @@ Azure Bot Service provides the core components for creating bots, including the
  | **App name** | A unique name | The unique URL name of the bot. For example, if you name your bot *myawesomebot*, then your bot's URL will be `http://myawesomebot.azurewebsites.net`. The name must use alphanumeric and underscore characters only. There is a 35 character limit to this field. The App name cannot be changed once the bot is created. |
  | **Bot template** | Echo bot | Choose **SDK v4**. Select either C# or Node.js for this quickstart, then click **Select**.  
  | **App service plan/Location** | Your app service plan  | Select an [app service plan](https://azure.microsoft.com/pricing/details/app-service/plans/) location. Your location choice can be any location listed, though it's often best to choose the same location as the bot service. |
+ | **LUIS Accounts** _Only available for Basic Bot template_ | LUIS Azure Resource Name | After [migrating LUIS Resources over to an Azure Resource](https://docs.microsoft.com/azure/cognitive-services/luis/luis-migration-authoring), input the Azure Resource name to associate this LUIS Application with that Azure Resource. 
  | **Application Insights** | On | Decide if you want to turn [Application Insights](/bot-framework/bot-service-manage-analytics) **On** or **Off**. If you select **On**, you must also specify a regional location. Your location choice can be any location listed, though it's often best to choose the same location as the bot service. |
  | **Microsoft App ID and password** | Auto create App ID and password | Use this option if you need to manually enter a Microsoft App ID and password. Otherwise, a new Microsoft App ID and password will be created for you in the bot creation process. When creating an app egistration manually for the Bot Service, please ensure that the supported account types is set to ‘Accounts in any organizational directory’ or ‘Accounts in any organizational directory and personal Microsoft accounts (e.g. Skype, Outlook.com, Xbox, etc.)’ |
 

diff --git a/articles/v4sdk/bot-builder-telemetry.md b/articles/v4sdk/bot-builder-telemetry.md
@@ -7,7 +7,7 @@ ms.author: kamrani
 manager: kamrani
 ms.topic: article
 ms.service: bot-service
-ms.date: 07/17/2019
+ms.date: 11/17/2019
 monikerRange: 'azure-bot-service-4.0'
 ---
 
@@ -54,7 +54,6 @@ We will start with the [CoreBot sample app](https://aka.ms/cs-core-sample) and a
 
 2. Add  the `Microsoft.Bot.Builder.Integration.ApplicationInsights.Core ` NuGet package. For more information on using NuGet, see [Install and manage packages in Visual Studio](https://aka.ms/install-manage-packages-vs):
 
-
 3. Include the following statements in `Startup.cs`:
     ```csharp
     using Microsoft.ApplicationInsights.Extensibility;
@@ -108,7 +107,7 @@ We will start with the [CoreBot sample app](https://aka.ms/cs-core-sample) and a
     }
     ```
 
-7. Add the Application Insights instrumentation key in your `appsettings.json` file The `appsettings.json` file contains metadata about external services the Bot uses while running. For example, CosmosDB, Application Insights and the Language Understanding (LUIS) service connection and metadata is stored there. The addition to your `appsettings.json` file must be in this format:
+6. Add the Application Insights instrumentation key in your `appsettings.json` file The `appsettings.json` file contains metadata about external services the Bot uses while running. For example, CosmosDB, Application Insights and the Language Understanding (LUIS) service connection and metadata is stored there. The addition to your `appsettings.json` file must be in this format:
 
     ```json
     {
@@ -367,14 +366,6 @@ The easiest way to test is by creating a dashboard using [Azure portal's templat
 ```
 -->
 
-
-
-
-
-
-
-
-
 <!--
 ## Additional information
 
@@ -405,6 +396,7 @@ If using a Dialog within your Bot, every Dialog-based object (including Prompts)
 
 There are three main components available for your bot to log telemetry, and each component has customization available for logging your own events, which are discussed in this section. 
 
+
 - A  [Bot Framework Middleware component](#telemetry-middleware) (*TelemetryLoggerMiddleware*) that will log when messages are received, sent, updated or deleted. You can override for custom logging.
 - [*LuisRecognizer* class.](#telemetry-support-luis)  You can override for custom logging in two ways - per invocation (add/replace properties) or derived classes.
 - [*QnAMaker*  class.](#telemetry-qnamaker)  You can override for custom logging in two ways - per invocation (add/replace properties) or derived classes.
@@ -413,6 +405,7 @@ There are three main components available for your bot to log telemetry, and eac
 All components log using the `IBotTelemetryClient`  (or `BotTelemetryClient` in node.js) interface which can be overridden with a custom implementation.
 
 
+
 #### Telemetry Middleware
 
 |C#  | JavaScript |

diff --git a/articles/v4sdk/bot-builder-tutorial-dispatch.md b/articles/v4sdk/bot-builder-tutorial-dispatch.md
@@ -83,7 +83,8 @@ Before you can create the dispatch model, you'll need to have your LUIS apps and
 
 7. Once your new LUIS app has been published, select the _MANAGE_ Tab. From the 'Application Information' page, record the values `Application ID` as "_app-id-for-app_" and `Display name` as "_name-of-app_". From the 'Key and Endpoints' page, record the values `Authoring Key` as "_your-luis-authoring-key_" and `Region` as "_your-region_". These values will later be used within your 'appsetting.json' file.
 
-8. Once completed, _Train_ and _Publish_ both your LUIS **weather** app and your LUIS **dispatch** app by repeating the above steps for 'Weather.json' file.
+8. Once completed, _Train_ and _Publish_ both your LUIS **Home Automation** app and your LUIS **Weather** app by repeating the above steps for 'Weather.json' file.
+
 
 ### Create QnA Maker knowledge base
Original file line number	Diff line number	Diff line change
Expand Up		@@ -70,7 +70,6 @@ Bots are complex apps, with a lot of different parts working together. Like any

		- [Unit Test](https://docs.microsoft.com/azure/bot-service/unit-test-bots?view=azure-bot-service-4.0) your bot with the July update of Bot Framework SDK.


		### Publish
		When you are ready for your bot to be available on the web, publish your bot to [Azure](bot-builder-howto-deploy-azure.md) or to your own web service or data center. Having an address on the public internet is the first step to your bot coming to life on your site, or inside chat channels.

Expand Down