Skip to content

Commit f3eb25b

Browse files
committed
task7073260
1 parent 9236b18 commit f3eb25b

File tree

2 files changed

+28
-22
lines changed

2 files changed

+28
-22
lines changed

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

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,16 @@ ms.service: automation
66
ms.subservice: process-automation
77
author: mgoedtel
88
ms.author: magoedte
9-
ms.date: 05/20/2019
9+
ms.date: 04/23/2020
1010
ms.topic: conceptual
1111
manager: carmonm
1212
---
1313

1414
# Workspace mappings
1515

16-
When enabling solutions like Update Management, Change Tracking and Inventory, or Start/Stop VMs during off hours, only certain regions are supported for linking a Log Analytics workspace and an Automation account. This mapping only applies to the Automation account and the Log Analytics workspace. The resources reporting to your Automation account or Log Analytics workspace can reside in other regions.
16+
When enabling Update Management, Change Tracking and Inventory, or Start/Stop VMs during off-hours, 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.
17+
18+
For further information, see [Log Analytics workspace and Automation account](../azure-monitor/insights/solutions.md#log-analytics- workspace-and-automation-account).
1719

1820
## Supported mappings
1921

@@ -44,44 +46,44 @@ The following table shows the supported mappings:
4446

4547
## Unlink workspace
4648

47-
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 the Update Management, Change Tracking and Inventory, and Start/Stop VMs during off hours solutions if you are using them. If you do not remove them, you can't complete the unlinking operation. Review the article for the particular solution you've imported 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 do not remove them, you can't complete the unlinking operation. Review the article for each that you're enabling in order to understand the steps required to remove it.
4850

49-
After you remove these solutions, you can perform the following steps to unlink your Automation account.
51+
After you remove them, you can perform the following steps to unlink your Automation account.
5052

5153
> [!NOTE]
52-
> Some solutions including earlier versions of the Azure SQL monitoring solution might have created automation assets and might need to be removed prior to unlinking the workspace.
54+
> Some solutions including earlier versions of the Azure SQL monitoring solution might have created Automation assets and might need to be removed prior to unlinking the workspace.
5355
5456
1. From the Azure portal, open your Automation account. On the Automation account page, select **Linked workspace** under **Related Resources**.
5557

5658
2. On the Unlink workspace page, click **Unlink workspace**. You receive a prompt verifying if you wish to continue.
5759

5860
3. While Azure Automation attempts to unlink the account your Log Analytics workspace, you can track the progress under **Notifications** from the menu.
5961

60-
4. If you used the Update Management solution, optionally you might want to remove the following items that are no longer needed after you remove the solution.
62+
4. If you used Update Management, optionally you might want to remove the following items that are no longer needed after you remove it.
6163

6264
* Update schedules - Each has a name that matches an update deployment that you created.
6365
* Hybrid worker groups created for the solution - Each has a name similar to `machine1.contoso.com_9ceb8108-26c9-4051-b6b3-227600d715c8`.
6466

65-
5. If you used the Start/Stop VMs during off hours solution, you can optionally remove the following items that aren't needed after you remove the solution.
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.
6668

6769
* Start and stop VM runbook schedules
6870
* Start and stop VM runbooks
6971
* Variables
7072

71-
Alternatively, you can unlink your workspace from your Automation account within the workspace.
73+
Alternatively, you can unlink your workspace from your Automation account within the workspace.
7274

7375
1. In the workspace, select **Automation Account** under **Related Resources**.
7476
2. On the Automation Account page, select **Unlink account**.
7577

7678
## Next steps
7779

78-
* Learn how to onboard Update Management and Change Tracking and Inventory solutions:
80+
* Learn how to onboard Update Management and Change Tracking and Inventory:
7981

8082
* From a [virtual machine](../automation-onboard-solutions-from-vm.md)
8183
* From your [Automation account](../automation-onboard-solutions-from-automation-account.md)
8284
* When [browsing multiple machines](../automation-onboard-solutions-from-browse.md)
8385
* From a [runbook](../automation-onboard-solutions.md)
8486

85-
* Learn how to onboard the Start/Stop VMs during off hours solution:
87+
* Learn how to onboard the Start/Stop VMs during off-hours:
8688

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

articles/azure-monitor/insights/solutions.md

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,12 @@ ms.subservice: logs
55
ms.topic: conceptual
66
author: bwren
77
ms.author: bwren
8-
ms.date: 03/30/2020
8+
ms.date: 04/23/2020
99

1010
---
1111

1212
# Monitoring solutions in Azure Monitor
13+
1314
Monitoring solutions leverage services in Azure to provide additional insight into the operation of a particular application or service. This article provides a brief overview of monitoring solutions in Azure and details on using and installing them.
1415

1516
> [!NOTE]
@@ -22,6 +23,7 @@ You can add monitoring solutions to Azure Monitor for any applications and servi
2223
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-log-analytics-rebrand.md)]
2324

