Skip to content

Commit 339afcd

Browse files
authored
Merge pull request #174493 from austinmccollum/master
remove MIP from sensitivity labels
2 parents 2523e5b + 15267a6 commit 339afcd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/purview/create-sensitivity-label.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Sensitivity labels are supported in Azure Purview for the following data sources
5858

5959
## Labeling for SQL databases
6060

61-
In addition to Purview labeling for database columns, Microsoft also supports labeling for SQL database columns using the SQL data classification in [SQL Server Management Studio (SSMS)](/sql/ssms/sql-server-management-studio-ssms). While Purview uses the global [MIP sensitivity labels](/microsoft-365/compliance/sensitivity-labels), SSMS only uses labels defined locally.
61+
In addition to Purview labeling for database columns, Microsoft also supports labeling for SQL database columns using the SQL data classification in [SQL Server Management Studio (SSMS)](/sql/ssms/sql-server-management-studio-ssms). While Purview uses the global [sensitivity labels](/microsoft-365/compliance/sensitivity-labels), SSMS only uses labels defined locally.
6262

6363
Labeling in Purview and labeling in SSMS are separate processes that do not currently interact with each other. Therefore, **labels applied in SSMS are not shown in Purview, and vice versa**. We recommend Azure Purview for labeling SQL databases, as it uses global MIP labels that can be applied across multiple platforms.
6464

0 commit comments

Comments
 (0)