Skip to content

Commit 69f7869

Browse files
ktoliverktoliver
authored
Merge pull request #77077 from georgewallace/gw_mappings
region mappings
2 parents 27b2c4e + 6cfc2f2 commit 69f7869

File tree

5 files changed

+75
-69
lines changed

5 files changed

+75
-69
lines changed

‎articles/automation/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,8 @@
4242
href: automation-onboard-solutions-from-vm.md
4343
- name: Onboard from Automation account
4444
href: automation-onboard-solutions-from-automation-account.md
45+
- name: Region mappings
46+
href: how-to/region-mappings.md
4547
- name: Update Management
4648
items:
4749
- name: Update Management overview

‎articles/automation/automation-onboard-solutions-from-automation-account.md

Lines changed: 4 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -26,27 +26,10 @@ Choose the Log Analytics workspace and Automation account and click **Enable** t
2626

2727
![Onboard Inventory solution](media/automation-onboard-solutions-from-automation-account/onboardsolutions.png)
2828

29-
When enabling solutions, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
30-
31-
The following table shows the supported mappings:
32-
33-
|**Log Analytics Workspace Region**|**Azure Automation Region**|
34-
|---|---|
35-
|AustraliaSoutheast|AustraliaSoutheast|
36-
|CanadaCentral|CanadaCentral|
37-
|CentralIndia|CentralIndia|
38-
|EastUS<sup>1</sup>|EastUS2|
39-
|JapanEast|JapanEast|
40-
|SoutheastAsia|SoutheastAsia|
41-
|WestCentralUS<sup>2</sup>|WestCentralUS<sup>2</sup>|
42-
|WestEurope|WestEurope|
43-
|UKSouth|UKSouth|
44-
|USGovVirginia|USGovVirginia|
45-
|EastUS2EUAP<sup>1</sup>|CentralUSEUAP|
46-
47-
<sup>1</sup> EastUS2EUAP and EastUS mappings for Log Analytics workspaces to Automation Accounts are not an exact region to region mapping but is the correct mapping.
48-
49-
<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.
29+
> [!NOTE]
30+
> When enabling solutions, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
31+
>
32+
> For a list of the supported mapping pairs, see [Region mapping for Automation Account and Log Analytics workspace](how-to/region-mappings.md).
5033
5134
The Change Tracking and Inventory solution provides the ability to [track changes](automation-vm-change-tracking.md) and [inventory](automation-vm-inventory.md) on your virtual machines. In this step, you enable the solution on a virtual machine.
5235

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

Lines changed: 7 additions & 24 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

@@ -53,27 +53,10 @@ If the workspace selected is not linked to an Automation Account, you'll see the
5353

5454
![No workspace](media/automation-onboard-solutions-from-browse/no-workspace.png)
5555

56-
When enabling solutions, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
57-
58-
The following table shows the supported mappings:
59-
60-
|**Log Analytics Workspace Region**|**Azure Automation Region**|
61-
|---|---|
62-
|AustraliaSoutheast|AustraliaSoutheast|
63-
|CanadaCentral|CanadaCentral|
64-
|CentralIndia|CentralIndia|
65-
|EastUS<sup>1</sup>|EastUS2|
66-
|JapanEast|JapanEast|
67-
|SoutheastAsia|SoutheastAsia|
68-
|WestCentralUS<sup>2</sup>|WestCentralUS<sup>2</sup>|
69-
|WestEurope|WestEurope|
70-
|UKSouth|UKSouth|
71-
|USGovVirginia|USGovVirginia|
72-
|EastUS2EUAP<sup>1</sup>|CentralUSEUAP|
73-
74-
<sup>1</sup> EastUS2EUAP and EastUS mappings for Log Analytics workspaces to Automation Accounts are not an exact region to region mapping but is the correct mapping.
75-
76-
<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.
56+
> [!NOTE]
57+
> When enabling solutions, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
58+
>
59+
> For a list of the supported mapping pairs, see [Region mapping for Automation Account and Log Analytics workspace](how-to/region-mappings.md).
7760
7861
Deselect the checkbox next to any virtual machine that you don't want to enable. Virtual machines that can't be enabled are already deselected.
7962

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

147130
**Cause**: Virtual machines that use the classic deployment model are not supported.
148131

149-
**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).
150133

151134
### VM is stopped. (deallocated)
152135

‎articles/automation/automation-solution-vm-management.md

Lines changed: 5 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -85,30 +85,6 @@ To deploy the Start/Stop VMs during off hours solution to a new Automation Accou
8585
| Microsoft.Automation/automationAccounts/write | Resource Group |
8686
| Microsoft.OperationalInsights/workspaces/write | Resource Group |
8787

