Merge pull request #205545 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: TimShererWithAquent

articles/azure-app-configuration/use-key-vault-references-dotnet-core.md

@@ -104,7 +104,7 @@ To add a secret to the vault, you need to take just a few additional steps. In t
     using Azure.Identity;
     ```
 
-1. Update the `CreateWebHostBuilder` method to use App Configuration by calling the `config.AddAzureAppConfiguration` method. Include the `ConfigureKeyVault` option, and pass the correct credentials to your Key Vault.
+1. Update the `CreateWebHostBuilder` method to use App Configuration by calling the `config.AddAzureAppConfiguration` method. Include the `ConfigureKeyVault` option, and pass the correct credential to your Key Vault using the `SetCredential` method. If you have multiple Key Vaults, the same credential will be used for all of them. If your Key Vaults require different credentials, you can set them using `Register` or `SetSecretResolver` methods from the [`AzureAppConfigurationKeyVaultOptions`](/dotnet/api/microsoft.extensions.configuration.azureappconfiguration.azureappconfigurationkeyvaultoptions) class.
 
      #### [.NET Core 5.x](#tab/core5x)
 

articles/azure-vmware/concepts-identity.md

@@ -3,13 +3,13 @@ title: Concepts - Identity and access
 description: Learn about the identity and access concepts of Azure VMware Solution
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 06/06/2022
+ms.date: 07/21/2022
 ms.custom: references_regions
 ---
 
 # Azure VMware Solution identity concepts
 
-Azure VMware Solution private clouds are provisioned with a vCenter Server and NSX-T Manager. You'll use vCenter to manage virtual machine (VM) workloads and NSX-T Manager to manage and extend the private cloud. The CloudAdmin role is used for vCenter Server and the administrator role (with restricted permissions) is used for NSX-T Manager.
+Azure VMware Solution private clouds are provisioned with a vCenter Server and NSX-T Manager. You'll use vCenter to manage virtual machine (VM) workloads and NSX-T Manager to manage and extend the private cloud. The CloudAdmin role is used for vCenter Server and the CloudAdmin role (with restricted permissions) is used for NSX-T Manager.
 
 ## vCenter Server access and identity
 
@@ -18,9 +18,9 @@ Azure VMware Solution private clouds are provisioned with a vCenter Server and N
 > [!IMPORTANT]
 > Azure VMware Solution offers custom roles on vCenter Server but currently doesn't offer them on the Azure VMware Solution portal. For more information, see the [Create custom roles on vCenter Server](#create-custom-roles-on-vcenter-server) section later in this article.
 
-### View the vCenter privileges
+### View the vCenter Server privileges
 
-You can view the privileges granted to the Azure VMware Solution CloudAdmin role on your Azure VMware Solution private cloud vCenter.
+You can view the privileges granted to the Azure VMware Solution CloudAdmin role on your Azure VMware Solution private cloud vCenter Server.
 
 1. Sign into the vSphere Client and go to **Menu** > **Administration**.
 1. Under **Access Control**, select **Roles**.
@@ -89,28 +89,28 @@ To prevent creating roles that can't be assigned or deleted, clone the CloudAdmi
 
 ## NSX-T Manager access and identity
 
-When a private cloud is provisioned using Azure portal, software defined data center (SDDC) management components like vCenter and NSX-T Manager are provisioned for customers.
+When a private cloud is provisioned using Azure portal, software-defined data center (SDDC) management components like vCenter Server and NSX-T Manager are provisioned for customers.
 
-Microsoft is responsible for the lifecycle management of NSX-T appliances like NSX-T Managers and NSX-T Edges. They're responsible for bootstrapping network configuration, like creating the Tier-0 gateway.
+Microsoft is responsible for the lifecycle management of NSX-T appliances like NSX-T Managers and NSX-T Data Center Edges. They're responsible for bootstrapping network configuration, like creating the Tier-0 gateway.
 
-You're responsible for NSX-T software-defined networking (SDN) configuration, for example:
+You're responsible for NSX-T Data Center software-defined networking (SDN) configuration, for example:
 
 - Network segments
 - Other Tier-1 gateways
 - Distributed firewall rules
 - Stateful services like gateway firewall
 - Load balancer on Tier-1 gateways
 
-You can access NSX-T Manager using the built-in local user "admin" assigned to **Enterprise admin** role that gives full privileges to a user to manage NSX-T. While Microsoft manages the lifecycle of NSX-T, certain operations aren't allowed by a user. Operations not allowed include editing the configuration of host and edge transport nodes or starting an upgrade. For new users, Azure VMware Solution deploys them with a specific set of permissions needed by that user. The purpose is to provide a clear separation of control between the Azure VMware Solution control plane configuration and Azure VMware Solution private cloud user.  
+You can access NSX-T Manager using the built-in local user "cloudadmin" assigned to a custom role that gives limited privileges to a user to manage NSX-T Data Center. While Microsoft manages the lifecycle of NSX-T Data Center, certain operations aren't allowed by a user. Operations not allowed include editing the configuration of host and edge transport nodes or starting an upgrade. For new users, Azure VMware Solution deploys them with a specific set of permissions needed by that user. The purpose is to provide a clear separation of control between the Azure VMware Solution control plane configuration and Azure VMware Solution private cloud user.  
 
-For new private cloud deployments, NSX-T access will be provided with a built-in local user cloud admin assigned to the **cloudadmin** role with a specific set of permissions to use NSX-T functionality for workloads.
+For new private cloud deployments, NSX-T Data Center access will be provided with a built-in local user cloudadmin assigned to the **cloudadmin** role with a specific set of permissions to use NSX-T Data Center functionality for workloads.
 
-### NSX-T cloud admin user permissions
+### NSX-T Data Center cloudadmin user permissions
 
-The following permissions are assigned to the **cloudadmin** user in Azure VMware Solution NSX-T.
+The following permissions are assigned to the **cloudadmin** user in Azure VMware Solution NSX-T Data Center.
 
 > [!NOTE]
-> **NSX-T cloudadmin user** on Azure VMware Solution is not the same as the **cloudadmin user** mentioned in the VMware product documentation.
+> **NSX-T Data Center cloudadmin user** on Azure VMware Solution is not the same as the **cloudadmin user** mentioned in the VMware product documentation.
 
 | Category        | Type                  | Operation                                                            | Permission                                                       |
 |-----------------|-----------------------|----------------------------------------------------------------------|------------------------------------------------------------------|
@@ -130,28 +130,28 @@ The following permissions are assigned to the **cloudadmin** user in Azure VMwar
 | System          | Configuration<br>Settings<br>Settings<br>Settings              | Identity firewall<br>Users and Roles<br>Certificate Management (Service Certificate only)<br>User Interface Settings   | Full Access<br>Full Access<br>Full Access<br>Full Access                          |
 | System          | All other    |                                                                      | Read-only                                                        |
 
-You can view the permissions granted to the Azure VMware Solution cloudadmin role on your Azure VMware Solution private cloud NSX-T.
+You can view the permissions granted to the Azure VMware Solution cloudadmin role on your Azure VMware Solution private cloud NSX-T Data Center.
 
 1. Log in to the NSX-T Manager.
 1. Navigate to **Systems** and locate **Users and Roles**.
 1. Select and expand the **cloudadmin** role, found under **Roles**.
 1. Select a category like, Networking or Security, to view the specific permissions.
 
 > [!NOTE]
-> **Private clouds created before June 2022** will switch from **admin** role to **cloudadmin** role. You'll receive a notification through Azure Service Health that includes the timeline of this change so you can change the NSX-T credentials you've used for other integration.
+> **Private clouds created before June 2022** will switch from **admin** role to **cloudadmin** role. You'll receive a notification through Azure Service Health that includes the timeline of this change so you can change the NSX-T Data Center credentials you've used for other integration.
 
-## NSX-T LDAP integration for role based access control (RBAC)
+## NSX-T Data Center LDAP integration for role based access control (RBAC)
 
-In an Azure VMware Solution deployment, the NSX-T can be integrated with external LDAP directory service to add remote directory users or group, and assign them an NSX-T RBAC role, like on-premises deployment.  For more information on how to enable NSX-T LDAP integration, see the [VMware product documentation](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-DB5A44F1-6E1D-4E5C-8B50-D6161FFA5BD2.html).
+In an Azure VMware Solution deployment, the NSX-T Data Center can be integrated with external LDAP directory service to add remote directory users or group, and assign them an NSX-T Data Center RBAC role, like on-premises deployment.  For more information on how to enable NSX-T Data Center LDAP integration, see the [VMware product documentation](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-DB5A44F1-6E1D-4E5C-8B50-D6161FFA5BD2.html).
 
-Unlike on-premises deployment, not all pre-defined NSX-T RBAC roles are supported with Azure VMware solution to keep Azure VMware Solution IaaS control plane config management separate from tenant network and security configuration. Please see the next section, Supported NSX-T RBAC roles, for more details.
+Unlike on-premises deployment, not all pre-defined NSX-T Data Center RBAC roles are supported with Azure VMware solution to keep Azure VMware Solution IaaS control plane config management separate from tenant network and security configuration. Please see the next section, Supported NSX-T Data Center RBAC roles, for more details.
 
 > [!NOTE]
-> NSX-T LDAP Integration supported only with SDDC’s with NSX-T “cloudadmin” user.
+> NSX-T LDAP Integration supported only with SDDC’s with NSX-T Data Center “cloudadmin” user.
 
-### Supported and unsupported NSX-T RBAC roles  
+### Supported and unsupported NSX-T Data Center RBAC roles  
 
- In an Azure VMware Solution deployment, the following NSX-T predefined RBAC roles are supported with LDAP integration:
+ In an Azure VMware Solution deployment, the following NSX-T Data Center predefined RBAC roles are supported with LDAP integration:
 
 - Auditor
 - Cloudadmin
@@ -160,17 +160,17 @@ Unlike on-premises deployment, not all pre-defined NSX-T RBAC roles are supporte
 - VPN Admin
 - Network Operator
 
- In an Azure VMware Solution deployment, the following NSX-T predefined RBAC roles are not supported with LDAP integration:
+ In an Azure VMware Solution deployment, the following NSX-T Data Center predefined RBAC roles are not supported with LDAP integration:
 
 - Enterprise Admin
 - Network AdminSecurity Admin
 - Netx Partner Admin
 - GI Partner Admin
 
-You can create custom roles in NSX-T with permissions lesser than or equal to Cloudadmin role created by Microsoft. Following are examples on how to create a supported "Network Admin" and "Security Admin" role.
+You can create custom roles in NSX-T Data Center with permissions lesser than or equal to CloudAdmin role created by Microsoft. Following are examples on how to create a supported "Network Admin" and "Security Admin" role.
 
 > [!NOTE]
-> Custom role creation will fail if you assign a permission not allowed by Cloudadmin role.
+> Custom role creation will fail if you assign a permission not allowed by CloudAdmin role.
 
 #### Create “AVS network admin” role
 
@@ -206,10 +206,10 @@ You can create custom roles in NSX-T with permissions lesser than or equal to Cl
 4. **Apply** the changes and **Save** the Role.
 
 > [!NOTE]
-> The NSX-T **System** > **Identity Firewall AD** configuration option isn't supported by the NSX custom role. The recommendation is to assign the **Security Operator** role to the user with the custom role to allow managing the Identity Firewall (IDFW) feature for that user.
+> The NSX-T Data Center **System** > **Identity Firewall AD** configuration option isn't supported by the NSX custom role. The recommendation is to assign the **Security Operator** role to the user with the custom role to allow managing the Identity Firewall (IDFW) feature for that user.
 
 > [!NOTE]
-> The NSX-T Traceflow feature isn't supported by NSX-T custom role. The recommendation is to assign the **Auditor** role to the user along with above custom role to enable Traceflow feature for that user.
+> The NSX-T Data Center Traceflow feature isn't supported by NSX-T Data Center custom role. The recommendation is to assign the **Auditor** role to the user along with above custom role to enable Traceflow feature for that user.
 
 ## Next steps
 

articles/azure-vmware/concepts-run-command.md

@@ -9,7 +9,7 @@ ms.date: 09/17/2021
 
 # Run command in Azure VMware Solution 
 
-In Azure VMware Solution, vCenter Server has a built-in local user called *cloudadmin* assigned to the CloudAdmin role. The CloudAdmin role has vCenter Server [privileges](concepts-identity.md#view-the-vcenter-privileges) that differ from other VMware cloud solutions and on-premises deployments. The Run command feature lets you perform operations that would normally require elevated privileges through a collection of PowerShell cmdlets. 
+In Azure VMware Solution, vCenter Server has a built-in local user called *cloudadmin* assigned to the CloudAdmin role. The CloudAdmin role has vCenter Server [privileges](concepts-identity.md#vcenter-server-access-and-identity) that differ from other VMware cloud solutions and on-premises deployments. The Run command feature lets you perform operations that would normally require elevated privileges through a collection of PowerShell cmdlets. 
 
 Azure VMware Solution supports the following operations:
 

articles/azure-vmware/configure-storage-policy.md

@@ -121,10 +121,6 @@ You'll run the `Set-LocationStoragePolicy` cmdlet to Modify vSAN based storage p
 You'll run the `Set-ClusterDefaultStoragePolicy` cmdlet to specify default storage policy for a cluster,
 
 
->[!NOTE]
->Changing the storage policy of the default management cluster (Cluster-1) isn't allowed.
-
-
 1. Select **Run command** > **Packages** > **Set-ClusterDefaultStoragePolicy**.
 
 1. Provide the required values or change the default values, and then select **Run**.

articles/cognitive-services/Translator/document-translation/client-sdks.md

@@ -23,7 +23,7 @@ To get started, you'll need:
 
 * An active [**Azure account**](https://azure.microsoft.com/free/cognitive-services/).  If you don't have one, you can [**create a free account**](https://azure.microsoft.com/free/).
 
-* A [**single-service Translator resource**](https://portal.azure.com/#create/Microsoft.CognitiveServicesTextTranslation) (**not** a multi-service Cognitive Services resource).
+* A [**single-service Translator resource**](https://portal.azure.com/#create/Microsoft.CognitiveServicesTextTranslation) (**not** a multi-service Cognitive Services resource). Choose **Global** unless your business or application requires a specific region. Select the **Standard S1** pricing tier to get started (document translation is not supported for the free tier).
 
 * An [**Azure blob storage account**](https://portal.azure.com/#create/Microsoft.StorageAccount-ARM). You'll [**create containers**](../../../storage/blobs/storage-quickstart-blobs-portal.md#create-a-container) in your Azure blob storage account for your source and target files:
 
@@ -180,47 +180,47 @@ pip install azure-ai-translation-document==1.0.0
 Create a new Python application in your preferred editor or IDE. Then import the following libraries.
 
 ```python
