> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Azure on Vortex IQ > Monitor Microsoft Azure health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Microsoft Azure health, cost and reliability signals, and catch incidents and runaway spend early. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) ยท [How connecting works](/integrations/connector-catalogue) | **20** | **3** | **Build your own** | **Ready to build yours** | **3** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 20 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher. | Signal | Outcome | Alert behaviour | What it tracks | | -------------------------------- | ----------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Azure Spend (30d)** | Run operations | Alert band 10 / 50 | Sum of Cost over the last 30d of daily rows from the CostManagement/query 60d Daily ActualCost response; change vs the previous 30d window. Cost Management Reader role re | | **Cloud Health Score** | Run operations | Alert band 90 / 70 | Composite 0-100: start at 100, minus 30 if 30d spend is up >50% vsP (15 if up >25%), minus 10 if the top service is >80% of 30d spend, minus 20 if subscription state is n | | **Cost by Service (30d)** | Run operations | Watch only | Cost summed per ServiceName over the last 30d of the CostManagement/query rows; top 10 services by spend. | | **Active Services (30d)** | Run operations | Watch only | Count of distinct ServiceName values with Cost > 0 in the last 30d of the cost rows. | | **Annualised Run Rate** | Run operations | Watch only | Avg daily spend (30d Cost sum / days with spend) x 365; what the current burn costs over a year. | | **Avg Cost per Service (30d)** | Run operations | Watch only | 30d Cost sum / count of distinct ServiceName values with Cost > 0 in the window. | | **Avg Daily Spend (30d)** | Run operations | Watch only | 30d Cost sum / count of distinct UsageDate values with Cost > 0 in the window. | | **Azure Spend (7d)** | Run operations | Watch only | Sum of Cost for daily rows with UsageDate in the last 7 days. | | **Billing Currency** | Run operations | Watch only | Currency column value from the CostManagement/query rows (e.g. USD, GBP); also drives the currency symbol on every spend card. | | **Daily Spend Trend** | Run operations | Watch only | Cost summed per UsageDate over the last 30d of the CostManagement/query Daily rows. | | **Days with Spend (30d)** | Run operations | Watch only | Count of distinct UsageDate values with Cost > 0 in the last 30d; gaps mean idle days or missing cost data. | | **Month-to-Date Spend** | Run operations | Watch only | Sum of Cost for daily rows with UsageDate on or after the 1st of the current month, from the same CostManagement/query response. | | **New Cost Services (30d)** | Run operations | Watch only | Count of ServiceName values with Cost > 0 in the current 30d window but zero cost in the previous 30d window; new services quietly adding spend. | | **Peak Daily Spend (30d)** | Run operations | Watch only | Max of the per-UsageDate Cost sums over the last 30d; detail names the peak day. | | **Previous 30d Spend** | Run operations | Watch only | Sum of Cost over the previous 30d window (days 31-60) of the same 60d Daily cost response; the vsP baseline. | | **Service Concentration (30d)** | Run operations | Watch only | Top service 30d Cost sum / total 30d Cost sum x 100; a very concentrated bill is a single point of cost failure. | | **Spend Change vs Previous 30d** | Run operations | Watch only | (current 30d Cost sum - previous 30d Cost sum) / previous 30d Cost sum x 100, from the 60d Daily cost rows. | | **Spend Spike Alert** | Run operations | Alert band 10 / 50 | Spend change vs the prior 30d from the 60d Daily cost rows; fires on a spike per the ai\_spend\_trend band. | | **Subscription State** | Control risk and change | Watch only | state from GET /subscriptions/{subscription_id} (api-version=2022-12-01), e.g. Enabled or Disabled; detail shows displayName. Renders with the token + subscription read a | | **Top Service by Cost (30d)** | Run operations | Watch only | The single largest ServiceName by 30d Cost sum; detail names the service. | ## Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. | Check | Severity | Outcome | Why it matters | Fix status | | ------------------------------------------------------------------ | -------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **API key invalid, expired or lacking the scopes the cards need** | high | Control risk and change | Once this credential fails, VortexIQ stops seeing usage, cost and health data from this platform entirely, and every finding here that depends on it goes stale from that moment, silently, un | Report only | | **Spend up more than 50% vs the prior period** | high | Run operations | Spend on this platform rose more than 50% versus the prior period. A jump this size is either a deliberate scale-up worth confirming was intentional, or an unbounded process, a stuck job, a | Report only | | **Usage dropped more than 50% vs the prior period (silent stall)** | medium | Control risk and change | Usage halving against the prior period is the earliest sign of a silent stall: a broken schedule, an expired credential, or a team that quietly stopped. | Report only | ### Build your own automated fixes 3 checks report findings on Microsoft Azure today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change. ## Automate approved work Vortex IQ is integrated with **1 read** and **2 write** operations across oauth2tokens, subscriptions, subscription providermicrosoftcostmanagementquerys on Microsoft Azure. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=azure) | Resource | Read operations | Write operations | | -------------------------------------------------- | --------------- | ---------------- | | oauth2tokens | 0 | 1 | | subscriptions | 1 | 0 | | subscription providermicrosoftcostmanagementquerys | 0 | 1 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready to build your first Microsoft Azure workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*