2425
## Use monitoring solutions
26+
2527
Open the **Overview** page in Azure Monitor to display a tile for each solution installed in the workspace.
2628

2729
1. Go to the [Azure portal](https://ms.portal.azure.com). Search for and select **Monitor**.
@@ -33,7 +35,8 @@ Open the **Overview** page in Azure Monitor to display a tile for each solution
3335

3436
Monitoring solutions can contain multiple types of Azure resources, and you can view any resources included with a solution just like any other resource. For example, any log queries included in the solution are listed under **Solution Queries** in [Query explorer](../log-query/get-started-portal.md#load-queries) You can use those queries when performing ad hoc analysis with [log queries](../log-query/log-query-overview.md).
3537

36-
## List installed monitoring solutions
38+
## List installed monitoring solutions
39+
3740
Use the following procedure to list the monitoring solutions installed in your subscription.
3841

3942
1. Go to the [Azure portal](https://ms.portal.azure.com). Search for and select **Solutions**.
@@ -47,9 +50,8 @@ Click on the name of a solution to open its summary page. This page displays any
4750

4851
![Solution properties](media/solutions/solution-properties.png)
4952

50-
51-
5253
## Install a monitoring solution
54+
5355
Monitoring solutions from Microsoft and partners are available from the [Azure Marketplace](https://azuremarketplace.microsoft.com). You can search available solutions and install them using the following procedure. When you install a solution, you must select a [Log Analytics workspace](../platform/manage-access.md) where the solution will be installed and where its data will be collected.
5456

5557
1. From the [list of solutions for your subscription](#list-installed-monitoring-solutions), click **Add**.
@@ -61,6 +63,7 @@ Monitoring solutions from Microsoft and partners are available from the [Azure M
6163
![Install a solution](media/solutions/install-solution.png)
6264

6365
### Install a solution from the community
66+
6467
Members of the community can submit management solutions to Azure Quickstart Templates. You can install these solutions directly or download them templates for later installation.
6568

6669
1. Follow the process described in [Log Analytics workspace and Automation account](#log-analytics-workspace-and-automation-account) to link a workspace and account.
@@ -71,28 +74,29 @@ Members of the community can submit management solutions to Azure Quickstart Tem
7174
6. You're prompted to provide information such as the resource group and location in addition to values for any parameters in the solution.
7275
7. Click **Purchase** to install the solution.
7376

74-
7577
## Log Analytics workspace and Automation account
78+
7679
All monitoring solutions require a [Log Analytics workspace](../platform/manage-access.md) to store data collected by the solution and to host its log searches and views. Some solutions also require an [Automation account](../../automation/automation-security-overview.md#automation-account-overview) to contain runbooks and related resources. The workspace and account must meet the following requirements.
7780

7881
* Each installation of a solution can only use one Log Analytics workspace and one Automation account. You can install the solution separately into multiple workspaces.
7982
* If a solution requires an Automation account, then the Log Analytics workspace and Automation account must be linked to one another. A Log Analytics workspace may only be linked to one Automation account, and an Automation account may only be linked to one Log Analytics workspace.
80-
* To be linked, the Log Analytics workspace and Automation account must be in the same resource group and region. The exception is a workspace in East US region and Automation account in East US 2.
83+
* To be linked, 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. The exception is a workspace in East US region and Automation account in East US 2.
8184

8285
When you install a solution through the Azure Marketplace, you're prompted for a workspace and Automation account. The link between them is created if they aren't already linked.
8386

8487
### Verify the link between a Log Analytics workspace and Automation account
88+
8589
You can verify the link between a Log Analytics workspace and an Automation account using the following procedure.
8690

8791
1. Select the Automation account in the Azure portal.
88-
1. Scroll to the **Related Resources** section of the menu.
89-
1. If the **Workspace** setting is enabled, then this account is linked to a Log Analytics workspace. You can click on **Workspace** to view the details of the workspace.
92+
1. Scroll to the **Related Resources** section of the menu and select **Linked workspace**.
93+
1. If the **Workspace** is linked to an Automation account, then this page lists the workspace it is linked to. You can click on the name of the linked workspace listed and you are redirected to the overview page for that workspace.
9094

9195
## Remove a monitoring solution
92-
To remove an installed solution, locate it in the [list of installed solutions](#list-installed-monitoring-solutions). Click on the name of the solution to open its summary page and then click on **Delete**.
9396

97+
To remove an installed solution, locate it in the [list of installed solutions](#list-installed-monitoring-solutions). Click on the name of the solution to open its summary page and then click on **Delete**.
9498

9599
## Next steps
96-
* Get a [list of monitoring solutions from Microsoft](solutions-inventory.md).
97-
* Learn how to [create queries](../log-query/log-query-overview.md) to analyze data collected by monitoring solutions.
98100

101+
* Get a [list of monitoring solutions from Microsoft](solutions-inventory.md).
102+
* Learn how to [create queries](../log-query/log-query-overview.md) to analyze data collected by monitoring solutions.

0 commit comments

Comments
 (0)