You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/how-to/move-account.md
+44-44Lines changed: 44 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,16 +14,16 @@ manager: carmonm
14
14
15
15
Azure Automation allows you to move some resources to a new resource group or subscription. You can move resources through the Azure portal, PowerShell, the Azure CLI, or the REST API. To learn more about the process, see [Move resources to a new resource group or subscription](../../azure-resource-manager/management/move-resource-group-and-subscription.md).
16
16
17
-
The Azure Automation account is one of the resources that you can move. In this article, you'll learn to move Automation accounts to another resource or subscription. The high-level steps for moving your Automation account are:
17
+
The Automation account is one of the resources that you can move. In this article, you'll learn to move Automation accounts to another resource or subscription. The high-level steps for moving your Automation account are:
18
18
19
19
1. Remove your solutions.
20
20
2. Unlink your workspace.
21
21
3. Move the Automation account.
22
-
4. Delete and recreate the Run As accounts.
22
+
4. Delete and re-create the Run As accounts.
23
23
5. Re-enable your solutions.
24
24
25
25
>[!NOTE]
26
-
>This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md).
26
+
>In this article, you work with the Azure PowerShell Az module. You can still use the AzureRM module. To learn more about Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version by using [How to update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md).
27
27
28
28
## Remove solutions
29
29
@@ -34,54 +34,54 @@ To unlink your workspace from your Automation account, you must remove these sol
34
34
- Start/Stop VMs during off hours
35
35
36
36
1. In the Azure portal, locate your resource group.
37
-
2. Find each solution and click**Delete** on the Delete Resources page.
37
+
2. Find each solution, and select**Delete** on the **Delete Resources** page.
38
38
39
-
39
+
40
40
41
-
If you prefer, you can delete the solutions using the [Remove-AzResource](https://docs.microsoft.com/powershell/module/Az.Resources/Remove-AzResource?view=azps-3.7.0) cmdlet:
41
+
If you prefer, you can delete the solutions by using the [Remove-AzResource](https://docs.microsoft.com/powershell/module/Az.Resources/Remove-AzResource?view=azps-3.7.0) cmdlet:
### Remove alert rules for the Start/Stop VMs during off hours solution
51
+
### Remove alert rules for the "Start/Stop VMs during off hours" solution
52
52
53
-
For the Start/Stop VMs during off hours solution, you also need to remove the alert rules created by the solution.
53
+
For this solution, you also need to remove the alert rules created by the solution.
54
54
55
55
1. In the Azure portal, go to your resource group and select **Monitoring** > **Alerts** > **Manage alert rules**.
56
56
57
-
57
+
58
58
59
-
2. On the Rules page, you should see a list of the alerts configured in that resource group. The solution creates these rules:
59
+
2. On the **Rules** page, you should see a list of the alerts configured in that resource group. The solution creates these rules:
60
60
61
61
* AutoStop_VM_Child
62
62
* ScheduledStartStop_Parent
63
63
* SequencedStartStop_Parent
64
64
65
-
3. Select the rules one at a time and click **Delete** to remove them.
65
+
3. Select the rules one at a time, and select**Delete** to remove them.
66
66
67
-
67
+
68
68
69
69
> [!NOTE]
70
-
> If you don't see any alert rules on the Rules page, change the **Status** field to Disabled to show disabled alerts, because you might have disabled them.
70
+
> If you don't see any alert rules on the **Rules** page, change the **Status** field to **Disabled** to show disabled alerts. You might have disabled them.
71
71
72
-
4. When the alert rules are removed, you must remove the action group created for Start/Stop VMs during off hours solution notifications. In the Azure portal, select **Monitor** > **Alerts** > **Manage action groups**.
72
+
4. When you remove the alert rules, you must remove the action group created for the "Start/Stop VMs during off hours" solution notifications. In the Azure portal, select **Monitor** > **Alerts** > **Manage action groups**.
73
73
74
74
5. Select **StartStop_VM_Notification**.
75
75
76
76
6. On the action group page, select **Delete**.
77
77
78
-
78
+
79
79
80
-
If you prefer, you can delete your action group using the [Remove-AzActionGroup](https://docs.microsoft.com/powershell/module/az.monitor/remove-azactiongroup?view=azps-3.7.0) cmdlet:
80
+
If you prefer, you can delete your action group by using the [Remove-AzActionGroup](https://docs.microsoft.com/powershell/module/az.monitor/remove-azactiongroup?view=azps-3.7.0) cmdlet:
@@ -91,52 +91,52 @@ Now you can unlink your workspace:
91
91
92
92
2. Select **Unlink workspace** to unlink the workspace from your Automation account.
93
93
94
-
94
+
95
95
96
96
## Move your Automation account
97
97
98
98
You can now move your Automation account and its runbooks.
99
99
100
100
1. In the Azure portal, browse to the resource group of your Automation account. Select **Move** > **Move to another subscription**.
101
101
102
-
102
+
103
103
104
104
2. Select the resources in your resource group that you want to move. Ensure that you include your Automation account, runbooks, and Log Analytics workspace resources.
105
105
106
-
## Recreate Run As accounts
106
+
## Re-create Run As accounts
107
107
108
-
[Run As accounts](../manage-runas-account.md) create a service principal in Azure Active Directory to authenticate with Azure resources. When you change subscriptions, the Automation account no longer uses the existing Run As account. To recreate the Run As accounts:
108
+
[Run As accounts](../manage-runas-account.md) create a service principal in Azure Active Directory to authenticate with Azure resources. When you change subscriptions, the Automation account no longer uses the existing Run As account. To re-create the Run As accounts:
109
109
110
-
1. Go to your Automation account in the new subscription and select **Run as accounts** under **Account Settings**. You'll see that the Run As accounts show as incomplete now.
110
+
1. Go to your Automation account in the new subscription, and select **Run as accounts** under **Account Settings**. You'll see that the Run As accounts show as incomplete now.
111
111
112
-
112
+
113
113
114
-
2. Delete the Run As accounts one at a time using the **Delete** button on the Properties page.
114
+
2. Delete the Run As accounts, one at a time, by selecting**Delete** on the **Properties** page.
115
115
116
116
> [!NOTE]
117
-
> If you don't have permissions to create or view the Run As accounts, you see the following message: `You do not have permissions to create an Azure Run As account (service principal) and grant the Contributor role to the service principal.` To learn about the permissions required to configure a Run As account, see [Permissions required to configure Run As accounts](../manage-runas-account.md#permissions).
117
+
> If you don't have permissions to create or view the Run As accounts, you see the following message: `You do not have permissions to create an Azure Run As account (service principal) and grant the Contributor role to the service principal.`For more information, see [Permissions required to configure Run As accounts](../manage-runas-account.md#permissions).
118
118
119
119
3. After you've deleted the Run As accounts, select **Create** under **Azure Run As account**.
120
120
121
-
4. On the Add Azure Run As account page, select **Create** to create the Run As account and service principal.
121
+
4. On the **Add Azure Run As account** page, select **Create** to create the Run As account and service principal.
122
122
123
123
5. Repeat the steps above with the Azure Classic Run As account.
124
124
125
125
## Enable solutions
126
126
127
-
After you recreate the Run As accounts, you must re-enable the solutions that you removed before the move:
127
+
After you re-create the Run As accounts, you must re-enable the solutions that you removed before the move:
128
128
129
-
1. To turn on the Change Tracking and Inventory solution, select Change Tracking and Inventory in your Automation account. Choose the Log Analytics workspace that you moved over and select **Enable**.
129
+
1. To turn on the "Change Tracking and Inventory" solution, select **Change Tracking and Inventory** in your Automation account. Choose the Log Analytics workspace that you moved over, and select **Enable**.
130
130
131
-
2. Repeat step 1 for the Update Management solution.
131
+
2. Repeat step 1 for the "Update Management" solution.
132
132
133
-
133
+
134
134
135
-
3. Machines that are onboarded with your solutions are visible when you've connected the existing Log Analytics workspace. To turn on the Start/Stop VMs during off hours solution, you must redeploy the solution. Under **Related Resources**, select **Start/Stop VMs** > **Learn more about and enable the solution** > **Create** to start the deployment.
135
+
3. Machines that are onboarded with your solutions are visible when you've connected the existing Log Analytics workspace. To turn on the "Start/Stop VMs during off hours" solution, you must redeploy the solution. Under **Related Resources**, select **Start/Stop VMs** > **Learn more about and enable the solution** > **Create** to start the deployment.
136
136
137
-
4. On the Add Solution page, choose your Log Analytics workspace and Automation account.
137
+
4. On the **Add Solution** page, choose your Log Analytics workspace and Automation account.
140
140
141
141
5. Configure the solution as described in [Start/Stop VMs during off hours solution in Azure Automation](../automation-solution-vm-management.md).
142
142
@@ -150,8 +150,8 @@ When the move is complete, verify that the capabilities listed below are enabled
150
150
|Source control|You can run a manual sync on your source control repository.|[Source control integration](../source-control-integration.md)|
151
151
|Change tracking and inventory|Verify that you see current inventory data from your machines.|[Troubleshoot change tracking](../troubleshoot/change-tracking.md)|
152
152
|Update management|Verify that you see your machines and that they're healthy.</br>Run a test software update deployment.|[Troubleshoot update management](../troubleshoot/update-management.md)|
153
-
|Shared resources|Verify that you see all your shared resources, such as [credentials](../shared-resources/credentials.md), [variables](../shared-resources/variables.md), and the like.|
153
+
|Shared resources|Verify that you see all your shared resources, such as [credentials](../shared-resources/credentials.md) and [variables](../shared-resources/variables.md).|
154
154
155
155
## Next steps
156
156
157
-
To learn more about moving resources in Azure, see [Move resources in Azure](../../azure-resource-manager/management/move-support-resources.md).
157
+
To learn about moving resources in Azure generally, see [Move resources in Azure](../../azure-resource-manager/management/move-support-resources.md).
0 commit comments