Loading...

Announcing the Public Preview of Alerting on Azure Resource Graph

Announcing the Public Preview of Alerting on Azure Resource Graph

Azure Resource Graph is an Azure service designed to provide efficient and performant resource exploration with the ability to query at scale across a given set of subscriptions so that you can effectively govern your environment. While customers could provide complex queries to get visibility into their environments, there was no easy way to proactively identify issues and get notified. 

We are happy to announce that you can enable alerts on Azure Resource Graph queries using Azure Monitor alerting. With this feature, you have the option to customize alerts based on the results of your ARG (Azure Resource Graph) queries. This means that not only can you gain insights from your resource data, but you can also take proactive actions when predefined criteria are met.

 

How to Get Started

To create an alert on ARG queries, you need to have a Log Analytics Workspace and a Managed identity with reader permission for the resource.  Here is a basic guide to help you set up your first ARG alert.  

  1. Go to Azure portal to access Azure Monitor and click on either Alerts or Logs.  
  2. From the Logs query builder, craft Azure Resource Graph queries and execute them to obtain results by utilizing the specified prefix arg("").Table_name as shown in the picture below.
    Saandrine_0-1699904898951.pngarg("").resourcechanges | extend Target = tostring(properties.targetResourceType), changeType = tostring(properties.changeType), targetResourceId = tostring(properties.targetResourceId), timestamp = todatetime(properties.changeAttributes.timestamp), correlationId = todatetime(properties.changeAttributes.correlationId) | where changeType == "Delete"
  3. After checking the results, click on “New alert rule” and follow the steps from choosing the Log Analytics workspace previously created as the scope of the rule execution to “create” the alert rule. 

Sample Scenarios & Examples 

Alert on Failed update runs

 

arg("").maintenanceresources | extend failed = toint(properties.resourceUpdateSummary.failed), timeout = toint(properties.resourceUpdateSummary.timedout), maintenanceId = tostring(properties.maintenanceConfigurationId), EndTime = todatetime(properties.endDateTime) | where failed > 0 or timeout > 0 | where EndTime > ago(12h) | summarize Failed=count() by maintenanceId

 

 

Alert on VMs (Virtual Machines) needing patches

 

arg("").patchassessmentresources | where type has "softwarepatches" | extend id = tolower(id) | parse id with resourceId "/patchassessmentresults" * | where isnotnull(properties.kbId) | extend MissingUpdate = tostring(properties.patchName), Classification = tostring(properties.classifications[0]) | extend UpdatesNeeded = pack_array(MissingUpdate, Classification) | summarize UpdatesNeeded = make_set(UpdatesNeeded), Count= count() by resourceId

 

 

Related Resources 

To learn about this exciting capability, refer to:

 

This is one of many features that we plan to bring to you for rich alerting capabilities on Azure Resource Graph queries. We want to build featuresthat will help you quickly identify issues within your IT landscape, whichis why we would appreciate your feedback and collaboration opportunity here. We look forward toworkingwith you as we build out the alerting on Azure Resource Graph capabilities.

 

Happy Alerting!

 

Feedback 

If you have any feedback for Azure Resource Graph service, post your ideas here. If you're just getting started with Azure Resource Graph, you can learn about the service hereand follow us on Twitter for the latest updates.  

Published on:

Learn more
Azure Governance and Management Blog articles
Azure Governance and Management Blog articles

Azure Governance and Management Blog articles

Share post:

Related posts

Microsoft to Retire Together Mode for Teams Meetings

In a somewhat decision, Microsoft announced plans to retire the Together mode feature for Teams meetings in June 2026. Based on personal exper...

2 hours ago

Python support for the Microsoft Teams SDK is now generally available

Python developers can now build Teams-native apps and agents using the same SDK surface that powers modern Teams experiences across our TypeSc...

2 days ago

Microsoft 365 Copilot : 5 nouveautés à connaître pour votre PME

Microsoft continue d'enrichir Microsoft 365 Copilot à un rythme soutenu, et la dernière vague d'annonces met clairement la barre plus haut pou...

2 days ago

Introducing langchain-azure-cosmosdb: Build Agentic Apps and RAG with One Database

Build AI Agents and RAG Applications with the New LangChain + LangGraph Connector for Azure Cosmos DB Building AI agents and RAG applications ...

2 days ago

Updates available for Microsoft 365 Apps for Current Channel

We’ve released updates to the following update channel for Microsoft 365 Apps: Current Channel When this will happen: We’ll be gra...

3 days ago

Microsoft 365 Copilot: Legal Agent for Word

Microsoft 365 introduces Legal Agent for Word, a Copilot feature for US legal professionals in the Frontier Public Preview (April 2026). It he...

3 days ago

Microsoft 365 Copilot: Claude Sonnet 4.5 retiring for Copilot Studio (automatic migration to Claude Sonnet 4.6)

Claude Sonnet 4.5 in Microsoft Copilot Studio will retire by May 30, 2026, with automatic migration to Claude Sonnet 4.6 starting then. An eva...

3 days ago

Introducing Calendar Agent capabilities in Microsoft 365 Copilot

Microsoft 365 Copilot introduces Calendar Agent capabilities to automate calendar management via natural-language instructions, helping users ...

3 days ago

Teams Phone call transfer improvements

Microsoft Teams is enhancing desktop call transfers by separating Transfer and Consult transfer into single-click buttons, adding suggested tr...

3 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy