Skip to content

Commit e39518e

Browse files
committed
Rephrasing and fixing errors
1 parent 86ca8ce commit e39518e

File tree

2 files changed

+20
-15
lines changed

2 files changed

+20
-15
lines changed

articles/sentinel/connect-microsoft-purview.md

Lines changed: 19 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -10,32 +10,37 @@ ms.author: lwainstein
1010

1111
# Stream data from Microsoft Purview Information Protection to Microsoft Sentinel
1212

13-
This article describes how to stream data from Microsoft Purview Information Protection (formerly Microsoft Information Protection) 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.
13+
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.
1414

1515
> [!IMPORTANT]
1616
> 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.
1717
1818
## Overview
1919

20-
Auditing and reporting are an important part of the security and compliance strategy for many organizations. 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.
20+
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.
2121

2222
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.
2323

2424
With the connector, you can:
2525

26-
- Track adoption of labels, explore, query and detects events.
27-
- Monitor labeled and protected documents and emails
26+
- Track adoption of labels, explore, query, and detect events.
27+
- Monitor labeled and protected documents and emails.
2828
- Monitor user access to labeled documents and emails, while tracking classification changes.
29-
- Gain visibility into activities performed on labels, policies, configurations, files and documents. This helps security teams to identify security breaches, and risk and compliance violations.
29+
- Gain visibility into activities performed on labels, policies, configurations, files and documents. This helps security teams identify security breaches, and risk and compliance violations.
3030
- Use the connector data during an audit, to prove that the organization is compliant.
3131

32-
### Schema and API
32+
### Azure Information Protection connector vs. Microsoft Purview Information Protection connector
3333

34-
If you're currently using the Azure Information Protection connector, note that the Azure Information Protection (AIP) service is undergoing sunsetting.
34+
This connector replaces the Azure Information Protection (AIP) data connector. Learn how to [disconnect the AIP connector](#disconnect-the-azure-information-protection-connector).
35+
36+
> [!NOTE]
37+
> The Azure Information Protection (AIP) data connector uses the AIP audit logs (public preview) feature. As of **March 18, 2022**, we are sunsetting the AIP analytics and audit logs public preview, and moving forward will be using the [Microsoft 365 auditing solution](/microsoft-365/compliance/auditing-solutions-overview). Full retirement is scheduled for **September 30, 2022**.
38+
>
39+
> For more information, see [Removed and retired services](/azure/information-protection/removed-sunset-services#azure-information-protection-analytics).
40+
>
3541
3642
When you enable the Microsoft Purview Information Protection connector, audit logs stream into the standardized
37-
`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
38-
parameters.
43+
`MicrosoftPurviewInformationProtection` table. Data is gathered through the [Office Management API](/office/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.
3944

4045
Review the list of supported [audit log record types and activities](microsoft-purview-record-types-activities.md).
4146

@@ -46,7 +51,7 @@ Before you begin, verify that you have:
4651
- The Microsoft Sentinel solution enabled.
4752
- A defined Microsoft Sentinel workspace.
4853
- A valid license to [Microsoft Purview Information Protection](/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance).
49-
- [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) and [enabled auditing](/microsoft-365/compliance/turn-audit-log-search-on-or-off?view=o365-worldwide#use-the-compliance-center-to-turn-on-auditing).
54+
- [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).
5055
- The Global Administrator or Security Administrator role on the workspace.
5156

5257
## Set up the connector
@@ -57,7 +62,9 @@ Before you begin, verify that you have:
5762
1. Below the connector description, select **Open connector page**.
5863
1. Under **Configuration**, select **Connect**.
5964

60-
When a connection is established, the **Connect** button changes to **Disconnect**. You are now connected to the Microsoft Purview Information Protection.
65+
When a connection is established, the **Connect** button changes to **Disconnect**. You are now connected to the Microsoft Purview Information Protection.
66+
67+
Review the list of supported [audit log record types and activities](microsoft-purview-record-types-activities.md).
6168

6269
## Disconnect the Azure Information Protection connector
6370

@@ -74,9 +81,7 @@ To disconnect the Azure Information Protection connector:
7481

7582
## Known Issues And Limitations
7683

77-
### Office Management API doesn't obtain a Downgrade Label
78-
79-
- 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, extracting the `labelId` of each label and enrich the results.
84+
- 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.
8085

8186
Here's an example KQL query:
8287

articles/sentinel/microsoft-purview-record-types-activities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This article lists supported audit log record types and activities when using th
1313

1414
When you use the [Microsoft Purview Information Protection connector](connect-microsoft-purview.md), you stream audit logs into the
1515
`MicrosoftPurviewInformationProtection` standardized table. Data is
16-
gathered through the [Office Management API](/office-365-management-api/office-365-management-activity-api-schema), which uses a structured schema.
16+
gathered through the [Office Management API](/office/office-365-management-api/office-365-management-activity-api-schema), which uses a structured schema.
1717

1818
## Supported audit log record types
1919

0 commit comments

Comments
 (0)