Skip to content

Commit 6cfc2f2

Browse files
committed
updating per feedback
1 parent ec041d6 commit 6cfc2f2

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

articles/automation/automation-onboard-solutions-from-browse.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ ms.custom: mvc
1414

1515
Azure Automation provides solutions to manage operating system security updates, track changes, and inventory what is installed on your computers. There are multiple ways to onboard machines, you can onboard the solution [from a virtual machine](automation-onboard-solutions-from-vm.md), from your [Automation account](automation-onboard-solutions-from-automation-account.md), when browsing virtual machines, or by [runbook](automation-onboard-solutions.md). This article covers onboarding these solutions when browsing virtual machines in Azure.
1616

17-
## Log in to Azure
17+
## Sign in to Azure
1818

19-
Log in to Azure at https://portal.azure.com
19+
Sign in to Azure at https://portal.azure.com
2020

2121
## Enable solutions
2222

@@ -129,7 +129,7 @@ When onboarding multiple machines, there may be machines that show as **Cannot e
129129

130130
**Cause**: Virtual machines that use the classic deployment model are not supported.
131131

132-
**Solution**: Migrate the virtual machine to the resource manager deployment model. To learn how to do this, see [Migrate classic deployment model resources](../virtual-machines/windows/migration-classic-resource-manager-overview.md).
132+
**Solution**: Migrate the virtual machine to the Resource Manager deployment model. To learn how to do this, see [Migrate classic deployment model resources](../virtual-machines/windows/migration-classic-resource-manager-overview.md).
133133

134134
### VM is stopped. (deallocated)
135135

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ manager: carmonm
1414

1515
When enabling solutions like Update Management, Change Tracking and Inventory, or the Start/Stop VMs during off-hours solution, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
1616

17+
## Supported mappings
18+
1719
The following table shows the supported mappings:
1820

1921
|**Log Analytics Workspace Region**|**Azure Automation Region**|
@@ -39,7 +41,7 @@ The following table shows the supported mappings:
3941

4042
<sup>2</sup> Due to capacity restraints the region is not available when creating new resources. This includes Automation Accounts and Log Analytics workspaces. However, preexisting linked resources in the region should continue to work.
4143

42-
### Next steps
44+
## Next steps
4345

4446
Learn how to onboard the following solutions:
4547

0 commit comments

Comments
 (0)