Merge pull request #294401 from tfitzmac/0210edits1

copy edit

Author: JillGrant615

articles/azure-resource-manager/management/manage-resources-powershell.md

@@ -2,7 +2,7 @@
 title: Manage resources - Azure PowerShell
 description: Use Azure PowerShell and Azure Resource Manager to manage your resources. Shows how to deploy and delete resources. 
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 02/10/2025
 ms.custom: devx-track-azurepowershell, devx-track-arm-template
 ---
 
@@ -123,7 +123,7 @@ For more information, see [Lock resources with Azure Resource Manager](lock-reso
 
 ## Tag resources
 
-Tagging helps organizing your resource group and resources logically. For information, see [Using tags to organize your Azure resources](tag-resources-powershell.md).
+Tagging helps you organize your resource group and resources logically. For information, see [Using tags to organize your Azure resources](tag-resources-powershell.md).
 
 ## Manage access to resources
 

articles/azure-resource-manager/management/manage-resources-python.md

@@ -2,7 +2,7 @@
 title: Manage resources - Python
 description: Use Python and Azure Resource Manager to manage your resources. Shows how to deploy and delete resources. 
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 02/10/2025
 ms.custom: devx-track-arm-template, devx-track-python
 content_well_notification: 
   - AI-contribution
@@ -242,7 +242,7 @@ For more information, see [Lock resources with Azure Resource Manager](lock-reso
 
 ## Tag resources
 
-Tagging helps organizing your resource group and resources logically. For information, see [Using tags to organize your Azure resources](tag-resources-python.md).
+Tagging helps you organize your resource group and resources logically. For information, see [Using tags to organize your Azure resources](tag-resources-python.md).
 
 ## Next steps
 

articles/azure-resource-manager/management/manage-resources-rest.md

@@ -3,7 +3,7 @@ title: Manage resources - REST
 description: Use REST operations with Azure Resource Manager to manage your resources. Shows how to read, deploy, and delete resources. 
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 09/26/2024
+ms.date: 02/10/2025
 ---
 
 # Manage Azure resources by using the REST API
@@ -12,11 +12,11 @@ Learn how to use the REST API for [Azure Resource Manager](overview.md) to manag
 
 ## Obtain an access token
 
-To make a REST API call to Azure, you first need to obtain an access token. Include this access token in the headers of your Azure REST API calls using the "Authorization" header and setting the value to "Bearer {access-token}".
+To make a REST API call to Azure, you first need to obtain an access token. Include this access token in the headers of your Azure REST API calls using the `Authorization` header and setting the value to `Bearer {access-token}`.
 
 If you need to programmatically retrieve new tokens as part of your application, you can obtain an access token by [Registering your client application with Microsoft Entra ID](/rest/api/azure/#register-your-client-application-with-azure-ad).
 
-If you're getting started and want to test Azure REST APIs using your individual token, you can retrieve your current access token quickly with either Azure PowerShell or Azure CLI.
+To test Azure REST APIs using your individual token, retrieve your current access token with either Azure PowerShell or Azure CLI.
 
 ### [Azure CLI](#tab/azure-cli)
 
@@ -53,7 +53,7 @@ Authorization: Bearer <bearer-token>
 Host: management.azure.com
 ```
 
-Here is an example cURL command that you can use to list all resources in a resource group using the Azure Resource Manager API:
+Here's an example cURL command that you can use to list all resources in a resource group using the Azure Resource Manager API:
 
 ```curl
 curl  -H "Authorization: Bearer $token" -H 'Content-Type: application/json' -X GET 'https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/resources?api-version=2021-04-01'
@@ -124,7 +124,7 @@ Host: management.azure.com
 }
 ```
 
-For the REST APIs, the value of `uri` can't be a local file or a file that is only available on your local network. Azure Resource Manager must be able to access the template. Provide a URI value that downloadable as HTTP or HTTPS.
+For the REST APIs, the value of `uri` can't be a local file or a file that is only available on your local network. Azure Resource Manager must access the template. Provide a URI value that is downloadable as HTTP or HTTPS.
 For more information, see [Deploy resources with Resource Manager templates and Azure PowerShell](../templates/deploy-powershell.md).
 
 ## Deploy a resource group and resources

articles/azure-resource-manager/management/microsoft-resources-move-regions.md

@@ -2,12 +2,12 @@
 title: Move regions for resources in Microsoft.Resources
 description: Show how to move resources that are in the Microsoft.Resources namespace to new regions.
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 02/10/2025
 ---
 
 # Move Microsoft.Resources resources to new region
 
-You may need to move an existing resource to a new region. This article shows how to move two resource types - templateSpecs and deploymentScripts - that are in the Microsoft.Resources namespace.
+You might need to move an existing resource to a new region. This article shows how to move two resource types - templateSpecs and deploymentScripts - that are in the Microsoft.Resources namespace.
 
 ## Move template specs to new region
 
@@ -65,19 +65,19 @@ If you have a [template spec](../templates/template-specs.md) in one region and
 
 1. [Export the template](../templates/export-template-portal.md). When exporting, select the deployment script and any other required resources.
 
-1. In the exported template, delete the following properties:
+1. Delete the following properties in the exported template:
 
    * tenantId
    * principalId
    * clientId
 
-1. The exported template has a hardcoded value for the region of the deployment script.
+1. Find the hardcoded value for the region of the deployment script.
 
    ```json
    "location": "westus2",
    ```
 
-   Change the template to allow a parameter for setting the location. For more information, see [Set resource location in ARM template](../templates/resource-location.md)
+   Change the template to allow a parameter for setting the location. For more information, see [Set resource location in ARM template](../templates/resource-location.md).
 
    ```json
    "location": "[parameters('location')]",

articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md

@@ -3,7 +3,7 @@ title: Move Azure App Service resources across resource groups or subscriptions
 description: Use Azure Resource Manager to move App Service resources to a new resource group or subscription.
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 09/13/2024
+ms.date: 02/11/2025
 ---
 
 # Move App Service resources to a new resource group or subscription
@@ -18,20 +18,20 @@ You can move App Service resources to a new resource group or subscription but y
 
 When you move an app across subscriptions, the following guidance applies:
 
-- Moving a resource to a new resource group or subscription is a metadata change that shouldn't affect anything about how the resource functions. For example, the inbound IP address for an app service doesn't change when moving the app service.
+- Moving a resource to a new resource group or subscription is a metadata change that doesn't affect how the resource functions. For example, the inbound IP address for an app service doesn't change when you move the app service.
 - The destination resource group must not have any existing App Service resources. App Service resources include:
     - Web apps
     - App Service plans
     - Uploaded or imported TLS/SSL certificates
     - App Service Environments
-- All App Service resources in the resource group must be moved together.
-- App Service Environments can't be moved to a new resource group or subscription.
+- You must move all App Service resources in the resource group together.
+- You can't move App Service Environments to a new resource group or subscription.
     - You can move an app and plan hosted on an App Service Environment to a new subscription without moving the App Service Environment. The app and plan that you move are always associated with your initial App Service Environment. You can't move an app/plan to a different App Service Environment.
-    - If you need to move an app and plan to a new App Service Environment, you'll need to recreate these resources in your new App Service Environment. Consider using the [backup and restore feature](../../../app-service/manage-backup.md) as way of recreating your resources in a different App Service Environment.
-- Apps with private endpoints cannot be moved. Delete the private endpoint(s) and recreate it after the move.
-- Apps with virtual network integration can't be moved. Remove the virtual network integration and reconnect it after the move.
-- App Service resources can only be moved from the resource group in which they were originally created. If an App Service resource is no longer in its original resource group, move it back to its original resource group. Then, move the resource across subscriptions. For help with finding the original resource group, see the next section.
-- When you move an app to a different resource group or subscription, the location of the app remains the same, but its policy is changed. For example, consider a case where your app runs in `Subscription1` (Central US) and has `Policy1` and `Subscription2` (UK South) that has `Policy2`. If you move your app to Subscription2, the location of the app remains the same (Central US); however, it falls under the new policy `Policy2`.
+    - If you need to move an app and plan to a new App Service Environment, you must recreate these resources in your new App Service Environment. To recreate your resources in a different App Service Environment, consider using the [backup and restore feature](../../../app-service/manage-backup.md).
+- You can't move apps with private endpoints. To move the app, delete the private endpoints and recreate them after the move.
+- You can't move apps with virtual network integration. To move the app, remove the virtual network integration and reconnect it after the move.
+- You can only move App Service resources from the resource group where you originally created them. If an App Service resource isn't in its original resource group, move it back to its original resource group. Then, move the resource across subscriptions. For help with finding the original resource group, see the next section.
+- When you move an app to a different resource group or subscription, the location of the app remains the same, but its policy changes. For example, consider a case where your app runs in `Subscription1` (Central US) and has `Policy1` and `Subscription2` (UK South) that has `Policy2`. If you move your app to Subscription2, the location of the app remains the same (Central US); however, it falls under the new policy `Policy2`.
 
 ## Find original resource group
 
@@ -53,19 +53,19 @@ You see the recommended actions to take before moving the resources. The informa
 
 ## Move hidden resource types in portal
 
-When using the portal to move your App Service resources, you may see an error indicating that you haven't moved all of the resources. If you see this error, check if there are resource types that the portal didn't display. Select **Show hidden types**. Then, select all of the resources to move.
+When you use the portal to move your App Service resources, you might see an error indicating that you didn't move all of the resources. If you see this error, check if there are resource types that the portal didn't display. Select **Show hidden types**. Then, select all of the resources to move.
 
 :::image type="content" source="./media/app-service-move-limitations/show-hidden-types.png" alt-text="Screenshot of the Show Hidden Types option in the portal when moving App Service resources.":::
 
 ## Move with free managed certificates
 
 You can't move a free App Service managed certificate. Instead, delete the managed certificate and recreate it after moving the web app. To get instructions for deleting the certificate, use the **Migration Operations** tool.
 
-If your free App Service managed certificate gets created in an unexpected resource group, try moving the app service plan back to its original resource group. Then, recreate the free managed certificate. This issue will be fixed.
+If your free App Service managed certificate gets created in an unexpected resource group, try moving the app service plan back to its original resource group. Then, recreate the free managed certificate. This change fixes the issue.
 
 ## Move support
 
-To determine which App Service resources can be moved, see move support status for:
+To determine which App Service resources you can move, see move support status for:
 
 - [Microsoft.AppService](../move-support-resources.md#microsoftappservice)
 - [Microsoft.CertificateRegistration](../move-support-resources.md#microsoftcertificateregistration)

articles/azure-resource-manager/management/move-limitations/classic-model-move-limitations.md

@@ -2,7 +2,7 @@
 title: Move Azure classic deployment resources
 description: Use Azure Resource Manager to move classic deployment resources to a new resource group or subscription.
 ms.topic: conceptual
-ms.date: 06/20/2024
+ms.date: 02/11/2025
 ms.custom: devx-track-arm-template
 ---
 
@@ -12,26 +12,26 @@ The steps to move resources deployed through the classic model differ based on w
 
 ## Move in the same subscription
 
-When moving resources from one resource group to another resource group within the same subscription, the following restrictions apply:
+When you move resources from one resource group to another resource group within the same subscription, the following restrictions apply:
 
-- Virtual networks (classic) can't be moved.
-- Virtual machines (classic) must be moved with the cloud service.
-- Cloud service can only be moved when the move includes all its virtual machines.
-- Only one cloud service can be moved at a time.
-- Only one storage account (classic) can be moved at a time.
-- Storage account (classic) can't be moved in the same operation with a virtual machine or a cloud service.
+- You can't move virtual networks (classic).
+- You must move virtual machines (classic) with the cloud service.
+- You can only move the cloud service when the move includes all its virtual machines.
+- You can only move one cloud service at a time.
+- You can only move one storage account (classic) at a time.
+- You can't move storage account (classic) in the same operation with a virtual machine or a cloud service.
 
-To move classic resources to a new resource group within the same subscription, use the [standard move operations](../move-resource-group-and-subscription.md) through the portal, Azure PowerShell, Azure CLI, or REST API. You use the same operations as you use for moving Resource Manager resources.
+To move classic resources to a new resource group within the same subscription, use the [standard move operations](../move-resource-group-and-subscription.md) through the portal, Azure PowerShell, Azure CLI, or REST API. Use the same operations as you use for moving Resource Manager resources.
 
 ## Move across subscriptions
 
-When moving classic cloud services to a new subscription, the following restrictions apply:
+When you move classic cloud services to a new subscription, the following restrictions apply:
 
 - The source and target subscriptions need to be under the same Microsoft Entra tenant.
-- Cloud Service Provider (CSP) subscriptions do not support migrating classic cloud services.
+- Cloud Service Provider (CSP) subscriptions don't support migrating classic cloud services.
 - All classic resources in the subscription must be moved in the same operation.
 - The target subscription must not have any other classic resources.
-- The move can only be requested through a separate REST API for classic moves. The standard Resource Manager move commands don't work when moving classic resources to a new subscription.
+- You can only request the move through a separate REST API for classic moves. The standard Resource Manager move commands don't work when moving classic resources to a new subscription.
 
 To move classic resources to a new subscription, use the REST operations that are specific to classic resources. To use REST, do the following steps:
 
@@ -76,7 +76,7 @@ To move classic resources to a new subscription, use the REST operations that ar
    ```
 
      The response is in the same format as the source subscription validation.
-1. If both subscriptions pass validation, move all classic resources from one subscription to another subscription with the following operation:
+1. Move all classic resources that pass validation from one subscription to another subscription. Use the following operation:
 
    ```HTTP
    POST https://management.azure.com/subscriptions/{subscription-id}/providers/Microsoft.ClassicCompute/moveSubscriptionResources?api-version=2016-04-01
@@ -90,27 +90,27 @@ To move classic resources to a new subscription, use the REST operations that ar
    }
    ```
 
-The operation may run for several minutes.
+The operation might run for several minutes.
 
 ## Possible error messages in the source subscription validation stage
 
 ### "Subscription migration for SubscriptionId {subscription ID} cannot continue as IaaS classic to ARM migration is in progress for the following deployment resource: _xx in HostedService {classic-cloud-service-name}_"
 
-This message means there is a classic cloud service that is ongoing migrating to the cloud service (extended support). Users should abort this ARM migration operation and then retry validation.
+This message means there's a classic cloud service that's ongoing migrating to the cloud service (extended support). You should abort this ARM migration operation and then retry validation.
 
 ### "Source subscription _{subscription ID}_ is empty"
 
-The source subscription cannot be empty, disabled, deleted or currently undergoing migration. During the migration period, write operations are not allowed on resources within the subscription.
+The source subscription can't be empty, disabled, deleted, or currently undergoing migration. During the migration period, write operations aren't allowed on resources within the subscription.
 
 ### "Source subscription contains application(s) which doesn't support migration: _{application name}_"
 
 ### "Source subscription contains following cloud service(s) which doesn't support migration: _{cloud service name}_"
 
-The resources mentioned in the error message cannot be migrated, so users should delete these resources before triggering the migration.
+You can't migrate the resources mentioned in the error message, so delete these resources before triggering the migration.
 
 ### More information
 
-The domain name and the public IP are still the same as before migration. Under normal circumstances, there should be no downtime for the cloud service during the migration.
+The domain name and the public IP are still the same as before migration. Under normal circumstances, there's no downtime for the cloud service during the migration.
 
 ## Next steps