Proposed Pull Request Change

title description author ms.author ms.topic ms.date
Stream data from Microsoft Purview Information Protection to Microsoft Sentinel Stream data from Microsoft Purview Information Protection (formerly Microsoft Information Protection) to Microsoft Sentinel so you can analyze and report on data from the Microsoft Purview labeling clients and scanners. guywi-ms guywild how-to 05/31/2023
๐Ÿ“„ Document Links
GitHub View on GitHub Microsoft Learn View on Microsoft Learn
Raw New Markdown
Generating updated version of doc...
Rendered New Markdown
Generating updated version of doc...
+0 -0
+0 -0
--- title: Stream data from Microsoft Purview Information Protection to Microsoft Sentinel description: Stream data from Microsoft Purview Information Protection (formerly Microsoft Information Protection) to Microsoft Sentinel so you can analyze and report on data from the Microsoft Purview labeling clients and scanners. author: guywi-ms ms.author: guywild ms.topic: how-to ms.date: 05/31/2023 #Customer intent: As a security engineer, I want to get specific labeling data from Microsoft Purview, so analysts can track, analyze, report on the data and use it for compliance purposes. --- # Stream data from Microsoft Purview Information Protection to Microsoft Sentinel This article describes how to stream data from Microsoft Purview Information Protection (formerly Microsoft Information Protection or MIP) to Microsoft Sentinel. You can use the data ingested from the Microsoft Purview labeling clients and scanners to track, analyze, report on the data, and use it for compliance purposes. > [!IMPORTANT] > The Microsoft Purview Information Protection connector is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. ## Overview Auditing and reporting are an important part of organizations' security and compliance strategy. With the continued expansion of the technology landscape that has an ever-increasing number of systems, endpoints, operations, and regulations, it becomes even more important to have a comprehensive logging and reporting solution in place. With the Microsoft Purview Information Protection connector, you stream auditing events generated from unified labeling clients and scanners. The data is then emitted to the Microsoft 365 audit log for central reporting in Microsoft Sentinel. With the connector, you can: - Track adoption of labels, explore, query, and detect events. - Monitor labeled and protected documents and emails. - Monitor user access to labeled documents and emails, while tracking classification changes. - Gain visibility into activities performed on labels, policies, configurations, files and documents. This visibility helps security teams identify security breaches, and risk and compliance violations. - Use the connector data during an audit, to prove that the organization is compliant. ### Azure Information Protection connector vs. Microsoft Purview Information Protection connector This connector replaces the Azure Information Protection (AIP) data connector. The Azure Information Protection (AIP) data connector uses the AIP audit logs (public preview) feature. > [!IMPORTANT] > > As of **March 31, 2023**, the AIP analytics and audit logs public preview will be retired, and moving forward will be using the [Microsoft 365 auditing solution](/microsoft-365/compliance/auditing-solutions-overview). > > For more information: > - See [Removed and retired services](/azure/information-protection/removed-sunset-services#azure-information-protection-analytics). > - Learn how to [disconnect the AIP connector](#disconnect-the-azure-information-protection-connector). When you enable the Microsoft Purview Information Protection connector, audit logs stream into the standardized `MicrosoftPurviewInformationProtection` table. Data is gathered through the [Office Management API](/office/office-365-management-api/office-365-management-activity-api-schema), which uses a structured schema. The new standardized schema is adjusted to enhance the deprecated schema used by AIP, with more fields and easier access to parameters. Review the list of supported [audit log record types and activities](microsoft-purview-record-types-activities.md). ## Prerequisites Before you begin, verify that you have: - Theโ€ฏMicrosoft Sentinel solution enabled. - A defined Microsoft Sentinel workspace. - A valid license to M365 E3, M365 A3, Microsoft Business Basic or any other Audit eligible license. Read more about [auditing solutions in Microsoft Purview](/microsoft-365/compliance/audit-solutions-overview). - [Enabled Sensitivity labels for Office](/microsoft-365/compliance/sensitivity-labels-sharepoint-onedrive-files?view=o365-worldwide#use-the-microsoft-purview-compliance-portal-to-enable-support-for-sensitivity-labels&preserve-view=true) and [enabled auditing](/microsoft-365/compliance/turn-audit-log-search-on-or-off?view=o365-worldwide#use-the-compliance-center-to-turn-on-auditing&preserve-view=true). - The Security Administrator role on the tenant, or the equivalent permissions. ## Set up the connector > [!NOTE] > If you set the connector on a workspace located in a different region than your Office 365 location, data might be streamed across regions. 1. Open the [Azure portal](https://portal.azure.com/) and navigate to the **Microsoft Sentinel** service. 1. In the **Data connectors** blade, in the search bar, type *Purview*. 1. Select the **Microsoft Purview Information Protection (Preview)** connector. 1. Below the connector description, select **Open connector page**. 1. Under **Configuration**, select **Connect**. When a connection is established, the **Connect** button changes to **Disconnect**. You're now connected to the Microsoft Purview Information Protection. Review the list of supported [audit log record types and activities](microsoft-purview-record-types-activities.md). ## Disconnect the Azure Information Protection connector We recommend using the Azure Information Protection connector and the Microsoft Purview Information Protection connector simultaneously (both enabled) for a short testing period. After the testing period, we recommend that you disconnect the Azure Information Protection connector to avoid data duplication and redundant costs. To disconnect the Azure Information Protection connector: 1. In the **Data connectors** blade, in the search bar, type *Azure Information Protection*. 1. Select **Azure Information Protection**. 1. Below the connector description, select **Open connector page**. 1. Under **Configuration**, select **Connect Azure Information Protection logs**. 1. Clear the selection for the workspace from which you want to disconnect the connector, and select **OK**. ## Known issues and limitations - Sensitivity label events collected through the Office Management API do not populate the Label Names. Customers can use watchlists or enrichments defined in KQL as the example below. - The Office Management API doesn't obtain a Downgrade Label with the names of the labels before and after the downgrade. To retrieve this information, extract the `labelId` of each label and enrich the results. Here's an example KQL query: ```kusto let labelsMap = parse_json('{' '"566a334c-ea55-4a20-a1f2-cef81bfaxxxx": "MyLabel1",' '"aa1c4270-0694-4fe6-b220-8c7904b0xxxx": "MyLabel2",' '"MySensitivityLabelId": "MyLabel3"' '}'); MicrosoftPurviewInformationProtection | extend SensitivityLabelName = iff(isnotempty(SensitivityLabelId), tostring(labelsMap[tostring(SensitivityLabelId)]), "") | extend OldSensitivityLabelName = iff(isnotempty(OldSensitivityLabelId), tostring(labelsMap[tostring(OldSensitivityLabelId)]), "") ``` - The `MicrosoftPurviewInformationProtection` table and the `OfficeActivity` table might include some duplicated events. See more information on the following items used in the preceding examples, in the Kusto documentation: - [***let*** statement](/kusto/query/let-statement?view=microsoft-sentinel&preserve-view=true) - [***extend*** operator](/kusto/query/extend-operator?view=microsoft-sentinel&preserve-view=true) - [***parse_json()*** function](/kusto/query/parse-json-function?view=microsoft-sentinel&preserve-view=true) - [***iff()*** function](/kusto/query/iff-function?view=microsoft-sentinel&preserve-view=true) - [***tostring()*** function](/kusto/query/tostring-function?view=microsoft-sentinel&preserve-view=true) [!INCLUDE [kusto-reference-general-no-alert](includes/kusto-reference-general-no-alert.md)] ## Next steps In this article, you learned how to set up the Microsoft Purview Information Protection connector to track, analyze, report on the data, and use it for compliance purposes. To learn more about Microsoft Sentinel, see the following articles: - Learn how to [get visibility into your data, and potential threats](get-visibility.md). - Get started [detecting threats with Microsoft Sentinel](detect-threats-built-in.md). - [Use workbooks](monitor-your-data.md) to monitor your data.
Success! Branch created successfully. Create Pull Request on GitHub
Error: