credentials edits

Author: ktoliver

articles/azure-functions/durable/durable-functions-configure-durable-functions-with-credentials.md

@@ -1,17 +1,17 @@
 ---
-title: "Quickstart: Authenticate a durable function app by using Microsoft Entra ID"
-description: Authenticate a durable function app in Azure Functions by using either managed identity credentials or client secret credentials in Microsoft Entra ID.
+title: "Quickstart: Authenticate a Durable Functions app by using Microsoft Entra ID"
+description: Authenticate a Durable Functions app in Azure Functions by using either managed identity credentials or client secret credentials in Microsoft Entra ID.
 author: naiyuantian
 ms.topic: quickstart
 ms.date: 02/01/2023
 ms.author: azfuncdf
 ---
 
-# Quickstart: Authenticate a durable function app by using Microsoft Entra ID
+# Quickstart: Authenticate a Durable Functions app by using Microsoft Entra ID
 
 [Microsoft Entra ID](/entra/fundamentals/whatis) is a cloud-based identity and access management service. Identity-based connections allow Durable Functions, a feature of Azure Functions, to make authorized requests against Microsoft Entra-protected resources, such as an Azure Storage account, without using manually managed secrets. When Durable Functions uses the default Azure storage provider, it must authenticate against an Azure storage account.
 
-In this quickstart, we demonstrate how to configure a durable function app to use two different kinds of identity-based connections:
+In this quickstart, you complete the steps to set up a Durable Functions app to use two different kinds of identity-based connections:
 
 * Managed identity credentials (recommended)
 * Client secret credentials
@@ -22,10 +22,10 @@ If you don't have an Azure account, create a [free account](https://azure.micros
 
 To complete this quickstart, you need:
 
-* An existing durable function project created in the Azure portal or a local durable function project deployed to Azure.
-* Familiarity running a durable function app in Azure.
+* An existing Durable Functions project created in the Azure portal or a local Durable Functions project deployed to Azure.
+* Familiarity running a Durable Functions app in Azure.
 
-If you don't have an existing durable function project deployed in Azure, we recommend that you start with one of the following quickstarts:
+If you don't have an existing Durable Functions project deployed in Azure, we recommend that you start with one of the following quickstarts:
 
 * [Create your first Durable Functions app - C#](durable-functions-isolated-create-first-csharp.md)
 * [Create your first Durable Functions app - JavaScript](quickstart-js-vscode.md)
@@ -60,7 +60,7 @@ Before you can use your app's managed identity, make some changes to the app con
 
 1. In the list of settings, select **AzureWebJobsStorage** and select the **Delete** icon.
 
-   ![Screenshot of the default storage settings and deleting AzureWebJobsStorage.](./media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-01.png)
+   :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-01.png" alt-text="Screenshot that shows default storage settings and deleting AzureWebJobsStorage.":::
 
 1. Add a setting to link your Azure storage account to the application.
 
@@ -91,7 +91,7 @@ Before you can use your app's managed identity, make some changes to the app con
 
      You can get the values for these URI variables in the storage account on the **Endpoints** tab.
 
-    ![Screenshot that shows an example of an endpoint as a specific service URL.](media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-02.png)
+     :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-02.png" alt-text="Screenshot that shows an example of an endpoint as a specific service URI.":::
 
 1. Finish your managed identity configuration:
 
@@ -103,11 +103,11 @@ Before you can use your app's managed identity, make some changes to the app con
 
      * For **AzureWebJobsStorage__clientId**, get this GUID value from the Microsoft Entra admin center.
 
-     ![Screenshot that shows the user identity client ID.](media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-03.png)
+     :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-03.png" alt-text="Screenshot that shows the user identity client ID.":::
 
 ## Configure your app to use client secret credentials
 
-Registering a client application in Microsoft Entra ID is another way that you can configure access to an Azure service for your durable function app. In the following steps, you use client secret credentials for authentication to your Azure Storage account. Function apps can use this method both locally and in Azure. Using a client secret credential is *less recommended* than using managed identity credentials because a client secret is more complicated to configure and manage. A client secret credential also requires sharing a secret credential with the Azure Functions service.
+Registering a client application in Microsoft Entra ID is another way that you can configure access to an Azure service for your Durable Functions app. In the following steps, you use client secret credentials for authentication to your Azure Storage account. Function apps can use this method both locally and in Azure. Using a client secret credential is *less recommended* than using managed identity credentials because a client secret is more complicated to configure and manage. A client secret credential also requires sharing a secret credential with the Azure Functions service.
 
 <a name='register-a-client-application-on-azure-active-directory'></a>
 
@@ -127,7 +127,7 @@ Registering a client application in Microsoft Entra ID is another way that you c
 
       The secret value doesn't appear again after you leave the pane, so be sure that you *copy the secret and save it*.
 
-   ![Screenshot of the Add a client secret pane.](media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-01.png)
+   :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-01.png" alt-text="Screenshot that shows the Add a client secret pane.":::
 
 ### Assign access roles to your application
 
@@ -143,11 +143,11 @@ To add the roles:
 
 1. In the resource menu, select **Access Control (IAM)**, and then select **Add role assignment**.
 
-   ![Screenshot of the Access control pane with Add role assignment highlighted.](media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-02.png)
+   :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-02.png" alt-text="Screenshot that shows the Access control pane with Add role assignment highlighted.":::
 
 1. Select the role you want to add, select **Next**, and then search for your application. Review the role, and then add the role.
 
-   ![Screenshot of the role assignment pane.](media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-03.png)
+   :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-03.png" alt-text="Screenshot that shows the role assignment pane.":::
 
 ### Configure the client secret
 
@@ -170,7 +170,7 @@ In the Azure portal, run and test the application. To run and test the app local
    * **Non-Azure cloud**: If your application runs in a cloud outside of Azure, you must add a specific service URI (endpoint) for the storage account instead of an account name.
 
      > [!NOTE]
-     > If you're using [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from public Azure, you must use the option to provide a specific service URL. For more information about using Azure Storage with Azure Government, see [Develop by using the Storage API in Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md).
+     > If you use [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from public Azure, you must use the option to provide a specific service URL. For more information about using Azure Storage with Azure Government, see [Develop by using the Storage API in Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md).
 
      * `AzureWebJobsStorage__<blobServiceUri>`
 
@@ -186,7 +186,7 @@ In the Azure portal, run and test the application. To run and test the app local
 
      You can get the values for these URI variables in the storage account on the **Endpoints** tab.
 
-     ![Screenshot that shows an example of an endpoint as a specific service URI.](media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-02.png)
+     :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-02.png" alt-text="Screenshot that shows an example of an endpoint as a specific service URI.":::
 
 1. To add client secret credentials, specify the following values:
 
@@ -196,6 +196,6 @@ In the Azure portal, run and test the application. To run and test the app local
 
    * **AzureWebJobsStorage__tenantId**: The tenant ID that the Microsoft Entra application is registered in. Get this GUID value on the Microsoft Entra application pane.
 
-   The values to use for the client ID and the tenant ID appear on your client application’s overview pane. The client secret value is the one that you saved in an earlier step. The client secret value isn't available after the page is refreshed.
+   The values to use for the client ID and the tenant ID appear on your client application Overview pane. The client secret value is the one that you saved in an earlier step. The client secret value isn't available after the page is refreshed.
 
-   ![Screenshot that shows the tenant ID and client ID on a Microsoft Entra application pane.](media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-04.png)
+   :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-04.png" alt-text="Screenshot that shows the tenant ID and client ID on a Microsoft Entra application pane.":::