Microsoft Purview Cancels Azure SQL and Storage Auto-Labeling Plan

Purview roadmap item 429876 no longer supplies a release plan​

The proposed change would have extended sensitivity-label auto-labeling policies to specific or all subscriptions within Azure Storage and Azure SQL Server. Its description also promised a way to define conditions for data sources beyond Microsoft 365 without interfering with existing Microsoft 365 file configurations. For an administrator maintaining both sets of policies, that separation was part of the proposed feature—not a detail to assume is available today.

Item 429876 listed July 2024 for preview and April 2026 for general availability in the worldwide commercial cloud. Those were roadmap estimates, not proof of a rollout. Microsoft’s September 24 update withdraws the plan for now and says it will communicate through a new roadmap item if it chooses to proceed. It gives no replacement date.

The schedule had already become uncertain. An archived Microsoft 365 Message Center notice associated with item 429876 said general availability was paused and that Microsoft would announce its timing when ready. That earlier notice provides context for the change in plans; it does not turn the cancelled roadmap entry into evidence that the proposed subscription-level experience shipped.

Purview Data Map labeling remains a separate preview capability​

Cancellation of item 429876 does not mean organizations have lost every way to label Azure data in Purview. Microsoft Learn describes sensitivity labeling in Microsoft Purview Data Map, currently in preview, for files in supported storage services such as Azure Data Lake and Azure Files, and for table columns in Azure SQL Database. It also describes auto-labeling policies that act on classifications found when registered assets are scanned.

That workflow has a different, documented unit of operation. Administrators register assets in Data Map, scan them, and select supported non-Microsoft 365 locations or assets for a policy. On a subsequent scan, Data Map evaluates the policy’s conditions and applies a label to matching catalog assets. The cancelled item described a planned subscription-scoping expansion; the existence of asset-based Data Map policies does not establish that the promised experience arrived.

The word label also needs care here. Microsoft says that when an already-labeled Office file is scanned into Data Map, its label appears on the catalog asset as metadata; the label on the actual file is a separate application of that label. A label visible in the map should therefore not be treated, by itself, as confirmation that Purview changed the underlying file or database object.

SQL administrators face another boundary. Purview uses global sensitivity labels, while SQL Server Management Studio’s SQL data classification uses locally defined labels. Microsoft says the two processes do not currently exchange labels: a classification applied in SSMS will not appear as a Purview sensitivity label, or vice versa. A governance inventory that combines their results needs to account for both systems.

A Data Map policy requires registered assets, scans, and preview billing​

Teams that need Azure-data labeling now can assess the documented Data Map workflow on its own terms. Microsoft’s setup instructions say it requires an active Microsoft 365 license that includes automatic sensitivity labeling and a pay-as-you-go billing setup. Labels must have the Files & other data assets scope; an existing label can be edited to add it. Data Map labeling remains a preview capability, so those prerequisites should be checked before treating it as a replacement for a planned production rollout.

The supported sequence is specific:

1. In the Microsoft Purview portal, open Information Protection > Sensitivity labels and create a label with the Files & other data assets scope, or edit an existing label to add that scope.
2. Register the intended data source in Data Map and scan it so its assets and detected classifications are available.
3. Open Information Protection > Policies > Auto-labeling policies, create a policy, and select a label with the required scope.
4. Select the supported non-Microsoft 365 locations or assets to cover. A location’s availability for selection depends on assets already registered in Data Map.
5. Define rules using Microsoft’s supported prebuilt classifiers, create the policy, allow 15 minutes for it to propagate, and scan the assets again. Applied labels can then be inspected on assets in the Purview Unified Catalog.

Two limitations affect policy design before the first scan. Microsoft’s Data Map instructions exclude custom sensitive information types and advanced classifiers including trainable classifiers, credentials, and Exact Data Match from this auto-labeling workflow. The instructions also display a simulation choice during policy creation but explicitly say Data Map locations do not support simulation. Administrators should plan their initial scope accordingly instead of relying on a simulation result for these assets.

What this means for you​

Remove item 429876’s old dates from delivery plans, then evaluate the preview Data Map workflow only against the assets and controls your organization actually needs. The roadmap description does not specify enough about its intended storage resource types, SQL variants, policy conditions, permissions, or licensing to claim that Data Map is a one-for-one substitute.

• Treat September 24, 2026, as the cancellation date for the planned policy expansion, not as a withdrawal notice for all Azure-data labeling.
• Do not use the item’s July 2024 preview or April 2026 general-availability estimates as evidence that your tenant received the proposed feature.
• If Data Map labeling is an option, confirm the supported asset type, eligible license, pay-as-you-go setup, and Files & other data assets label scope before creating a policy.
• Register and scan assets before expecting them to appear as policy locations; allow for policy propagation and a further scan before checking for labels in the catalog.
• Keep Purview catalog labels distinct from labels on underlying content and from SQL Server Management Studio classifications.

For now, administrators have a cancelled subscription-level roadmap plan and a separately documented, scan-based Data Map preview to assess. If Microsoft revisits the proposed expansion, it says the decision will arrive as a new roadmap item; until then, production plans should rest on the behavior available and verified in each tenant, not on item 429876’s retired dates.