Microsoft Purview | Information Protection: Auto-labeling for Microsoft Azure Storage and Azure SQL
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
- Roadmap
- 429876
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw- Seen 5 Dec 2025
late November 2025, late December 2025 - Seen 3 Jul 2025
mid-November 2024, late November 2024, mid-July 2025→ early July 2025, late July 2025, late November 2025, late December 2025 - Seen 6 Feb 2025
late March 2025, mid-April 2025→ mid-July 2025
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, safely structuredUpdated September 24, 2026: We have decided not to move forward with this change at this time and will communicate via Message center when we choose to proceed. We apologize for any inconvenience.
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 have decided not to move forward with this change at this time.
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.
What changed
Between archive captures, newest firstUpdated
December 5, 2025:September 24, 2026: We havepaused GA release fordecided not to move forward with this change at thisfeature. Thank youtime and will communicate via Message center when we choose to proceed. We apologize foryour patience.any inconvenience. Extend your sensitivity labels to specific or all subscriptions within Azure Storage, … and expect to complete by late July 2025. General Availability (Worldwide): Wewill announce via Message center when we are ready to proceed.have decided not to move forward with this change at this time. How this will affect your organization: You can create new auto-labeling policies … to extend labeling to assets in the Microsoft Purview Data Map (optin) Instead,in)Instead, you can select where to extend these assets in an auto-labeling policy Schematized data assets as an applicable labelscope YouscopeYou 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 labeldefinition IfdefinitionIf you have configured Auto-labeling for schematized data assets in the label definition, … associated with the label. You will be able to select non-m365 workloadsin the auto-labeling policy: What you need to do to prepare: This …Only details this page does not show changed.
Only details this page does not show changed.
Only details this page does not show changed.
Updated
July 3,December 5, 2025: We haveupdated the timeline below.paused GA release for this feature. Thank you for your patience. Extend your sensitivity labels to specific or … expect to complete by late July 2025. General Availability (Worldwide): We willbegin rolling out late November 2025 and expectannounce via Message center when we are ready tocomplete by late December 2025.proceed. How this will affect your organization: You can create new auto-labeling policies …Only details this page does not show changed.
Updated
February 6,July 3, 2025: We have updated therollouttimeline below. Thank you for your patience.Coming soon for Microsoft Purview | Information Protection: Automatically label all or some assets in MicrosoftExtend 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, AzureStorage and MicrosoftDatabricks Unity Catalog, Azure SQLwith an auto-labeling policy. You will be able to clearlyManaged Instance, Azure Synapse Analytics, Snowflake, Dataverse, and SQL Server via auto-labeling policy. Clearly define labeling conditions for data sourcesin Azure separately frombeyond M365 without fear of it interfering with existingMicrosoft 365M365 files configurations.This message is associated with Microsoft 365 Roadmap ID 429876. When this will happen: Public Preview: We will begin rolling outmid-November 2024early July 2025 and expect to complete by lateNovember 2024.July 2025. General Availability (Worldwide): We will begin rolling out lateJune (previously late March)November 2025 and expect to complete bymid-July 2025 (previously mid-April).late December 2025. How this will affect your organization: You can create new auto-labeling policies forAzure Storage and Azure SQLnon-m365 workloads Server that allow you to specify specific data assets or ALL assets … control settings associated with the label. You will be able to selectAzureStorage and AzureSQLServernon-m365 workloadsin the auto-labeling policy: What you need to do to prepare: This … 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- Tags
New feature, Admin impact→ Updated message, New feature, Admin impact
Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Information Protection: Automatically label all or … late November 2024. General Availability (Worldwide): We will begin rolling out late
March 2025June (previously late March) and expect to complete bymid-April 2025.mid-July 2025 (previously mid-April). How this will affect your organization: You can create new auto-labeling policies …- Tags
- · first version seen
Learn more
Links from the notice and their documentation checksRelated public changes
No related announcements were found in the saved public history. Check the source for newer announcements.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- 3 linked pages have not been read yet.