Merge remote-tracking branch 'upstream/master'

Author: Carey MacDonald

articles/active-directory-b2c/active-directory-b2c-devquickstarts-graph-dotnet.md

@@ -49,10 +49,7 @@ To use the Azure AD Graph API with your B2C tenant, you need to register an appl
 
 ### Create client secret
 
-1. Under **API ACCESS**, select **Keys**.
-1. Enter a description for the key in the **Key description** box. For example, *Management Key*.
-1. Select a validity **Duration** and then select **Save**.
-1. Record the key's **VALUE**. You use this value for configuration in a later step.
+[!INCLUDE [active-directory-b2c-client-secret](../../includes/active-directory-b2c-client-secret.md)]
 
 You now have an application that has permission to *create*, *read*, and *update* users in your Azure AD B2C tenant. Continue to the next section to add user *delete* and *password update* permissions.
 

articles/active-directory-b2c/active-directory-b2c-reference-audit-logs.md

@@ -108,10 +108,7 @@ Follow these steps register an application, grant it the required Microsoft Grap
 
 ### Create client secret
 
-1. Under **API ACCESS**, select **Keys**.
-1. Enter a description for the key in the **Key description** box. For example, *Audit Log Key*.
-1. Select a validity **Duration**, then select **Save**.
-1. Record the key's **VALUE**. You need this value for authentication in automation scripts like the example PowerShell script shown in a later section.
+[!INCLUDE [active-directory-b2c-client-secret](../../includes/active-directory-b2c-client-secret.md)]
 
 You now have an application with the required API access, an application ID, and a key that you can use in your automation scripts. See the PowerShell script section later in this article for an example of how you can get activity events with a script.
 

articles/active-directory-b2c/active-directory-b2c-user-migration.md

@@ -61,11 +61,7 @@ Next, grant the application the Azure AD Graph API permissions required for writ
 
 Create a client secret (key) for use by the user migration application that you configure in a later step.
 
-1. In the **Registered app** page, select **Settings**.
-1. Select **Keys**.
-1. Under **Passwords**, add a new key (also known as a client secret) named *MyClientSecret* or another name of your choosing, select an expiration window, select **Save**, and then copy the key value for later use.
-
-    ![Application ID value and Keys menu item highlighted in Azure portal](media/active-directory-b2c-user-migration/pre-migration-app-id-and-key.png)
+[!INCLUDE [active-directory-b2c-client-secret](../../includes/active-directory-b2c-client-secret.md)]
 
 Now you have an application with permissions to create, read, and update users in your Azure AD B2C tenant.
 

articles/active-directory-b2c/media/active-directory-b2c-user-migration/pre-migration-app-id-and-key.png

@@ -12,7 +12,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 07/31/2019
+ms.date: 10/01/2019
 ms.author: mimart
 ms.reviewer: arvinh
 ms.custom: aaddev;it-pro;seohack1

articles/active-directory/manage-apps/use-scim-to-provision-users-and-groups.md

@@ -813,7 +813,7 @@ For information about how to handle cancellation tokens, see the Azure Functions
 
 If your web app runs on multiple instances, a continuous WebJob runs on each instance, listening for triggers and calling functions. The various trigger bindings are designed to efficiently share work collaboratively across instances, so that scaling out to more instances allows you to handle more load.
 
-The queue and blob triggers automatically prevent a function from processing a queue message or blob more than once; functions don't have to be idempotent.
+While some triggers may result in double-processing, queue and blob storage triggers automatically prevent a function from processing a queue message or blob more than once. For more information, see [Designing for identical input](../azure-functions/functions-idempotent.md) in the Azure Functions documentation.
 
 The timer trigger automatically ensures that only one instance of the timer runs, so you don't get more than one function instance running at a given scheduled time.
 

articles/app-service/webjobs-sdk-how-to.md

@@ -9,13 +9,13 @@ manager: jeconnoc
 ms.assetid: 076f5f95-f8d2-42c7-b7fd-6798856ba0bb
 ms.service: azure-functions
 ms.topic: conceptual
-ms.date: 10/28/2018
+ms.date: 10/02/2019
 ms.author: glenga
 ---
 
 # Use Azure Functions to connect to an Azure SQL Database
 
-This article shows you how to use Azure Functions to create a scheduled job that connects to an Azure SQL Database instance. The function code cleans up rows in a table in the database. The new C# function is created based on a pre-defined timer trigger template in Visual Studio 2019. To support this scenario, you must also set a database connection string as an app setting in the function app. This scenario uses a bulk operation against the database. 
+This article shows you how to use Azure Functions to create a scheduled job that connects to an Azure SQL Database or Azure SQL Managed Instance. The function code cleans up rows in a table in the database. The new C# function is created based on a pre-defined timer trigger template in Visual Studio 2019. To support this scenario, you must also set a database connection string as an app setting in the function app. For Azure SQL Managed Instance you need to [enable public endpoint](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-public-endpoint-configure) to be able to connect from Azure Functions. This scenario uses a bulk operation against the database. 
 
 If this is your first experience working with C# Functions, you should read the [Azure Functions C# developer reference](functions-dotnet-class-library.md).
 
@@ -35,7 +35,7 @@ You need to get the connection string for the database you created when you comp
 
 1. Select **SQL Databases** from the left-hand menu, and select your database on the **SQL databases** page.
 
-1. Select **Connection strings** under **Settings** and copy the complete **ADO.NET** connection string.
+1. Select **Connection strings** under **Settings** and copy the complete **ADO.NET** connection string. For Azure SQL Managed Instance copy connection string for public endpoint.
 
     ![Copy the ADO.NET connection string.](./media/functions-scenario-database-table-cleanup/adonet-connection-string.png)
 

articles/azure-functions/functions-scenario-database-table-cleanup.md

@@ -11,7 +11,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: azure-government
-ms.date: 10/23/2018
+ms.date: 10/01/2019
 ms.author: jglixon
 
 ---
@@ -28,6 +28,7 @@ The following AI and Cognitive Services are generally available in Azure Governm
 - Speech
 - Translator Text
 - Language Understanding
+- QnA Maker
 - Azure Bot Service
 
 > [!IMPORTANT]
@@ -129,6 +130,16 @@ Variations in Azure Government:
 
 For more information, see [global Azure documentation](../cognitive-services/luis/what-is-luis.md) for Language Understanding.
 
+### QnA Maker
+
+Variations in Azure Government:
+
+- Endpoint: https://virginia.api.cognitive.microsoft.us/qnamaker/v4.0
+- QnA Maker portal: https://qnamaker.azure.us
+- Available SKUs: S0
+
+For more information, see [global Azure documentation](../cognitive-services/QnAMaker/Overview/overview.md) for QnA Maker.
+
 ## Azure Bot Service
 
 Variations in Azure Government:
@@ -158,8 +169,7 @@ Some Bot Service features available in the public cloud are not yet available in
 Commonly used services in bot applications that are currently unavailable in Azure Government:
 - Application Insights
 - Azure Search
-- QnA Maker Cognitive Service
-- Speech Services Cognitive Service
+- Speech Services
 
 For more information, see [global Azure documentation](https://aka.ms/botdocs/) for Bot Service.