Alerts created in the Operations Management Suite portal can extend into Azure
Updated: April 13, 2018
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 May 14, 2018, Microsoft will automatically extend alerts created in the OMS portal into 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 ITSM tool are done via an action group.
You can access the benefits of using Azure alerts and action groups before May 14, 2018. To do this, manually extend your alerts from the OMS portal into 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 May 14, 2018. After this update, alerts will continue to be listed in the OMS portal. But, for all management actions, you will be transparently taken to Azure alerts.
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. The new alerts experience gives you a unified authoring experience for metric, activity, and log alert rules. You can manage, enumerate, and view all your alert types, not only Log Analytics alerts. With action groups, you can have more than one action for each alert, including SMS, voice call, automation runbook, webhook, ITSM connector, and more.
For more information, see Extend alerts from the OMS portal into Azure.