88-
### Region mappings
89-
90-
When enabling Start/Stop VMs during off-hours, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
91-
92-
The following table shows the supported mappings:
93-
94-
|**Log Analytics Workspace Region**|**Azure Automation Region**|
95-
|---|---|
96-
|AustraliaSoutheast|AustraliaSoutheast|
97-
|CanadaCentral|CanadaCentral|
98-
|CentralIndia|CentralIndia|
99-
|EastUS<sup>1</sup>|EastUS2|
100-
|JapanEast|JapanEast|
101-
|SoutheastAsia|SoutheastAsia|
102-
|WestCentralUS<sup>2</sup>|WestCentralUS<sup>2</sup>|
103-
|WestEurope|WestEurope|
104-
|UKSouth|UKSouth|
105-
|USGovVirginia|USGovVirginia|
106-
|EastUS2EUAP<sup>1</sup>|CentralUSEUAP|
107-
108-
<sup>1</sup> EastUS2EUAP and EastUS mappings for Log Analytics workspaces to Automation Accounts are not an exact region to region mapping but is the correct mapping.
109-
110-
<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.
111-
11288
## Deploy the solution
11389

11490
Perform the following steps to add the Start/Stop VMs during off-hours solution to your Automation account, and then configure the variables to customize the solution.
@@ -135,6 +111,11 @@ Perform the following steps to add the Start/Stop VMs during off-hours solution
135111
- Select a **Location**. Currently, the only locations available are **Australia Southeast**, **Canada Central**, **Central India**, **East US**, **Japan East**, **Southeast Asia**, **UK South**, **West Europe**, and **West US 2**.
136112
- Select a **Pricing tier**. Choose the **Per GB (Standalone)** option. Azure Monitor logs has updated [pricing](https://azure.microsoft.com/pricing/details/log-analytics/) and the Per GB tier is the only option.
137113

114+
> [!NOTE]
115+
> When enabling solutions, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
116+
>
117+
> For a list of the supported mapping pairs, see [Region mapping for Automation Account and Log Analytics workspace](how-to/region-mappings.md).
118+
138119
5. After providing the required information on the **Log Analytics workspace** page, click **Create**. You can track its progress under **Notifications** from the menu, which returns you to the **Add Solution** page when done.
139120
6. On the **Add Solution** page, select **Automation account**. If you're creating a new Log Analytics workspace, you can create a new Automation account to be associated with it, or select an existing Automation Account that is not already linked to a Log Analytics workspace. Select an existing Automation Account or click **Create an Automation account**, and on the **Add Automation account** page, provide the following information:
140121
- In the **Name** field, enter the name of the Automation account.

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

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
title: Azure Automation and Log Analytics workspace mappings
3+
description: This article describes the mappings allowed between an Automation Account and a Log Analytics Workspace to support solution
4+
services: automation
5+
ms.service: automation
6+
ms.subservice: process-automation
7+
author: georgewallace
8+
ms.author: gwallace
9+
ms.date: 05/20/2019
10+
ms.topic: conceptual
11+
manager: carmonm
12+
---
13+
# Workspace mappings
14+
15+
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.
16+
17+
## Supported mappings
18+
19+
The following table shows the supported mappings:
20+
21+
|**Log Analytics Workspace Region**|**Azure Automation Region**|
22+
|---|---|
23+
|**US**||
24+
|EastUS<sup>1</sup>|EastUS2|
25+
|WestUS2|WestUS2|
26+
|WestCentralUS<sup>2</sup>|WestCentralUS<sup>2</sup>|
27+
|**Canada**||
28+
|CanadaCentral|CanadaCentral|
29+
|**Asia Pacific**||
30+
|AustraliaSoutheast|AustraliaSoutheast|
31+
|SoutheastAsia|SoutheastAsia|
32+
|CentralIndia|CentralIndia|
33+
|JapanEast|JapanEast|
34+
|**Europe**||
35+
|UKSouth|UKSouth|
36+
|WestEurope|WestEurope|
37+
|**US Gov**||
38+
|USGovVirginia|USGovVirginia|
39+
40+
<sup>1</sup> EastUS mapping for Log Analytics workspaces to Automation Accounts are not an exact region to region mapping but is the correct mapping.
41+
42+
<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.
43+
44+
## Next steps
45+
46+
Learn how to onboard the following solutions:
47+
48+
Update Management and Change Tracking and Inventory:
49+
50+
* From a [virtual machine](../automation-onboard-solutions-from-vm.md)
51+
* From your [Automation account](../automation-onboard-solutions-from-automation-account.md)
52+
* When [browsing multiple machines](../automation-onboard-solutions-from-browse.md)
53+
* From a [runbook](../automation-onboard-solutions.md)
54+
55+
Start/Stop VMs during off-hours
56+
57+
* [Deploy Start/Stop VMs during off-hours](../automation-solution-vm-management.md)

0 commit comments

Comments
 (0)