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

Author: Yulin Li

articles/active-directory/authentication/how-to-mfa-server-migration-utility.md

@@ -341,9 +341,8 @@ Content-Type: application/json
 
 
 #### Response
->[!NOTE] 
->The response object shown here might be shortened for readability.
-
+>**Note:** The response object shown here might be shortened for readability.
+<!-- {
   "blockType": "response",
   "truncated": true,
   "@odata.type": "microsoft.graph.internalDomainFederation"
@@ -414,12 +413,11 @@ If the upgrade had issues, follow these steps to roll back:
      "federatedIdpMfaBehavior": "enforceMfaByFederatedIdp"
    }
    ```
-
+   
+   The following response object is shortened for readability.
 
    **Response**
 
-   >[!NOTE]
-   >The response object shown here might be shortened for readability.
    <!-- {
      "blockType": "response",
      "truncated": true,
@@ -452,6 +450,7 @@ If the upgrade had issues, follow these steps to roll back:
 
 Users will no longer be redirected to your on-premises federation server for MFA, whether they’re targeted by the Staged Rollout tool or not. Note this can take up to 24 hours to take effect.
 
+
 ## Next steps
 
 - [Overview of how to migrate from MFA Server to Azure AD Multi-Factor Authentication](how-to-migrate-mfa-server-to-azure-mfa.md)

articles/azure-cache-for-redis/cache-overview.md

@@ -42,7 +42,7 @@ Azure Cache for Redis is available in these tiers:
 | Basic | An OSS Redis cache running on a single VM. This tier has no service-level agreement (SLA) and is ideal for development/test and non-critical workloads. |
 | Standard | An OSS Redis cache running on two VMs in a replicated configuration. |
 | Premium | High-performance OSS Redis caches. This tier offers higher throughput, lower latency, better availability, and more features. Premium caches are deployed on more powerful VMs compared to the VMs for Basic or Standard caches. |
-| Enterprise | High-performance caches powered by Redis Inc.'s Redis Enterprise software. This tier supports Redis modules including RediSearch, RedisBloom, and RedisTimeSeries. Also, it offers even higher availability than the Premium tier. |
+| Enterprise | High-performance caches powered by Redis Inc.'s Redis Enterprise software. This tier supports Redis modules including RediSearch, RedisBloom, RedisJSON, and RedisTimeSeries. Also, it offers even higher availability than the Premium tier. |
 | Enterprise Flash | Cost-effective large caches powered by Redis Inc.'s Redis Enterprise software. This tier extends Redis data storage to non-volatile memory, which is cheaper than DRAM, on a VM. It reduces the overall per-GB memory cost. |
 
 ### Feature comparison
@@ -59,11 +59,14 @@ The [Azure Cache for Redis Pricing](https://azure.microsoft.com/pricing/details/
 | [Data persistence](cache-how-to-premium-persistence.md) |-|-|✔|Preview|Preview|
 | [Zone redundancy](cache-how-to-zone-redundancy.md) |-|-|✔|✔|✔|
 | [Geo-replication](cache-how-to-geo-replication.md) |-|-|✔|✔|✔|
-| [Redis Modules](#choosing-the-right-tier) |-|-|-|✔|-|
+| [Redis Modules](cache-redis-modules.md) |-|-|-|✔|Preview|
 | [Import/Export](cache-how-to-import-export-data.md) |-|-|✔|✔|✔|
 | [Reboot](cache-administration.md#reboot) |✔|✔|✔|-|-|
 | [Scheduled updates](cache-administration.md#schedule-updates) |✔|✔|✔|-|-|
 
+> [!NOTE]
+> The Enterprise Flash tier currently supports only the RedisJSON and RediSearch modules in preview. 
+
 ### Choosing the right tier
 
 Consider the following options when choosing an Azure Cache for Redis tier:
@@ -76,7 +79,7 @@ Consider the following options when choosing an Azure Cache for Redis tier:
 - **High availability**: Azure Cache for Redis provides multiple [high availability](cache-high-availability.md) options. It guarantees that a Standard, Premium, or Enterprise cache is available according to our [SLA](https://azure.microsoft.com/support/legal/sla/cache/v1_0/). The SLA only covers connectivity to the cache endpoints. The SLA doesn't cover protection from data loss. We recommend using the Redis data persistence feature in the Premium and Enterprise tiers to increase resiliency against data loss.
 - **Data persistence**: The Premium and Enterprise tiers allow you to persist the cache data to an Azure Storage account and a Managed Disk respectively. Underlying infrastructure issues might result in potential data loss. We recommend using the Redis data persistence feature in these tiers to increase resiliency against data loss. Azure Cache for Redis offers both RDB and AOF (preview) options. Data persistence can be enabled through Azure portal and CLI. For the Premium tier, see [How to configure persistence for a Premium Azure Cache for Redis](cache-how-to-premium-persistence.md).
 - **Network isolation**: Azure Private Link and Virtual Network (VNET) deployments provide enhanced security and traffic isolation for your Azure Cache for Redis. VNET allows you to further restrict access through network access control policies. For more information, see [Azure Cache for Redis with Azure Private Link](cache-private-link.md) and [How to configure Virtual Network support for a Premium Azure Cache for Redis](cache-how-to-premium-vnet.md).
-- **Redis Modules**: Enterprise tiers support [RediSearch](https://docs.redis.com/latest/modules/redisearch/), [RedisBloom](https://docs.redis.com/latest/modules/redisbloom/) and [RedisTimeSeries](https://docs.redis.com/latest/modules/redistimeseries/). These modules add new data types and functionality to Redis.
+- **Redis Modules**: Enterprise tiers support [RediSearch](https://docs.redis.com/latest/modules/redisearch/), [RedisBloom](https://docs.redis.com/latest/modules/redisbloom/), [RedisTimeSeries](https://docs.redis.com/latest/modules/redistimeseries/), and [RedisJSON](https://docs.redis.com/latest/modules/redisjson/) (preview). These modules add new data types and functionality to Redis.
 
 You can scale your cache from the Basic tier up to Premium after it has been created. Scaling down to a lower tier isn't supported currently. For step-by-step scaling instructions, see [How to Scale Azure Cache for Redis](cache-how-to-scale.md) and [How to automate a scaling operation](cache-how-to-scale.md#how-to-automate-a-scaling-operation).
 

articles/azure-resource-manager/management/resources-without-resource-group-limit.md

@@ -2,7 +2,7 @@
 title: Resources without 800 count limit
 description: Lists the Azure resource types that can have more than 800 instances in a resource group.
 ms.topic: conceptual
-ms.date: 08/10/2022
+ms.date: 08/31/2022
 ---
 
 # Resources not limited to 800 instances per resource group
@@ -32,7 +32,7 @@ Some resources have a limit on the number instances per region. This limit is di
 
 ## Microsoft.BotService
 
-* botServices - By default, limited to 800 instances. That limit can be increased by contacting support.
+* botServices - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.Resources/ARMDisableResourcesPerRGLimit 
 
 ## Microsoft.Compute
 
@@ -44,7 +44,7 @@ Some resources have a limit on the number instances per region. This limit is di
 * snapshots
 * virtualMachines
 * virtualMachines/extensions
-* virtualMachineScaleSets - By default, limited to 800 instances. That limit can be increased by contacting support.
+* virtualMachineScaleSets - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.Resources/ARMDisableResourcesPerRGLimit 
 
 ## Microsoft.ContainerInstance
 
@@ -84,7 +84,7 @@ Some resources have a limit on the number instances per region. This limit is di
 
 ## Microsoft.DevTestLab
 
-* labs/virtualMachines - By default, limited to 800 instances. That limit can be increased by contacting support.
+* labs/virtualMachines - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.DevTestLab/DisableLabVirtualMachineQuota 
 * schedules
 
 ## Microsoft.EdgeOrder
@@ -184,17 +184,17 @@ Some resources have a limit on the number instances per region. This limit is di
 
 ## Microsoft.NotificationHubs
 
-* namespaces - By default, limited to 800 instances. That limit can be increased by contacting support.
-* namespaces/notificationHubs - By default, limited to 800 instances. That limit can be increased by contacting support.
+* namespaces - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.NotificationHubs/ARMDisableResourcesPerRGLimit 
+* namespaces/notificationHubs - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.NotificationHubs/ARMDisableResourcesPerRGLimit 
 
 ## Microsoft.PowerBI
 
-* workspaceCollections - By default, limited to 800 instances. That limit can be increased by contacting support.
+* workspaceCollections - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.PowerBI/UnlimitedQuota 
 
 ## Microsoft.PowerBIDedicated
 
-* autoScaleVCores - By default, limited to 800 instances. That limit can be increased by contacting support.
-* capacities - By default, limited to 800 instances. That limit can be increased by contacting support.
+* autoScaleVCores - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.PowerBIDedicated/UnlimitedResourceGroupQuota 
+* capacities - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.PowerBIDedicated/UnlimitedResourceGroupQuota 
 
 ## Microsoft.Relay
 
@@ -245,7 +245,7 @@ Some resources have a limit on the number instances per region. This limit is di
 
 ## Microsoft.StreamAnalytics
 
-* streamingjobs - By default, limited to 800 instances. That limit can be increased by contacting support.
+* streamingjobs - By default, limited to 800 instances. That limit can be increased by [registering the following features](preview-features.md) - Microsoft.StreamAnalytics/ASADisableARMResourcesPerRGLimit 
 
 ## Microsoft.Web