Skip to content

Commit 4f85bab

Browse files
committed
edit pass: automation-articles-jd-batch2
1 parent 5298ba8 commit 4f85bab

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/automation/how-to/move-account.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ For this solution, you also need to remove the alert rules created by the soluti
5454

5555
1. In the Azure portal, go to your resource group and select **Monitoring** > **Alerts** > **Manage alert rules**.
5656

57-
![Screenshot of Alerts page, showing selection of Manage alert rules](../media/move-account/alert-rules.png)
57+
![Screenshot of Alerts page, showing selection of Manage alert rules](../media/move-account/alert-rules.png)
5858

5959
2. On the **Rules** page, you should see a list of the alerts configured in that resource group. The solution creates these rules:
6060

articles/automation/how-to/region-mappings.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ manager: carmonm
1313

1414
# Workspace mappings
1515

16-
In Azure Automation, you can enable the following solutions: "Update Management," "Change Tracking and Inventory," and "Start/Stop VMs during off-hours." When you do so, however, be aware that only certain regions are supported for linking a Log Analytics workspace and an Automation account in your subscription. This mapping only applies to the Automation account and the Log Analytics workspace. The Log Analytics workspace and Automation account must be in the same subscription, but can be in different resource groups deployed to the same region.
16+
In Azure Automation, you can enable the following solutions: "Update Management," "Change Tracking and Inventory," and "Start/Stop VMs during off hours." When you do so, however, be aware that only certain regions are supported for linking a Log Analytics workspace and an Automation account in your subscription. This mapping only applies to the Automation account and the Log Analytics workspace. The Log Analytics workspace and Automation account must be in the same subscription, but can be in different resource groups deployed to the same region.
1717

1818
For further information, see [Log Analytics workspace and Automation account](../../azure-monitor/insights/solutions.md#log-analytics-workspace-and-automation-account).
1919

@@ -46,7 +46,7 @@ The following table shows the supported mappings:
4646

4747
## Unlink a workspace
4848

49-
If you decide that you no longer want to integrate your Automation account with a Log Analytics workspace, you can unlink your account directly from the Azure portal. Before proceeding, you first need to remove "Update Management," "Change Tracking and Inventory," and "Start/Stop VMs during off-hours" if you are using them. If you don't remove them, you can't complete the unlinking operation. Review the article for each solution that you're enabling, in order to understand the steps required to remove it.
49+
If you decide that you no longer want to integrate your Automation account with a Log Analytics workspace, you can unlink your account directly from the Azure portal. Before proceeding, you first need to remove "Update Management," "Change Tracking and Inventory," and "Start/Stop VMs during off hours" if you are using them. If you don't remove them, you can't complete the unlinking operation. Review the article for each solution that you're enabling, in order to understand the steps required to remove it.
5050

5151
After you remove them, you can perform the following steps to unlink your Automation account.
5252

@@ -64,7 +64,7 @@ After you remove them, you can perform the following steps to unlink your Automa
6464
* Update schedules: Each has a name that matches an update deployment that you created.
6565
* Hybrid worker groups created for the solution: Each has a name similar to `machine1.contoso.com_9ceb8108-26c9-4051-b6b3-227600d715c8`.
6666

67-
5. If you used "Start/Stop VMs during off-hours," you can optionally remove the following items that aren't needed after you remove it.
67+
5. If you used "Start/Stop VMs during off hours," you can optionally remove the following items that aren't needed after you remove it.
6868

6969
* Start and stop VM runbook schedules
7070
* Start and stop VM runbooks
@@ -84,6 +84,6 @@ Alternatively, you can unlink your workspace from your Automation account within
8484
* When [browsing multiple machines](../automation-onboard-solutions-from-browse.md).
8585
* From a [runbook](../automation-onboard-solutions.md).
8686

87-
* Learn how to start using "Start/Stop VMs during off-hours":
87+
* Learn how to start using "Start/Stop VMs during off hours":
8888

89-
* [Start/Stop VMs during off-hours overview](../automation-solution-vm-management.md).
89+
* [Start/Stop VMs during off hours overview](../automation-solution-vm-management.md).

0 commit comments

Comments
 (0)