Skip to content

Commit e54d81b

Browse files
authored
acrolinx writing feedback
1 parent 8cfd584 commit e54d81b

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/automanage/move-automanaged-configurationprofile.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,29 +10,29 @@ ms.custom: subject-moving-resources
1010
---
1111

1212
# Move an Azure Automanage Configuration Profile to a different region
13-
This article describes how to migrate an Automanage Configuration Profile to a different region. You might want to move your Configuration Profiles to another region for a number of reasons. For example, to take advantage of a new Azure region, to meet internal policy and governance requirements, or in response to capacity planning requirements. You may want to deploy Azure Automanage to some VMs that are in a new region, and may want to do so with a Configuration Profile local to that region..
13+
This article describes how to migrate an Automanage Configuration Profile to a different region. You might want to move your Configuration Profiles to another region for many reasons. For example, to take advantage of a new Azure region, to meet internal policy and governance requirements, or in response to capacity planning requirements. You may want to deploy Azure Automanage to some VMs that are in a new region. Some regions may require that you use Automanage Configuration Profiles that are local to that region..
1414

1515
## Prerequisites
1616
* Ensure that your target region is [supported by Automanage](./automanage-virtual-machines.md#prerequisites).
1717
* Ensure that your Log Analytics workspace region, Automation account region, and your target region are all regions supported by the region mappings [here](../automation/how-to/region-mappings.md).
1818

1919
## Download your desired Automanage Configuration Profile
2020

21-
This can be done by using PowerShell. First, perform a `GET` using `Invoke-RestMethod` against the Automanage Resource Provider, substituting the values for your subscription.
21+
We'll begin by downloading our previous Configuration Profile using PowerShell. First, perform a `GET` using `Invoke-RestMethod` against the Automanage Resource Provider, substituting the values for your subscription.
2222

2323
```url
2424
https://management.azure.com/subscriptions/<yourSubscription>/providers/Microsoft.Automanage/configurationProfiles?api-version=2021-04-30-preview
2525
```
2626

27-
This will display a list of Automanage Configuration Profile information, including the settings and the ConfigurationProfile ID
27+
The GET command will display a list of Automanage Configuration Profile information, including the settings and the ConfigurationProfile ID
2828
```azurepowershell-interactive
2929
$listConfigurationProfilesURI = "https://management.azure.com/subscriptions/<yourSubscription>/providers/Microsoft.Automanage/configurationProfiles?api-version=2021-04-30-preview"
3030
3131
Invoke-RestMethod `
3232
-URI $listConfigurationProfilesURI
3333
```
3434

35-
This will result in a list of your Configuration Profiles created in this subscription, as seen below, edited for brevity.
35+
Here are the results, edited for brevity.
3636

3737
```json
3838
{
@@ -63,7 +63,7 @@ This will result in a list of your Configuration Profiles created in this subscr
6363
}
6464
```
6565

66-
The next step is to do another `GET`, this time to retrieve the specific profile we would like to create in a new region. For this example, we will retrieve 'testProfile1'. We will perform a `GET` against the `id` value for the desired profile.
66+
The next step is to do another `GET`, this time to retrieve the specific profile we would like to create in a new region. For this example, we'll retrieve 'testProfile1'. We'll perform a `GET` against the `id` value for the desired profile.
6767

6868
```azurepowershell-interactive
6969
$profileId = "https://management.azure.com/subscriptions/yourSubscription/resourceGroups/yourResourceGroup/providers/Microsoft.Automanage/configurationProfiles/testProfile1?api-version=2021-04-30-preview"
@@ -76,7 +76,7 @@ $profile = Invoke-RestMethod `
7676

7777
Creating the profile in a new location is as simple as changing the `Location` property to our desired Azure Region.
7878

79-
We also will need to create a new name for this profile. Let's change this to profileUk. This should be done for the `Name` property within the profile, and also in the URL. We can use the `-replace` format operator to make this very simple.
79+
We also will need to create a new name for this profile. Let's change the name of the Configuration Profile `profileUk`. We should update the `Name` property within the profile, and also in the URL. We can use the `-replace` format operator to make this simple.
8080

8181
```powershell
8282
$profile.Location = "westeurope"
@@ -99,7 +99,7 @@ $profile = Invoke-RestMethod `
9999
## Enable Automanage on your VMs
100100
For details on how to move your VMs, see this [article](../resource-mover/tutorial-move-region-virtual-machines.md).
101101

102-
Once you have moved your pofile to a new region, you may use it as a custom profile for any VM. Details are available [here](./automanage-virtual-machines.md#enabling-automanage-for-vms-in-azure-portal).
102+
Once you've moved your profile to a new region, you may use it as a custom profile for any VM. Details are available [here](./automanage-virtual-machines.md#enabling-automanage-for-vms-in-azure-portal).
103103

104104
## Next steps
105105
* [Learn more about Azure Automanage](./automanage-virtual-machines.md)

0 commit comments

Comments
 (0)