Merge pull request #221972 from SnehaSudhirG/20Dec-AUM-Regionsupport

added new region

Author: ttorble

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

@@ -14,7 +14,7 @@ ms.custom: references_regions, engagement-fy23
 
 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.
+The mappings discussed here applying only to linking the Log Analytics Workspace to an Automation account. They don't 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 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.
 
@@ -31,61 +31,63 @@ The following table shows the supported mappings:
 
 |**Log Analytics workspace region**|**Azure Automation region**|
 |---|---|
-|**US**||
-|EastUS<sup>1</sup>|EastUS2|
-|EastUS2<sup>2</sup>|EastUS|
-|WestUS|WestUS|
-|WestUS2|WestUS2|
-|NorthCentralUS|NorthCentralUS|
-|CentralUS|CentralUS|
-|SouthCentralUS|SouthCentralUS|
-|WestCentralUS|WestCentralUS|
+|**Asia Pacific**||
+|EastAsia|EastAsia|
+|SoutheastAsia|SoutheastAsia|
+|**Australia**||
+|AustraliaEast|AustraliaEast|
+|AustraliaSoutheast|AustraliaSoutheast|
 |**Brazil**||
 |BrazilSouth|BrazilSouth|
 |**Canada**||
 |CanadaCentral|CanadaCentral|
 |**China**||
 |ChinaEast2<sup>3</sup>|ChinaEast2|
-|**Asia Pacific**||
-|EastAsia|EastAsia|
-|SoutheastAsia|SoutheastAsia|
+|**Europe**||
+|NorthEurope|NorthEurope|
+|WestEurope|WestEurope|
+|**France**||
+|FranceCentral|FranceCentral|
 |**India**||
 |CentralIndia|CentralIndia|
 |**Japan**||
 |JapanEast|JapanEast|
-|**Australia**||
-|AustraliaEast|AustraliaEast|
-|AustraliaSoutheast|AustraliaSoutheast|
 |**Korea**||
 |KoreaCentral|KoreaCentral|
 |**Norway**||
 |NorwayEast|NorwayEast|
-|**Europe**||
-|NorthEurope|NorthEurope|
-|WestEurope|WestEurope|
-|**France**||
-|FranceCentral|FranceCentral|
-|**United Kingdom**
-|UKSouth|UKSouth|
+|**Qatar**||
+|QatarCentral|QatarCentral|
 |**Switzerland**||
 |SwitzerlandNorth|SwitzerlandNorth|
 |**United Arab Emirates**||
 |UAENorth|UAENorth|
+|**United Kingdom**
+|UK South|UK South|
 |**US Gov**||
-|USGovVirginia|USGovVirginia|
 |USGovArizona<sup>3</sup>|USGovArizona|
+|USGovVirginia|USGovVirginia|
+|**US**||
+|EastUS<sup>1</sup>|EastUS2|
+|EastUS2<sup>2</sup>|EastUS|
+|CentralUS|CentralUS|
+|NorthCentralUS|NorthCentralUS|
+|SouthCentralUS|SouthCentralUS|
+|WestUS|WestUS|
+|WestUS2|WestUS2|
+|WestCentralUS|WestCentralUS|
 
 <sup>1</sup> EastUS mapping for Log Analytics workspaces to Automation accounts isn't an exact region-to-region mapping, but is the correct mapping.
 
 <sup>2</sup> EastUS2 mapping for Log Analytics workspaces to Automation accounts isn't an exact region-to-region mapping, but is the correct mapping.
 
-<sup>3</sup> In this region, only Update Management is supported, and other features like Change Tracking and Inventory are not available at this time.
+<sup>3</sup> In this region, only Update Management is supported, and other features like Change Tracking and Inventory aren't 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](move-account.md#remove-features) 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.
+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](move-account.md#remove-features) Update Management, Change Tracking and Inventory, and Start/Stop VMs during off-hours if you're 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.
+With the features removed, you can follow the steps to unlink your Automation account.
 
 > [!NOTE]
 > 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.