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
+71-60Lines changed: 71 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ 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
-
Azure Automation accounts are one of the resources that can be moved. In this article, you'll learn the steps to move Automation accounts to another resource or subscription. The high-level steps to moving your Automation account are:
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:
18
18
19
19
1. Remove your solutions.
20
20
2. Unlink your workspace.
@@ -27,119 +27,130 @@ Azure Automation accounts are one of the resources that can be moved. In this ar
27
27
28
28
## Remove solutions
29
29
30
-
To unlink your workspace from your Automation account, these solutions must be removed from your workspace:
30
+
To unlink your workspace from your Automation account, you must remove these solutions from your workspace:
31
31
32
32
- Change Tracking and Inventory
33
33
- Update Management
34
34
- Start/Stop VMs during off hours
35
35
36
-
In your resource group, find each solution and select **Delete**. On the Delete Resources page, confirm the resources to be removed, and select **Delete**.
36
+
1. In the Azure portal, locate your resource group.
37
+
2. Find each solution and click **Delete** on the Delete Resources page.
37
38
38
-
39
+
39
40
40
-
You can accomplish the same task with the [Remove-AzResource](https://docs.microsoft.com/powershell/module/Az.Resources/Remove-AzResource?view=azps-3.7.0) cmdlet as shown in the following example:
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:
### Remove alert rules for the Start/Stop VMs during off hours solution
51
52
52
-
For the **Start/Stop VMs** solution, you also need to remove the alert rules created by the solution.
53
+
For the Start/Stop VMs during off hours solution, you also need to remove the alert rules created by the solution.
53
54
54
-
In the Azure portal, go to your resource group and select **Monitoring** > **Alerts** > **Manage alert rules**.
55
+
1. In the Azure portal, go to your resource group and select **Monitoring** > **Alerts** > **Manage alert rules**.
55
56
56
57
57
58
58
-
On the Rules page, you should see a list of the alerts configured in that resource group. The **Start/Stop VMs**solution creates three alert 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:
59
60
60
-
* AutoStop_VM_Child
61
-
* ScheduledStartStop_Parent
62
-
* SequencedStartStop_Parent
61
+
* AutoStop_VM_Child
62
+
* ScheduledStartStop_Parent
63
+
* SequencedStartStop_Parent
63
64
64
-
Select these three alert rules, and then select **Delete**. This action will remove these alert rules.
65
+
3. Select the rules one at a time and click **Delete** to remove them.
65
66
66
-
67
+
67
68
68
-
> [!NOTE]
69
-
> If you don't see any alert rules on the Rules page, change the **Status** to Disabled to show disabled alerts, because you might have disabled them.
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
71
71
-
When the alert rules are removed, remove the action group that was created for the **Start/Stop VMs**solution notifications.
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
73
73
-
In the Azure portal, select **Monitor** > **Alerts** > **Manage action groups**.
74
+
5. Select **StartStop_VM_Notification**.
74
75
75
-
Select **StartStop_VM_Notification** from the list. On the action group page, select **Delete**.
76
-
A
77
-
76
+
6. On the action group page, select **Delete**.
78
77
79
-
Similarly, you can delete your action group by using PowerShell with the [Remove-AzActionGroup](https://docs.microsoft.com/powershell/module/az.monitor/remove-azactiongroup?view=azps-3.7.0) cmdlet, as seen in the following example:
78
+
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:
In the Azure portal, select **Automation account** > **Related Resources** > **Linked workspace**. Select **Unlink workspace** to unlink the workspace from your Automation account.
88
+
Now you can unlink your workspace:
89
+
90
+
1. In the Azure portal, select **Automation account** > **Related Resources** > **Linked workspace**.
91
+
92
+
2. Select **Unlink workspace** to unlink the workspace from your Automation account.
88
93
89
-
94
+
90
95
91
96
## Move your Automation account
92
97
93
-
After removing the previous items, you can continue to remove your Automation account and its runbooks. In the Azure portal, browse to the resource group of your Automation account. Select **Move** > **Move to another subscription**.
98
+
You can now move your Automation account and its runbooks.
94
99
95
-
100
+
1. In the Azure portal, browse to the resource group of your Automation account. Select **Move** > **Move to another subscription**.
96
101
97
-
Select the resources in your resource group that you want to move. Ensure you include your **Automation account**, **Runbook**, and **Log Analytics workspace**resources.
102
+
98
103
99
-
After the move is complete, there are additional steps required to make everything work.
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.
100
105
101
-
## Re-create Run As accounts
106
+
## Recreate Run As accounts
102
107
103
-
[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.
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:
104
109
105
-
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.
106
111
107
-
112
+
108
113
109
-
Select each Run As account. On the Properties page, select **Delete**to delete the Run As account.
114
+
2. Delete the Run As accounts one at a time using the **Delete** button on the Properties page.
110
115
111
-
> [!NOTE]
112
-
> If you do not have permissions to create or view the Run As accounts, you'll 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).
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).
113
118
114
-
After the Run As accounts are deleted, select **Create** under **Azure Run As account**. On the **Add Azure Run As account** page, select **Create** to create the Run As account and service principal. Repeat the preceding steps with the **Azure Classic Run As account**.
119
+
3. After you've deleted the Run As accounts, select **Create** under **Azure Run As account**.
120
+
121
+
4. On the Add Azure Run As account page, select **Create** to create the Run As account and service principal.
122
+
123
+
5. Repeat the steps above with the Azure Classic Run As account.
115
124
116
125
## Enable solutions
117
126
118
-
After you re-create the Run As accounts, you'll re-enable the solutions that you removed before the move. To turn on **Change Tracking and Inventory** and **Update Management**, select the respective capability in your Automation account. Choose the Log Analytics workspace you moved over and select **Enable**.
127
+
After you recreate the Run As accounts, you must re-enable the solutions that you removed before the move:
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**.
119
130
120
-
131
+
2. Repeat step 1 for the Update Management solution.
121
132
122
-
Machines that are onboarded with your solutions will be visible when you've connected the existing Log Analytics workspace.
133
+
123
134
124
-
To turn on the **Start/Stop VMs** during off-hours solution, you'll need to 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 offhours 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.
125
136
126
-
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.
For detailed instructions on configuring the solution, see [Start/Stop VMs during off-hours solution in Azure Automation](../automation-solution-vm-management.md).
141
+
5. Configure the solution as described in [Start/Stop VMs during offhours solution in Azure Automation](../automation-solution-vm-management.md).
131
142
132
-
## Post-move verification
143
+
## Verify the move
133
144
134
-
When the move is complete, check the following list of tasks that should be verified:
145
+
When the move is complete, verify that the capabilities listed below are enabled.
135
146
136
-
|Capability|Tests|Troubleshooting link|
147
+
|Capability|Tests|Troubleshooting|
137
148
|---|---|---|
138
149
|Runbooks|A runbook can successfully run and connect to Azure resources.|[Troubleshoot runbooks](../troubleshoot/runbooks.md)
139
-
|Source control|You can run a manual sync on your source control repo.|[Source control integration](../source-control-integration.md)|
140
-
|Change tracking and inventory|Verify you see current inventory data from your machines.|[Troubleshoot change tracking](../troubleshoot/change-tracking.md)|
141
-
|Update management|Verify you see your machines and they're healthy.</br>Run a test software update deployment.|[Troubleshoot update management](../troubleshoot/update-management.md)|
142
-
|Shared resources|Verify that you see all of your shared resources, such as [Credentials](../shared-resources/credentials.md), [Variables](../shared-resources/variables.md), etc.|
150
+
|Source control|You can run a manual sync on your source control repository.|[Source control integration](../source-control-integration.md)|
151
+
|Change tracking and inventory|Verify that you see current inventory data from your machines.|[Troubleshoot change tracking](../troubleshoot/change-tracking.md)|
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.|
Copy file name to clipboardExpand all lines: articles/automation/how-to/region-mappings.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ After you remove these solutions, you can perform the following steps to unlink
53
53
54
54
1. From the Azure portal, open your Automation account. On the Automation account page, select **Linked workspace** under **Related Resources**.
55
55
56
-
2. On the Unlink workspace page, click **Unlink workspace**. You'll receive a prompt verifying if you wish to continue.
56
+
2. On the Unlink workspace page, click **Unlink workspace**. You receive a prompt verifying if you wish to continue.
57
57
58
58
3. While Azure Automation attempts to unlink the account your Log Analytics workspace, you can track the progress under **Notifications** from the menu.
59
59
@@ -68,7 +68,10 @@ After you remove these solutions, you can perform the following steps to unlink
68
68
* Start and stop VM runbooks
69
69
* Variables
70
70
71
-
Alternatively, you can unlink your workspace from your Automation account from your Log Analytics workspace. In the workspace, select **Automation Account** under **Related Resources**. On the Automation Account page, select **Unlink account**.
71
+
Alternatively, you can unlink your workspace from your Automation account within the workspace.
72
+
73
+
1. In the workspace, select **Automation Account** under **Related Resources**.
74
+
2. On the Automation Account page, select **Unlink account**.
0 commit comments