Azure Resource Graph
by Microsoft
Azure Resource Graph answers KQL queries across every subscription a principal can see, returning resources with their tags and properties, recent resource changes, policy compliance states and Advisor findings. Platform teams use it to inventory Azure at scale. A daily snapshot in the Lake keeps a longer history than Resource Graph holds, and lets ownership, cost and compliance be read together.
- Category
- Cloud & Data Platforms
- Type
- Cloud inventory & governance
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0, Service account key
02Data
What you can sync.
- Resources
- Resource changes
- Policy compliance
- Advisor resources
Load Azure Resource Graph resources into your Lake and model it in the Warehouse with the rest of your stack.
Need more? Name any other Azure Resource Graph data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
- A service account key
Azure Resource Graph uses OAuth 2.0 (client ID, client secret, refresh token) or a service account key. You add the credentials once, when the AI asks for them, and it tells you where to create them in Microsoft if you need help.
04Questions
Questions you can answer.
Once Azure Resource Graph data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- Which resources have no owner tag, and how much do they cost?
- Which policy assignments have the most noncompliant resources by subscription?
- Which resources were created or deleted in production last week?
- How many virtual machines run operating system versions we no longer support?
05How it works
How it works in DataMind.
-
Pick Azure Resource Graph.
Open Lake, pick Azure Resource Graph in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Azure Resource Graph API docs.
-
Answer a few questions.
The AI reads the Azure Resource Graph documentation, then asks which credentials you will use, which data to sync (for example resources and resource changes), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Azure Resource Graph data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Pairs
Works well with Azure Resource Graph.
Sources teams join with Azure Resource Graph in the Warehouse, each one connected the same way.
