MC933531 - Microsoft Purview | Information Protection: Auto-labeling for Microsoft Azure Storage and Azure SQL

Updated December 5, 2025: We have paused GA release for this feature. Thank you for your patience.

Extend your sensitivity labels to specific or all subscriptions within Azure Storage, Azure SQL, Azure Cosmos DB, Azure Data Explorer, Azure Database for MySQL, Azure Database for PostgreSQL, Azure Databricks Unity Catalog, Azure SQL Managed Instance, Azure Synapse Analytics, Snowflake, Dataverse, and SQL Server via auto-labeling policy. Clearly define labeling conditions for data sources beyond M365 without fear of it interfering with existing M365 files configurations. 

This message is associated with Microsoft 365 Roadmap ID 429876.

When this will happen:

Public Preview: We will begin rolling out early July 2025 and expect to complete by late July 2025.

General Availability (Worldwide): We will announce via Message center when we are ready to proceed. 

How this will affect your organization:

You can create new auto-labeling policies for non-m365 workloads Server that allow you to specify specific data assets or ALL assets to be automatically labeled when the out-of-the-box sensitive information types are detected in a column or asset. After the auto-labeling policy is turned on, wait 15 minutes, and then rescan the scoped data assets. The assets will be labeled automatically.

This change will be available by default for admins to configure.

After the rollout, these capabilities will no longer be available:

• The ability to extend labeling to assets in the Microsoft Purview Data Map (opt in)
  • Instead, you can select where to extend these assets in an auto-labeling policy
• Schematized data assets as an applicable label scope
  • You can select any label with the scope Files & other data assets for labeling in non-Microsoft 365 workloads
• Auto-labeling for schematized data assets in label definition
  • If you have configured Auto-labeling for schematized data assets in the label definition, you will need to reconfigure those conditions in an auto-labeling policy.

Tip: After you apply labeling to data assets, you can use protection policies to add access control settings associated with the label.

You will be able to select non-m365 workloads in the auto-labeling policy:

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

• Sensitivity Labels in the Microsoft Purview Data Map FAQ
• Learn about Microsoft Purview billing models | Microsoft Learn
• Data sources that connect to Microsoft Purview Data Map | Microsoft Learn