Microsoft Purview and Microsoft Priva extensibility

Microsoft Purview solutions help organizations intelligently assess their compliance risks, govern and protect sensitive data, and effectively respond to regulatory requirements. Microsoft Purview is rich in extensibility scenarios and enables organizations to adapt, extend, integrate, accelerate, and support their compliance solutions.

There are two key building blocks for compliance extensibility:

  • Data connectors. Use to import and archive non-Microsoft data so you can apply Microsoft 365 protection and governance capabilities to third-party data.

  • APIs. Enables programmatic access to Microsoft Purview capabilities.

Tip

If you're not an E5 customer, you can try all the premium features in Microsoft Purview for free. Use the 90-day Purview solutions trial to explore how robust Purview capabilities can help your organization manage data security and compliance needs. Start now at the Microsoft Purview compliance portal trials hub. Learn details about signing up and trial terms.

Data connectors

Microsoft provides third-party data connectors that can be configured in the Microsoft Purview compliance portal. For a list of data connectors provided by Microsoft, see the Third-party data connectors table. The table of third-party data connectors also summarizes the compliance solutions that you can apply to third-party data after you import and archive data in Microsoft 365, and links to the step-by-step instructions for each connector.

To learn more about Microsoft Purview Data Connectors, see Archiving third-party data. If a third-party data type isn't supported by the data connectors available in the compliance portal, you can work with a partner who can provide you with a custom connector. For a list of partners you can work with and the step-by-step process for this method, see Work with a partner to archive third-party data.

Prerequisites for data connectors

Many of the data connectors available in the compliance portal to import and archive third-party data require that you prepare and perform configuration tasks in the third-party data source. These prerequisites are documented in detail for each third-party data connector.

For data connectors in the compliance portal provided by one of Microsoft's partners, your organization will need a business relationship with the partner before you can deploy a connector.

For guidance and requirements for third-party data connectors, see the "Data connectors" section in Microsoft 365 guidance for security & compliance - Service Descriptions | Microsoft Docs.

APIs

Microsoft Purview and Microsoft Priva APIs are available in the Microsoft Information Protection SDK, Microsoft Graph API, and the Office 365 Management Activity API. Some compliance APIs are part of a new set of security and compliance APIs that enable developers for Microsoft 365 customers, independent software vendors, system integrators, and managed security service providers to build high-value security and compliance solutions.

To learn more about how to access Graph APIs, see Overview of Microsoft Graph.

Microsoft Graph APIs for subject rights requests

In accordance with certain privacy regulations around the world, individuals can make requests to review or manage the personal data about themselves that companies have collected. These requests are referred to as subject rights requests within the Microsoft Priva Subject Rights Requests solution. Subject rights requests are also referred to as data subject requests (DSRs) or data subject access requests (DSARs). Microsoft Graph APIs for subject rights requests enable developers to integrate Microsoft 365-related subject rights requests with the broader privacy ecosystem. This API-based extensibility enables organizations to respond to subject rights requests in a unified manner across their entire data estate covering both Microsoft and non-Microsoft environments. This capability also helps with automation at scale and helps organizations meet industry regulations more efficiently without relying on manual processes.

To learn more, see Microsoft Graph APIs for subject rights request.

Microsoft Information Protection (MIP) SDK

The MIP SDK exposes the labeling and protection services from Microsoft 365 security and compliance centers to third-party applications and services. Developers can use the SDK to build native support for applying labels and protection to files. Developers can determine which actions should be taken when specific labels are detected, and reason over MIP-encrypted information.

High-level MIP SDK use cases include:

  • A line-of-business application that applies classification labels to files on export.

  • A CAD/CAM design application that provides native support for sensitivity labels.

  • A cloud access security broker or data loss prevention solution that can encrypt data with Azure Information Protection.

To learn more about the MIP SDK, prerequisites, additional scenarios, and samples, see MIP SDK Overview.

Microsoft Graph API for Teams DLP

Data loss prevention (DLP) capabilities are widely used in Microsoft Teams particularly as organizations have shifted to remote work. Recently we announced the general availability of the Microsoft Graph Change Notification API for messages in Teams. This API enables developers to build apps that can listen to Microsoft Teams messages in near-real time and then implement DLP scenarios for both customers and partners. Additionally, Microsoft Graph Patch API lets you apply DLP actions to Teams messages.

