Skip to content

Commit c3b83c0

Browse files
author
cabailey
committed
fix typos
1 parent 59f3923 commit c3b83c0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sentinel/connect-azure-information-protection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ However, if logging information from Azure Information Protection is going to a
3434

3535
- Change the workspace for Azure Information Protection, which you can do by configuring this data connector.
3636

37-
If you change the workspace, new reporting data for Azure Information Protection will now be stored in the workspace you're using for Azure Sentinel, and historical data isn't available to Azure Sentinel. In addition, if the previous workspace is configured for custome queries, alerts, or REST APIs, these must be reconfigured for the Azure Sentinel workspace if you want to carry on using them for Azure Inforamtion Protection. No reconfiguration is needed for clients and services that use Azure Information Protection.
37+
If you change the workspace, new reporting data for Azure Information Protection will now be stored in the workspace you're using for Azure Sentinel, and historical data isn't available to Azure Sentinel. In addition, if the previous workspace is configured for custom queries, alerts, or REST APIs, these must be reconfigured for the Azure Sentinel workspace if you want to carry on using them for Azure Information Protection. No reconfiguration is needed for clients and services that use Azure Information Protection.
3838

3939
## Prerequisites
4040

0 commit comments

Comments
 (0)