Skip to content
Security and identity ⇄ Data warehouse

Azure Active Directory to Tinybird integration — real-time, two-way sync

Keep Azure Active Directory and Tinybird in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Azure Active Directory and Tinybird

Land the users, groups, and access events from Azure Active Directory in Tinybird continuously for security analytics, and write computed results back — without building or maintaining a pipeline.

Azure Active Directory is the record of who exists and what they can reach; Tinybird is where the business measures everything else. The two overlap on people and their access — the same users, groups, roles, and events that Azure Active Directory governs are what security, compliance, and analytics teams want to query in Tinybird. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs Service principals, Directory roles, Devices, Users from Azure Active Directory into tables in Tinybird in real time, and the connection works in both directions: values computed in Tinybird, such as risk scores or access-review decisions, can be written back to attributes in Azure Active Directory where the identity team acts on them. Schema changes are handled, API limits are managed, and the sync is something you configure rather than a pipeline you keep alive.

Common use cases

  • 01 Stream CRM activity such as deals and tickets into Tinybird Data Sources to power customer-facing dashboards.
  • 02 Sync order events from an ERP into Tinybird to serve low-latency operational analytics endpoints.
  • 03 Sync manager, department, and jobTitle from an HRIS back onto Entra ID User attributes to keep dynamic groups and Conditional Access accurate.
  • 04 Replicate Groups and their Members into a Postgres warehouse for access reviews and entitlement reporting.

Common sync patterns

Access and sign-in analytics

Sign-in and access events from Azure Active Directory land in Tinybird, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.

Access governance on joined data

Join Azure Active Directory's users and group memberships with HR, product, and usage data already in Tinybird to surface who holds access they no longer need.

Queryable history for audit and compliance

A continuously synced copy in Tinybird gives you a durable, queryable record of identity and access state for access reviews, SOC 2, and audit questions.

What you can sync between Azure Active Directory and Tinybird

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Azure Active Directory objects Tinybird objects How this pairing syncs
Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. Tokens Scoped credentials that control read and append rights per resource. Devices is specific to Azure Active Directory and Tokens to Tinybird — each maps to any object or custom field on the other side.
Users /users in Microsoft Graph; synced two-way — profile attributes, accountEnabled, and assignedLicenses are read out while provisioning writes (create, update, disable, delete) are pushed back. Data Sources ClickHouse-backed tables that receive ingested rows; the write target for syncs into Tinybird. Users is specific to Azure Active Directory and Data Sources to Tinybird — each maps to any object or custom field on the other side.
Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. Pipes Chained SQL nodes that transform Data Sources into query-ready results. Groups is specific to Azure Active Directory and Pipes to Tinybird — each maps to any object or custom field on the other side.
Group memberships Member and owner relationships on /groups/{id}/members; added and removed via the $ref endpoint and tracked for changes with delta query on $select=members. API Endpoints Published Pipe outputs exposed as parameterized HTTP queries; the main read surface. Group memberships is specific to Azure Active Directory and API Endpoints to Tinybird — each maps to any object or custom field on the other side.
Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. Materialized Views Pipes materialized into new Data Sources for pre-aggregation at ingest time. Applications is specific to Azure Active Directory and Materialized Views to Tinybird — each maps to any object or custom field on the other side.
Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. Workspaces Project boundary that scopes Data Sources, Pipes, and tokens for a sync. Service principals is specific to Azure Active Directory and Workspaces to Tinybird — each maps to any object or custom field on the other side.

How changes propagate between Azure Active Directory and Tinybird

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Azure Active Directory Tinybird Sub-second propagation

DetectionAzure Active Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification.

DeliveryEach detected change is applied to Tinybird as a row-level write, with types converted between the two schemas.

Tinybird Azure Active Directory Interval-based propagation

DetectionStacksync polls Tinybird for changes on an incremental schedule, reading only records changed since the previous pass. Append-oriented ingestion.

DeliveryEach detected change is written to Azure Active Directory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Azure Active Directory: Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header.
  • Tinybird: Subject to the platform's ingestion and query rate limits; batch appends where possible.
What ships with Azure Active Directory ⇄ Tinybird

Connect Azure Active Directory and Tinybird for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Tinybird connection.

Real-time

Two-way sync

Changes in Azure Active Directory or Tinybird instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Active Directory or Tinybird data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Azure Active Directory or Tinybird record.

Observability

Monitoring

Track your Azure Active Directory ⇄ Tinybird sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Active Directory and Tinybird.

How the Azure Active Directory and Tinybird connectors work

Azure Active Directory

Integration surface
Microsoft Graph REST API (v1.0)
Authentication
OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent
Change detection
Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push
Capabilities
read · write · webhooks
Rate limits
Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header

Tinybird

Integration surface
REST API (Events API for ingestion, published query endpoints) with a ClickHouse SQL dialect
Authentication
Scoped auth tokens
Change detection
Append-oriented ingestion; reads are pulled by querying published endpoints, no outbound CDC
Capabilities
read · write
Rate limits
Subject to the platform's ingestion and query rate limits; batch appends where possible.
How it works

How to connect Azure Active Directory to Tinybird — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Azure Active Directory and Tinybird with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Active Directory connected
    Tinybird connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Active Directory and Tinybird objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Active Directory ⇄ Tinybird
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure Active Directory Tinybird
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Active Directory and Tinybird integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 429 integrations available for Azure Active Directory and Tinybird.

Popular · 8 of 429
All Azure Active Directory integrations All Tinybird integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own