Extend alerts created in the Azure Government cloud's OMS portal to Azure
Published date: February 01, 2019
Azure Government customers who use the Microsoft Operations Management Suite portal (OMS portal) can now manage log query–based alerts for Azure Log Analytics in the OMS portal and in the Azure portal.
Beginning March 1, 2019, Microsoft will automatically extend alerts created in the Azure Government cloud's OMS portal to Azure alerts. Monitoring won't be affected, and there's no downtime. You don't have to change your alert definition, query, or configuration. The only change involved is that in Azure, actions like email notifications, webhook calls, running an automation runbook, or connecting to an IT service management (ITSM) tool are done via an action group.
You can access the benefits of using Azure alerts and action groups before March 1, 2019. To do this, manually extend your alerts from the OMS portal to Azure by using the wizard in the OMS portal or a REST API. Alerts that you created in the OMS portal will automatically extend to Azure beginning March 1, 2019. After this update, alerts will continue to be listed in the OMS portal. But, for all management actions, you will be taken to Azure alerts. For more information, see Extend alerts from the OMS portal to Azure.
If you access alerts programmatically by using the Log Analytics Alert REST API, you’ll need to use action groups instead of actions in your API calls, Azure Resource Manager templates, and PowerShell commands.
The alerts experience in Azure has a fresh look and updated functionality in Azure Government. The new alerts experience in Azure Government gives you a unified authoring experience and is generally available for Log Analytics alerts. With action groups, you can have more than one action for each alert, including SMS, voice call, automation runbook, webhook, and more.