Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-troubleshoot-owner-remove

Author: rolyon

articles/app-service/overview-managed-identity.md

@@ -472,29 +472,34 @@ To learn more about configuring AzureServiceTokenProvider and the operations it
 
 For Java applications and functions, the simplest way to work with a managed identity is through the [Azure SDK for Java](https://github.com/Azure/azure-sdk-for-java). This section shows you how to get started with the library in your code.
 
-1. Add a reference to the [Azure SDK library](https://mvnrepository.com/artifact/com.microsoft.azure/azure). For Maven projects, you might add this snippet to the `dependencies` section of the project's POM file:
+1. Add a reference to the [Azure SDK library](https://mvnrepository.com/artifact/com.azure.resourcemanager/azure-resourcemanager). For Maven projects, you might add this snippet to the `dependencies` section of the project's POM file:
 
     ```xml
     <dependency>
-        <groupId>com.microsoft.azure</groupId>
-        <artifactId>azure</artifactId>
-        <version>1.23.0</version>
+      <groupId>com.azure.resourcemanager</groupId>
+      <artifactId>azure-resourcemanager</artifactId>
+      <version>2.10.0</version>
     </dependency>
     ```
 
-2. Use the `AppServiceMSICredentials` object for authentication. This example shows how this mechanism may be used for working with Azure Key Vault:
+2. Use the `ManagedIdentityCredential` object for authentication. This example shows how this mechanism may be used for working with Azure Key Vault:
 
     ```java
-    import com.microsoft.azure.AzureEnvironment;
-    import com.microsoft.azure.management.Azure;
-    import com.microsoft.azure.management.keyvault.Vault
+    import com.azure.core.management.AzureEnvironment;
+    import com.azure.core.management.profile.AzureProfile;
+    import com.azure.identity.ManagedIdentityCredential;
+    import com.azure.identity.ManagedIdentityCredentialBuilder;
+    import com.azure.resourcemanager.AzureResourceManager;
+    import com.azure.resourcemanager.keyvault.models.Vault;
     //...
-    Azure azure = Azure.authenticate(new AppServiceMSICredentials(AzureEnvironment.AZURE))
-            .withSubscription(subscriptionId);
-    Vault myKeyVault = azure.vaults().getByResourceGroup(resourceGroup, keyvaultName);
+    AzureProfile azureProfile = new AzureProfile(AzureEnvironment.AZURE);
+    ManagedIdentityCredential managedIdentityCredential = new ManagedIdentityCredentialBuilder().build();
+    AzureResourceManager azure = AzureResourceManager.authenticate(managedIdentityCredential, azureProfile).withSubscription("subscription");
 
-    ```
+    Vault vault = azure.vaults().getByResourceGroup("resourceGroup", "keyVaultName");
 
+    ```
+For more information on how to use the Azure SDK for Java, please refer to this [quickstart guide](https://aka.ms/azsdk/java/mgmt). To learn more about Azure Identiy and authentication and Managed Identity in general, please visit [this guide](https://github.com/Azure/azure-sdk-for-java/wiki/Azure-Identity-Examples#authenticating-a-user-assigned-managed-identity-with-defaultazurecredential)
 
 ## <a name="remove"></a>Remove an identity
 
@@ -527,4 +532,4 @@ Update-AzFunctionApp -Name $functionAppName -ResourceGroupName $resourceGroupNam
 - [Call Microsoft Graph securely using a managed identity](scenario-secure-app-access-microsoft-graph-as-app.md)
 - [Connect securely to services with Key Vault secrets](tutorial-connect-msi-key-vault.md)
 
-[Microsoft.Azure.Services.AppAuthentication reference]: /dotnet/api/overview/azure/service-to-service-authentication
+[Microsoft.Azure.Services.AppAuthentication reference]: /dotnet/api/overview/azure/service-to-service-authentication

articles/azure-cache-for-redis/cache-how-to-scale.md

@@ -152,6 +152,7 @@ No, your cache name and keys are unchanged during a scaling operation.
 - When you scale a **Standard** cache to a different size or to a **Premium** cache, one of the replicas is shut down and reprovisioned to the new size and the data transferred over, and then the other replica does a failover before it's reprovisioned, similar to the process that occurs during a failure of one of the cache nodes.
 - When you scale out a clustered cache, new shards are provisioned and added to the Redis server cluster. Data is then resharded across all shards.
 - When you scale in a clustered cache, data is first resharded and then cluster size is reduced to required shards.
+- In some cases, such as scaling or migrating your cache to a different cluster, the underlying IP address of the cache can change. The DNS records for the cache changes and is transparent to most applications. However, if you use an IP address to configure the connection to your cache, or to configure NSGs, or firewalls allowing traffic to the cache, your application might have trouble connecting sometime after that the DNS record updates.
 
 ### Will I lose data from my cache during scaling?
 

articles/azure-cache-for-redis/quickstart-create-redis-enterprise.md

@@ -16,6 +16,8 @@ The Azure Cache for Redis Enterprise tiers provide fully integrated and managed
 * Enterprise, which uses volatile memory (DRAM) on a virtual machine to store data
 * Enterprise Flash, which uses both volatile and non-volatile memory (NVMe or SSD) to store data.
 
+Both Enterprise and Enterprise Flash support open-source Redis 6 and some new features that aren't yet available in the Basic, Standard, or Premium tiers. The supported features include some Redis modules that enable additional features like search, bloom filters, and time series.  
+
 ## Prerequisites
 
 You'll need an Azure subscription before you begin. If you don't have one, create an [account](https://azure.microsoft.com/). For more information, see [special considerations for Enterprise tiers](cache-overview.md#special-considerations-for-enterprise-tiers).

articles/virtual-desktop/autoscale-scaling-plan.md

@@ -111,7 +111,6 @@ To create and assign the custom role to your subscription with the Azure portal:
 				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/delete"
 				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/read"
 				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/sendMessage/action"
-				 "Microsoft.DesktopVirtualization/hostpools/sessionhosts/usersessions/read"
     ```
 
 5. When you're finished, select **Ok**.

includes/disk-storage-zrs-limitations.md

@@ -14,4 +14,4 @@ ZRS for managed disks have the following restrictions:
 
 - Only supported with premium solid-state drives (SSD) and standard SSDs.
 - Currently available only in the West US 2, West Europe, North Europe, and France Central regions.
-- Can't currently be used with Azure Backup or Azure Site Recovery.
+- Can't currently be used with Azure Site Recovery.