updates2

Author: LiSeda

articles/azure-resource-manager/management/azure-subscription-service-limits.md

@@ -2,7 +2,7 @@
 title: Azure subscription and service limits, quotas, and constraints
 description: Understand common Azure subscription and service limits, quotas, and constraints. This article includes information about how to increase limits along with maximum values.
 ms.topic: conceptual
-ms.date: 01/24/2025
+ms.date: 01/23/2025
 ms.custom: ignite-2024
 ---
 

articles/azure-resource-manager/management/manage-resource-groups-portal.md

@@ -16,9 +16,9 @@ Learn how to use the [Azure portal](https://portal.azure.com) with [Azure Resour
 
 A resource group is a container that holds related resources for an Azure solution. The resource group can include all the resources for the solution or only those resources that you want to manage as a group. You decide how to allocate resources to resource groups based on what makes the most sense for your organization. Generally, add resources sharing the same lifecycle to the same resource group so you can easily deploy, update, and delete them as a group.
 
-The Azure portal uses resource group scope to create views that span across multiple resources. For example:
+The Azure portal uses the resource group scope to create views that span across multiple resources. For example:
 
-- **Metrics blade** provides metrics information (CPU, resources) to users. 
+- **Metrics blade** provides metrics information (CPU, resources) to users.
 - **Deployments blade** shows the history of ARM template or Bicep deployments targeted to that resource group (which includes portal deployments).
 - **Policy blade** provides information related to the policies enforced on the resource group.
 - **Diagnostics settings blade** provides errors and warnings to review.

articles/azure-resource-manager/management/move-resource-group-and-subscription.md

@@ -2,7 +2,7 @@
 title: Move Azure resources to a new resource group or subscription
 description: Learn how to move resources to a new resource group or subscription, and understand the steps to ensure a successful move operation.
 ms.topic: conceptual
-ms.date: 01/24/2025
+ms.date: 01/23/2025
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, devx-track-arm-template, devx-track-python
 content_well_notification: 
   - AI-contribution

articles/azure-resource-manager/management/move-support-resources.md

@@ -2,7 +2,7 @@
 title: Azure resource types for move operations
 description: Lists the Azure resource types that can be moved to a new resource group, subscription, or region.
 ms.topic: conceptual
-ms.date: 01/24/2025
+ms.date: 01/23/2025
 ms.custom: tbd
 ---
 

articles/azure-resource-manager/management/request-limits-and-throttling.md

@@ -59,7 +59,6 @@ The subscription limits apply per subscription, per service principal, and per o
 
 The limits might be smaller for free or trial customers.
 
-
 For example, suppose you have a bucket size of 250 tokens for read requests and refill rate of 25 tokens per second. If you send 250 read requests in a second, the bucket is empty and your requests are throttled. Each second, 25 tokens become available until the bucket reaches its maximum capacity of 250 tokens. You can use tokens as they become available.
 
 Reading metrics using the `*/providers/microsoft.insights/metrics` API contributes significantly to overall Azure Resource Manager traffic and is a common cause of subscription throttling events. If you use this API heavily, we recommend that you switch to the `getBatch` API. You can query multiple resources in a single REST request, which improves performance and reduces throttling. For more information about converting your operations, see [How to migrate from the metrics API to the getBatch API](/azure/azure-monitor/essentials/migrate-to-batch-api).
@@ -123,10 +122,8 @@ When you reach the limit, you receive the HTTP status code **429 Too many reques
 
 If you're using an Azure SDK, the SDK might have an auto retry configuration. For more information, see [Retry guidance for Azure services](/azure/architecture/best-practices/retry-service-specific).
 
-
 Some resource providers return 429 to report a temporary problem. The problem could be an overload condition that your request didn't cause. Or, it could be a temporary error about the state of the target resource or dependent resource. For example, the network resource provider returns 429 with the **RetryableErrorDueToAnotherOperation** error code when another operation locks the target resource. To determine if the error comes from throttling or a temporary condition, view the error details in the response.
 
-
 ## Remaining requests
 
 You can determine the number of remaining requests by examining response headers. Read requests return a value in the header for the number of remaining read requests. Write requests include a value for the number of remaining write requests. The following table describes the response headers you can examine for those values:
@@ -136,12 +133,12 @@ You can determine the number of remaining requests by examining response headers
 | x-ms-ratelimit-remaining-subscription-deletes |Subscription scoped deletes remaining. This value is returned on delete operations. |
 | x-ms-ratelimit-remaining-subscription-reads |Subscription scoped reads remaining. This value is returned on read operations. |
 | x-ms-ratelimit-remaining-subscription-writes |Subscription scoped writes remaining. This value is returned on write operations. |
-| x-ms-ratelimit-remaining-tenant-reads |Tenant scoped reads remaining |
-| x-ms-ratelimit-remaining-tenant-writes |Tenant scoped writes remaining |
+| x-ms-ratelimit-remaining-tenant-reads |Tenant scoped reads remaining. |
+| x-ms-ratelimit-remaining-tenant-writes |Tenant scoped writes remaining. |
 | x-ms-ratelimit-remaining-subscription-resource-requests |Remaining subscription scoped resource type requests.<br /><br />This header value is returned only if a service overrides the default limit. Resource Manager adds this value instead of the subscription reads or writes. |
 | x-ms-ratelimit-remaining-subscription-resource-entities-read |Remaining subscription scoped resource type collection requests.<br /><br />This header value is returned only if a service overrides the default limit. This value provides the number of remaining collection requests (list resources). |
-| x-ms-ratelimit-remaining-tenant-resource-requests |Remaining tenant scoped resource type requests.<br /><br />This header is added for requests at tenant level, and only if a service overrides the default limit. Resource Manager adds this value instead of the tenant reads or writes. |
-| x-ms-ratelimit-remaining-tenant-resource-entities-read |Tenant scoped resource type collection requests remaining.<br /><br />This header is only added for requests at tenant level, and only if a service overrides the default limit. |
+| x-ms-ratelimit-remaining-tenant-resource-requests |Remaining tenant scoped resource type requests.<br /><br />This header is added for requests at tenant level and only if a service overrides the default limit. Resource Manager adds this value instead of the tenant reads or writes. |
+| x-ms-ratelimit-remaining-tenant-resource-entities-read |Tenant scoped resource type collection requests remaining.<br /><br />This header is only added for requests at tenant level and only if a service overrides the default limit. |
 
 The resource provider can also return response headers with information about remaining requests. For information about response headers returned by the Compute resource provider, see [Call rate informational response headers](/troubleshoot/azure/virtual-machines/troubleshooting-throttling-errors#call-rate-informational-response-headers).
 
@@ -162,7 +159,7 @@ $r = Invoke-WebRequest -Uri https://management.azure.com/subscriptions/{guid}/re
 $r.Headers["x-ms-ratelimit-remaining-subscription-reads"]
 ```
 
-For a complete PowerShell example, see [Check Resource Manager Limits for a Subscription](https://github.com/Microsoft/csa-misc-utils/tree/master/psh-GetArmLimitsViaAPI).
+For a complete PowerShell example, see [Check ARM Limits for a Given Subscription](https://github.com/Microsoft/csa-misc-utils/tree/master/psh-GetArmLimitsViaAPI).
 
 To see the remaining requests for debugging, provide the **-Debug** parameter on your **PowerShell** cmdlet.