These two APIs form the Microsoft Graph API for Teams DLP. You can get started by trying out the sample app. For more information about Microsoft Teams messaging webhooks, see the documentation.

For the licensing requirements for Teams DLP, see Microsoft 365 licensing guidance for security & compliance.

Microsoft Graph API for eDiscovery (preview)

With eDiscovery (Premium), organizations can discover data where it lives, and manage more end-to-end eDiscovery workflows with intelligent machine learning and analytics capabilities to reduce data to the relevant set – all while the data stays within the Microsoft 365 security and compliance boundary.

Graph APIs for eDiscovery (Premium) can be used to create and manage cases, review sets, and review set queries in a scalable and repeatable manner. This enables customers and partners to create apps and workflows to automate common and repetitive processes such as creating cases and managing custodians and legal holds.

The first set of Graph APIs for eDiscovery are available in public preview. We plan to add more capabilities by the end of the calendar year. To learn more about these APIs and other updates for eDiscovery (Premium), see this blog.

For the licensing requirements for eDiscovery (Premium) and the API, see the "eDiscovery" section in the Microsoft 365 licensing guidance for security & compliance.

Microsoft Graph API for Teams Export

Enterprise Information Archiving (EIA) for Microsoft Teams is a key scenario for our customers as it allows them to solve for regulatory requirements. In addition to our built-in capabilities for archiving content in Microsoft Teams, customers and partners can now use Teams Export APIs to solve for custom application and integration scenarios. The Teams Export APIs support bulk-export (up to 200 requests per second/per app/per tenant) of Teams messages and message attachments. Deleted messages are also accessible by the API for up to 30 days after they are deleted. For more information about these Teams Export APIs and how to use them in your applications, see Export content with the Microsoft Teams Export APIs.

For the licensing requirements for the use of the Teams Export APIs, see Microsoft 365 licensing guidance for security & compliance.

Microsoft Graph Connector APIs (preview)

With Microsoft Graph connectors, organizations can index third-party data so it appears in Microsoft Search results. This feature expands the types of content sources that are searchable in your Microsoft 365 productivity apps and the broader Microsoft ecosystem. The third-party data can be hosted on-premises or in public or private clouds. Starting with eDiscovery (Premium), we're enabling developer preview of built-in compliance value of Microsoft 365 connected apps. This enables compliance for apps integrating into the Microsoft 365 ecosystem to empower users with seamless compliance experiences. To learn more about to how to incorporate Microsoft Graph Connector APIs in your apps view, see Create, update, and delete connections in the Microsoft Graph.

Microsoft Graph API for records management (preview)

Organizations of all types require a records management solution to manage critical records across their data. Microsoft Purview Records Management helps an organization manage their legal obligations, provides the ability to demonstrate compliance with regulations, and increases efficiency with regular disposition of items that are no longer required.

The records management solution is used by organizations in large volumes to utilize its various capabilities in protecting, labeling, retaining, or deleting their data. The Microsoft Graph APIs for records management lets organizations manage retention labels and their associated actions more efficiently, automate repetitive tasks, and equip customers with flexibility in options.

Now rolling out, the first release of Graph APIs for records management support the management of retention labels, and event-based retention. Example scenarios:

  • Managing retention labels

    Record management admins and developers need to maintain their record management systems with labels that are periodically created, updated, and deleted.

    Developers and compliance admins use the Graph APIs for records management to perform CRUD operations on the label entity to maintain their systems.

  • Triggering an event for an existing label

    When an employee leaves an organization, the information is updated in the HR management system. From the date of leaving, confidential documents need to be retained for seven years. These documents already have the retention label "Employee_departure" applied to them.

    Developers and compliance admins use the Graph APIs for records management to read the label “Employee_departure” and look up the associated event type "Event-employee_departure".

    They then use the Graph APIs for records management to create an event for the associated event type. The retention period for the confidential documents starts after this event is created.

For more information about the Graph APIs for records management, see Use the Microsoft Graph Records Management API.

For licensing requirements to use these APIs, see the records management information from the Microsoft 365 guidance for security & compliance, Microsoft Purview Data Lifecycle Management & Microsoft Purview Records Management section.