Supported regions for linked Log Analytics workspace
In Azure Automation, you can enable the Update Management, Change Tracking and Inventory, and Start/Stop VMs during off-hours features for your servers and virtual machines. These features have a dependency on a Log Analytics workspace, and therefore require linking the workspace with an Automation account. However, only certain regions are supported to link them together. In general, the mapping is not applicable if you plan to link an Automation account to a workspace that won't have these features enabled.
The mappings discussed here apply only to linking the Log Analytics Workspace to an Automation account. They do not apply to the virtual machines (VMs) that are connected to the workspace that's linked to the Automation Account. VMs aren't limited to the regions supported by a given Log Analytics workspace. They can be in any region. Keep in mind that having the VMs in a different region may affect state, local, and country regulatory requirements, or your company's compliance requirements. Having VMs in a a different region could also introduce data bandwidth charges.
Before connecting VMs to a workspace in a different region, you should review the requirements and potential costs to confirm and understand the legal and cost implications.
This article provides the supported mappings in order to successfully enable and use these features in your Automation account.
For more information, see Log Analytics workspace and Automation account.
As shown in following table, only one mapping can exist between Log Analytics and Azure Automation.
The following table shows the supported mappings:
|Log Analytics workspace region||Azure Automation region|
|United Arab Emirates|
1 EastUS mapping for Log Analytics workspaces to Automation accounts isn't an exact region-to-region mapping, but is the correct mapping.
2 EastUS2 mapping for Log Analytics workspaces to Automation accounts isn't an exact region-to-region mapping, but is the correct mapping.
3 In this region, only Update Management is supported, and other features like Change Tracking and Inventory are not available at this time.
Unlink a workspace
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.
With the features removed, you can follow the steps below to unlink your Automation account.
Some features, including earlier versions of the Azure SQL monitoring solution, might have created Automation assets that need to be removed prior to unlinking the workspace.
From the Azure portal, open your Automation account. On the Automation account page, select Linked workspace under Related Resources.
On the Unlink workspace page, select Unlink workspace. You receive a prompt verifying if you want to continue.
While Azure Automation is unlinking the account from your Log Analytics workspace, you can track the progress under Notifications from the menu.
If you used Update Management, optionally you might want to remove the following items that are no longer needed:
- Update schedules: Each has a name that matches an update deployment that you created.
- Hybrid worker groups created for the feature: Each has a name similar to
If you used Start/Stop VMs during off-hours, optionally you can remove the following items that are no longer needed:
- Start and stop VM runbook schedules
- Start and stop VM runbooks
Alternatively, you can unlink your workspace from your Automation account within the workspace.
- In the workspace, select Automation Account under Related Resources.
- On the Automation Account page, select Unlink account.
Submit and view feedback for