Microsoft Entra ID

This documentation for the Microsoft Entra ID integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Microsoft Entra ID, visit our connection instructions.

Version

This integration utilizes the Microsoft Entra ID REST API v1.0.

Base URL

The base URL used for all Microsoft Entra ID API endpoints:

https://graph.microsoft.com/v1.0

Authentication & Authorization

The DataGrail Microsoft Entra ID integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to Microsoft Entra ID API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Scopes

The Microsoft Entra ID integration requires specific scopes that must be granted in order to function for a given capability.

Scope	Base	System Detection
offline_access	✅
Application.Read.All		✅
User.Read.All		✅

Base Scopes

All base scopes must be granted in order to connect the integration with DataGrail. The remaining scopes are only required if enabling those capabilities

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	https:​//login.microsoftonline.com/common/oauth2/v2.0/authorize	Request authorization
POST	https:​//login.microsoftonline.com/common/oauth2/v2.0/token	Get and refresh access token

---

Limits

Limits in Microsoft Entra ID are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

System Detection

DataGrail provides continuous system detection, delivering a real-time inventory of your data assets.

Data Interactions

DataGrail's System Detection process runs once daily and performs the following actions:

1. Retrieve a list of servicePrincipal objects to build a list of detected systems (applications).
2. List appRoleAssignments granted to each detected servicePrincipal (application) to define their owners (by application ID).
3. Retrieve properties of the users to define application owners emails (by user ID).

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/servicePrincipals	Retrieve a list of service principals.
GET	/servicePrincipals/APP_ID/appRoleAssignedTo	Retrieve the list of appRoleAssignments that have been granted to a service principal.
GET	/users/USER_ID	Retrieve the properties and relationships of a user object

---