This small change is no doubt related to the new name change of the service but also to help facilitate preparations for when they go live with some new Azure regions.
Essentially, the change will only affect sites that are running a connected SCOM-OpInsights scenario behind a proxy and with specific rules in place allowing connection to only certain URL destinations.
IMPORTANT for OpInsights users!
If you are using OpsMgr with Azure Operational Insights behind proxies with specific ACL or rules to only allow traffic to specific destination, please note the following upcoming change that would require an action in your environment.
In order to align the way that OpsMgr and direct agent send data to the service, and as we are making preparations to have a presence in more Azure regions, we have to make a ONE-TIME change to the URLs that the management packs use to post data to OpInsights:
Where in the past OpsMgr would be talking to ods.systemcenteradvisor.com , with an upcoming deployment (possibly mid of this week, we will update our blog post closer to the deployment as we have a more specific date) OpsMgr will instead start reporting to <yourworkspaceid>.ods.opinsights.azure.com. We recommend you update your firewall/proxy’s ACLs/rules to allow traffic to the new destination *.ods.opinsights.azure.com or your data would start either queuing up on OpsMgr and/or eventually being dropped if the new destination can’t be reached.
As the new management packs will be received, the system will start reporting to the new URL, and you can later remove the previous ods.systemcenteradvisor.com entry which won’t be needed any longer.
There's also a really quick survey that you can take to give some constructive feedback to Microsoft on how you use proxies with OpInsights and SCOM - this can go a long way in helping them understand how future integrated scenarios will be delivered.