I hope someone from the product team can fix this.
When connecting SCOM 2019 (though I assume this would be an issue with earlier versions aswell) to an Azure Log Analytics workspace the establishment of the connection fails if the Log Analytics workspace is provisioned anywhere else other than "Australia South East".
If the Log Workspace is setup in Australia East or Australia Central - SCOM cannot connect to it.
For example if it's Australia Central - the error is...
System.ServiceModel.EndpointNotFoundException:There was no endpoint listening at https://cau.service.opinsights.azure.com/Config/SettingService.svc/ServiceSettings that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote name could not be resolved: 'cau.service.opinsights.azure.com'
Same error for Australia East except the DNS name eau.service.opinsights.azure.com can't be found.
Both eau.service.opinsights.azure.com and cau.service.opinsights.azure.com cannot be resolved on the public internet (probably because they don't exist).
However if the Log Analytics workspace is setup in Australia South East, the name seau.service.opinsights.azure.com can be resolved publically, and SCOM can also connect to the workspace.
Is someone able to sort this out? Azure Log Analytics went GA last month for Australia East and Central, but the missing DNS entries mean products like SCOM can't connect to them.