Source connector

Microsoft Azure connector

Microsoft Azure integration for databases, warehouses and BI tools

Azure subscription resources, usage, and billing. Datrise captures Microsoft Azure entities such as subscriptions, resource groups, resources, usage records, costs and activity logs, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Azure Monitor Metrics REST API (2023-10-01) + Azure Resource Graph Query API (2022-10-01) + Activity Log REST API authenticates with OAuth 2.0, service account, incremental runs key on timespan / eventTimestamp window, and Microsoft Azure caps calls at Azure Resource Graph: 15 queries per rolling 5-second window per security principal by default (reported via x-ms-user-quota-remaining/x-ms-user-quota-resets-after headers, subject to change); Azure Monitor Metrics and the Activity Log share the general Azure Resource Manager throttling limits, which are hard per-subscription/per-tenant quotas rather than one published number.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `microsoft_azure_subscriptions`) with a schema derived from the Microsoft Azure API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Microsoft Azure pipeline page, and join the waitlist to get the Microsoft Azure connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Microsoft Azure data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
subscriptions	microsoft_azure_subscriptions	Upsert by primary key, incremental on updated-at
resource groups	microsoft_azure_resource_groups	Upsert by primary key, incremental on updated-at
resources	microsoft_azure_resources	Upsert by primary key, incremental on updated-at
usage records	microsoft_azure_usage_records	Upsert by primary key, incremental on updated-at
costs	microsoft_azure_costs	Upsert by primary key, incremental on updated-at
activity logs	microsoft_azure_activity_logs	Append-only, incremental by timestamp

Microsoft Azure API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Azure Monitor Metrics REST API (2023-10-01) + Azure Resource Graph Query API (2022-10-01) + Activity Log REST API
Authentication	OAuth 2.0, service account — Requests carry a Microsoft Entra ID (Azure AD) OAuth 2.0 bearer token scoped to `management.azure.com`, obtained via user delegation (`user_impersonation`) or an app registration/managed identity service principal; the caller needs RBAC read access (e.g. Reader or Monitoring Reader) on the target scope.
Pagination	token — Azure Resource Graph caps each query response at 1,000 rows and returns a `skipToken` to fetch the next page, with each page consuming its own query quota; Azure Monitor Metrics has no pagination at all — `top` defaults to 10 and results are instead windowed by `timespan`/`interval`.
Rate limit	Azure Resource Graph: 15 queries per rolling 5-second window per security principal by default (reported via x-ms-user-quota-remaining/x-ms-user-quota-resets-after headers, subject to change); Azure Monitor Metrics and the Activity Log share the general Azure Resource Manager throttling limits, which are hard per-subscription/per-tenant quotas rather than one published number
Incremental cursor	timespan / eventTimestamp window — Metrics and the Activity Log are pulled by advancing an ISO 8601 `timespan` or `$filter=eventTimestamp ge ...` window on each run; Resource Graph queries return a live snapshot of current resources, so detecting change means diffing successive snapshots rather than filtering a cursor field.
Webhooks	Yes — Azure Monitor Alert rules -> Action Groups (webhook, Logic App, or Event Grid) triggered off metric or Activity Log alerts
Bulk export	Yes — Activity Log diagnostic settings export to Azure Event Hubs, Storage, or a Log Analytics workspace
Deletes detectable	Yes — the Activity Log records delete operations by default (an `operationName` ending in `/delete`) but only for 90 days unless exported via a diagnostic setting; Resource Graph itself has no delete flag since it only reflects currently-existing resources

Official API reference

What bites when replicating Microsoft Azure

Azure Resource Graph allows only 15 queries per rolling 5-second window per security principal by default (`x-ms-user-quota-remaining`/`x-ms-user-quota-resets-after` headers), and each response caps at 1,000 rows, so a full-tenant pull needs both quota-aware backoff and `skipToken` pagination.
Azure Monitor's Metrics List endpoint limits a single request to 20 metric names (`metricnames`) and, when a `$filter` is used, defaults `top` to only 10 records per resource ID, silently truncating results if not raised explicitly.
The Activity Log retains events for only 90 days by default and captures write/delete control-plane operations only, never reads; anything needed longer-term must be exported via a diagnostic setting to a Log Analytics workspace, Event Hub, or Storage account before it ages out.
Activity Log REST calls have a hard 75-second server-side timeout (`Prefer: wait=75` header), and querying at the management-group level returns duplicate events for any subscription that also has its own diagnostic setting, requiring de-duplication by hashing the full record.

Compare this against every other documented API

Popular destinations for Microsoft Azure

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Microsoft Azure connector FAQ

What Microsoft Azure data does the connector extract?: 6 objects: subscriptions, resource groups, resources, usage records, costs and activity logs. Each lands in its own table with types preserved; history-style objects (1: activity logs) load as append-only streams.
Is the Microsoft Azure integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Microsoft Azure data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Microsoft Azure → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Microsoft Azure pipeline with guided onboarding

Join the waitlist to get priority access for Microsoft Azure integrations with guided setup, schema-aware mapping, and production-grade incremental sync.