Microsoft Priva
Version
This integration utilizes the Microsoft Priva API v1.
Base URL
The base URL used for all Microsoft Priva API endpoints:https://graph.microsoft.com/v1
Authentication & Authorization
The DataGrail Microsoft Priva integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.
Scopes
The Microsoft Priva integration requires specific scopes that must be granted in order to function for a given capability.
| Scope | Base | Access |
|---|---|---|
offline_access | ✅ | |
email | ✅ | |
openid | ✅ | |
profile | ✅ | |
SubjectRightsRequest.ReadWrite.All | ✅ | |
User.Read | ✅ |
Endpoints Utilized
DataGrail uses the following endpoints to authorize and test the connection:
Limits
Limits in Microsoft Priva 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
Access
DataGrail's Microsoft Priva integration provides Asynchronous Access capabilities for the following supported identifier category: Email.Data Interactions
For Access requests, DataGrail will take the following actions:
- Create a new subject rights request.
- Continuously fetch the status of a subject rights request until complete.
- Extract the final report for a subject rights request.
Endpoints Utilized
Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.