-    import os
-    from azure.core.credentials import AzureKeyCredential
-    from azure.ai.translation.document import DocumentTranslationClient
+import os
+from azure.core.credentials import AzureKeyCredential
+from azure.ai.translation.document import DocumentTranslationClient
 ```
 
 Create variables for your resource key, custom endpoint, sourceUrl, and targetUrl. For
 more information, *see*  [Custom domain name and key](get-started-with-document-translation.md#your-custom-domain-name-and-key)
 
 ```python
- key = "<your-key>"
- endpoint = "<your-custom-endpoint>"
- sourceUrl = "<your-container-sourceUrl>"
- targetUrl = "<your-container-targetUrl>"
+key = "<your-key>"
+endpoint = "<your-custom-endpoint>"
+sourceUrl = "<your-container-sourceUrl>"
+targetUrl = "<your-container-targetUrl>"
 ```
 
 ### Translate a document or batch files
 
 ```python
 client = DocumentTranslationClient(endpoint, AzureKeyCredential(key))
 
-    poller = client.begin_translation(sourceUrl, targetUrl, "fr")
-    result = poller.result()
-
-    print("Status: {}".format(poller.status()))
-    print("Created on: {}".format(poller.details.created_on))
-    print("Last updated on: {}".format(poller.details.last_updated_on))
-    print("Total number of translations on documents: {}".format(poller.details.documents_total_count))
-
-    print("\nOf total documents...")
-    print("{} failed".format(poller.details.documents_failed_count))
-    print("{} succeeded".format(poller.details.documents_succeeded_count))
-
-    for document in result:
-        print("Document ID: {}".format(document.id))
-        print("Document status: {}".format(document.status))
-        if document.status == "Succeeded":
-            print("Source document location: {}".format(document.source_document_url))
-            print("Translated document location: {}".format(document.translated_document_url))
-            print("Translated to language: {}\n".format(document.translated_to))
-        else:
-            print("Error Code: {}, Message: {}\n".format(document.error.code, document.error.message))
+poller = client.begin_translation(sourceUrl, targetUrl, "fr")
+result = poller.result()
+
+print("Status: {}".format(poller.status()))
+print("Created on: {}".format(poller.details.created_on))
+print("Last updated on: {}".format(poller.details.last_updated_on))
+print("Total number of translations on documents: {}".format(poller.details.documents_total_count))
+
+print("\nOf total documents...")
+print("{} failed".format(poller.details.documents_failed_count))
+print("{} succeeded".format(poller.details.documents_succeeded_count))
+
+for document in result:
+    print("Document ID: {}".format(document.id))
+    print("Document status: {}".format(document.status))
+    if document.status == "Succeeded":
+        print("Source document location: {}".format(document.source_document_url))
+        print("Translated document location: {}".format(document.translated_document_url))
+        print("Translated to language: {}\n".format(document.translated_to))
+    else:
+        print("Error Code: {}, Message: {}\n".format(document.error.code, document.error.message))
 ```
 
 That's it! You've created a program to translate documents in a storage container using the Python client library.

articles/machine-learning/how-to-responsible-ai-dashboard-ui.md

@@ -46,7 +46,7 @@ After you picked your dataset, select your modeling task type.
 :::image type="content" source="./media/how-to-responsible-ai-dashboard-ui/modeling.png" alt-text="Screenshot of the wizard on modeling task type." lightbox= "./media/how-to-responsible-ai-dashboard-ui/modeling.png":::
 
 > [!NOTE]
-> The wizard only supports models with MLflow format and sci-kit learn flavor.
+> The wizard only supports models with MLflow format and scikit-learn flavor.
 
 ## Select your dashboard components