I am hoping to use the State configuration (DSC) capability of Azure Automation accounts to manage configuration of various Windows VMs. I've successfully created a Configuration, registered a VM, and applied the configuration - it works!
However, that VM was in Central US region. I cannot seem to register VMs that are in the East US 2 region with the Automation Account.
I even tried creating an automation account that itself is in the East US2 region, but no luck. When I try to manually add a node (using Azure portal) the VMs in that region aren't listed. The interface for adding a node has filters to reduce the VMs listed. East US2 region doesn't even show up as an option to filtering against. Other regions show up, but not East US2.
No avail with PowerShell
```powershell
Register-AzAutomationDscNode -AutomationAccountName "aa-eastus2" -AzureVMName "vm-eastus2" -ResourceGroupName "rg-eastus2" -NodeConfigurationName "HelloWorld.localhost" -AzureVMResourceGroup "rg-eastus2-controllers"
```
Results in
```
Register-AzAutomationDscNode: One or more errors occurred. (Long running operation failed with status 'Failed'. Additional Info:'At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.')
```
When I look at deployment history in the resource group of the VM I am attempting to register, I see error:
```json
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
"details": [
{
"code": "NotFound",
"message": "The entity was not found in this Azure location."
}
]
}
```
Please help me understand how regions relate to Automation State Configuration capability.
