Docs / Data sources / Microsoft Entra ID

Microsoft Entra ID

Business software

Built when you ask for it

Sync Microsoft Entra ID user, group, application, and sign-in log data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Microsoft Entra ID connector syncs your identity and access-management data into analytics-ready tables in your data warehouse. Pull users, groups, applications, and sign-in logs from the Microsoft Graph API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Users
  • Groups
  • Applications
  • Sign-in logs

How it gets built

  1. Choose Microsoft Entra ID when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Microsoft Entra ID's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Microsoft Entra ID itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

OAuth 2.0 (Microsoft identity platform). Register an app in the Microsoft Entra admin center and request delegated or application permissions such as User.Read.All.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Microsoft Entra ID connector?
Not as a finished connector yet. Ingest builds it from Microsoft Entra ID's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Microsoft Entra ID data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Microsoft Entra ID API documentation: https://learn.microsoft.com/en-us/graph/identity-network-access-overview

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Microsoft Entra ID