Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr

Author: jjaygbay

includes/media/azure-app-configuration-role-assignment/add-role-assignment-button.png renamed to articles/azure-app-configuration/media/azure-app-configuration-role-assignment/add-role-assignment-button.png

@@ -27,7 +27,19 @@ The [Azure App Configuration](https://marketplace.visualstudio.com/items?itemNam
 
 ## Add role assignment
 
-[!INCLUDE [azure-app-configuration-role-assignment](../../includes/azure-app-configuration-role-assignment.md)]
+Assign the proper App Configuration role assignments to the credentials being used within the task so that the task can access the App Configuration store.
+
+1. Go to your target App Configuration store. 
+1. In the left menu, select **Access control (IAM)**.
+1. In the right pane, select **Add role assignments**.
+
+      :::image type="content"  border="true" source="./media/azure-app-configuration-role-assignment/add-role-assignment-button.png" alt-text="Screenshot shows the Add role assignments button.":::
+1. For **Role**, select **App Configuration Data Reader**. This role allows the task to read from the App Configuration store. 
+1. Select the service principal associated with the service connection that you created in the previous section.
+
+      :::image type="content"  border="true" source="./media/azure-app-configuration-role-assignment/add-role-assignment-data-reader.png" alt-text="Screenshot shows the Add role assignment dialog.":::
+1. Select **Review + assign**.
+1. If the store contains Key Vault references, go to relevant Key Vault and assign **Key Vault Secret User** role to the service principal created in the previous step. From the Key Vault menu, select **Access policies** and ensure [Azure role-based access control](../key-vault/general/rbac-guide.md) is selected as the permission model.
 
 ## Use in builds
 

includes/media/azure-app-configuration-role-assignment/add-role-assignment.png renamed to articles/azure-app-configuration/media/azure-app-configuration-role-assignment/add-role-assignment-data-owner.png

@@ -27,7 +27,18 @@ The [Azure App Configuration Push](https://marketplace.visualstudio.com/items?it
 
 ## Add role assignment
 
-[!INCLUDE [azure-app-configuration-role-assignment](../../includes/azure-app-configuration-role-assignment.md)]
+Assign the proper App Configuration role assignments to the credentials being used within the task so that the task can access the App Configuration store.
+
+1. Go to your target App Configuration store. 
+1. In the left menu, select **Access control (IAM)**.
+1. In the right pane, select **Add role assignments**.
+
+    :::image type="content"  border="true" source="./media/azure-app-configuration-role-assignment/add-role-assignment-button.png" alt-text="Screenshot shows the Add role assignments button.":::
+1. For **Role**, select **App Configuration Data Owner**. This role allows the task to read from and write to the App Configuration store.
+1. Select the service principal associated with the service connection that you created in the previous section.
+
+    :::image type="content"  border="true" source="./media/azure-app-configuration-role-assignment/add-role-assignment-data-owner.png" alt-text="Screenshot shows the Add role assignment dialog.":::
+1. Select **Review + assign**.
 
 ## Use in builds
 
@@ -50,7 +61,7 @@ This section will cover how to use the Azure App Configuration Push task in an A
 
 ## Use in releases
 
-This section will cover how to use the Azure App Configuration Push task in an Azure DevOps release pipelines.
+This section will cover how to use the Azure App Configuration Push task in an Azure DevOps release pipeline.
 
 1. Navigate to release pipeline page by selecting **Pipelines** > **Releases**. Documentation for release pipelines can be found [here](/azure/devops/pipelines/release).
 1. Choose an existing release pipeline. If you don’t have one, select **+ New** to create a new one.
@@ -111,4 +122,4 @@ Depending on the file content profile you selected, please refer to examples in
 
 **Why am I receiving a 409 error when attempting to push key-values to my configuration store?**
 
-A 409 Conflict error message will occur if the task tries to remove or overwrite a key-value that is locked in the App Configuration store.
+A 409 Conflict error message will occur if the task tries to remove or overwrite a key-value that is locked in the App Configuration store.

articles/azure-app-configuration/media/azure-app-configuration-role-assignment/add-role-assignment-data-reader.png

@@ -2,7 +2,7 @@
 title: Azure Resource Manager overview
 description: Describes how to use Azure Resource Manager for deployment, management, and access control of resources on Azure.
 ms.topic: overview
-ms.date: 10/05/2022
+ms.date: 02/28/2023
 ms.custom: contperf-fy21q1,contperf-fy21q3-portal
 ---
 # What is Azure Resource Manager?
@@ -86,6 +86,8 @@ There are some important factors to consider when defining your resource group:
   You may be wondering, "Why does a resource group need a location? And, if the resources can have different locations than the resource group, why does the resource group location matter at all?"
 
   The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region.
+
+  To ensure state consistency for the resource group, all [control plane operations](./control-plane-and-data-plane.md) are routed through the resource group's location. When selecting a resource group location, we recommend that you select a location close to where your control operations originate. Typically, this location is the one closest to your current location. This routing requirement only applies to control plane operations for the resource group. It doesn't affect requests that are sent to your applications.
 
   If a resource group's region is temporarily unavailable, you can't update resources in the resource group because the metadata is unavailable. The resources in other regions will still function as expected, but you can't update them. This condition doesn't apply to global resources like Azure Content Delivery Network, Azure DNS, Azure DNS Private Zones, Azure Traffic Manager, and Azure Front Door.
 

articles/azure-app-configuration/pull-key-value-devops-pipeline.md

@@ -19,7 +19,7 @@ ms.author: eur
 |French (France)|`fr-FR`|  
 |German (Germany)|`de-DE`<sup>1</sup>|
 |Japanese (Japan)|`ja-JP`<sup>1</sup>|
-|Norwegian (Bokmål, Norway)|`nb-NO`<sup>1</sup>|
+|Norwegian Bokmål (Norway)|`nb-NO`<sup>1</sup>|
 |Spanish (Mexico)|`es-MX`<sup>1</sup> | 
 |Spanish (Spain)|`es-ES` | 
 |Vietnamese (Vietnam)|`vi-VN`<sup>1</sup> |

articles/azure-app-configuration/push-kv-devops-pipeline.md

@@ -2,7 +2,7 @@
 author: eric-urban
 ms.service: cognitive-services
 ms.subservice: speech-service
-ms.date: 02/01/2023
+ms.date: 02/23/2023
 ms.topic: include
 ms.author: eur
 ---
@@ -37,7 +37,7 @@ ms.author: eur
 | `cs-CZ` | Czech (Czechia) | Audio + human-labeled transcript<br/><br/>Plain text<br/><br/>Pronunciation |
 | `cy-GB` | Welsh (United Kingdom) | Plain text |
 | `da-DK` | Danish (Denmark) | Audio + human-labeled transcript<br/><br/>Plain text<br/><br/>Pronunciation |
-| `de-AT` | German (Austria) | Plain text<br/><br/>Structured text<br/><br/>Pronunciation |
+| `de-AT` | German (Austria) | Audio + human-labeled transcript<br/><br/>Plain text<br/><br/>Structured text<br/><br/>Pronunciation |
 | `de-CH` | German (Switzerland) | Audio + human-labeled transcript<br/><br/>Plain text<br/><br/>Pronunciation |
 | `de-DE` | German (Germany) | Audio + human-labeled transcript<br/><br/>Plain text<br/><br/>Structured text<br/><br/>Pronunciation<br/><br/>Phrase list |
 | `el-GR` | Greek (Greece) | Plain text |
@@ -116,7 +116,7 @@ ms.author: eur
 | `ms-MY` | Malay (Malaysia) | Audio + human-labeled transcript<br/><br/>Plain text |
 | `mt-MT` | Maltese (Malta) | Plain text |
 | `my-MM` | Burmese (Myanmar) | Plain text |
-| `nb-NO` | Norwegian (Bokmål, Norway) | Audio + human-labeled transcript<br/><br/>Plain text |
+| `nb-NO` | Norwegian Bokmål (Norway) | Audio + human-labeled transcript<br/><br/>Plain text |
 | `ne-NP` | Nepali (Nepal) | Plain text |
 | `nl-BE` | Dutch (Belgium) | Plain text |
 | `nl-NL` | Dutch (Netherlands) | Audio + human-labeled transcript<br/><br/>Plain text<br/><br/>Pronunciation |

articles/azure-resource-manager/management/overview.md

@@ -41,7 +41,7 @@ ms.author: eur
 | `ja-JP` | Japanese (Japan) | Custom Neural Voice Pro<br/><br/>Custom Neural Voice Lite (Preview)<br/><br/>Cross-lingual voice (Preview) |
 | `ko-KR` | Korean (Korea) | Custom Neural Voice Pro<br/><br/>Custom Neural Voice Lite (Preview)<br/><br/>Cross-lingual voice (Preview) |
 | `ms-MY` | Malay (Malaysia) | Custom Neural Voice Pro |
-| `nb-NO` | Norwegian Bokmål (Norway) | Custom Neural Voice Pro |
+| `nb-NO` | Norwegian Bokmål (Norway) | Custom Neural Voice Pro |
 | `nl-NL` | Dutch (Netherlands) | Custom Neural Voice Pro |
 | `pl-PL` | Polish (Poland) | Custom Neural Voice Pro |
 | `pt-BR` | Portuguese (Brazil) | Custom Neural Voice Pro<br/><br/>Custom Neural Voice Lite (Preview)<br/><br/>Cross-lingual voice (Preview) |