Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Microsoft Entra ID from the Previews page. See Manage Azure Databricks previews.
This page answers frequently asked questions about the managed Microsoft Entra ID ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Microsoft Entra ID plans does the connector require?
The signins table and the signInActivity column of users require a Microsoft Entra ID P1 or P2 license. The role_eligibility_schedule table reads Privileged Identity Management data, which requires licenses. See Prerequisites.
Which tables does the connector support?
The connector supports directory tables (users, groups, group_members, group_owner, applications, and serviceprincipals). It also supports role tables (directoryroles, directory_role_member, directoryroletemplates, and role_eligibility_schedule), log tables (directoryaudits and signins), and configuration tables (user_registration_detail, identityproviders, and adminconsentrequestpolicy). See Destination table schemas.
How far back can the connector ingest data?
For directoryaudits and signins, the first sync ingests events from the previous 30 days, or from start_datetime if you set it. Each later sync ingests events after the last run. Full-refresh tables reingest all available records on every run.
Which authentication methods does the connector support?
The connector supports OAuth machine-to-machine (M2M) authentication with a Microsoft Entra ID app registration and client secret. It does not support OAuth U2M or basic authentication.
Does the connector support national clouds?
Yes. Set Microsoft Cloud Region on the connection to commercial, us_gov_gcc_high, us_gov_dod, or china_21vianet. See Create a Microsoft Entra ID connection.