MC790716 - Microsoft Purview | Information Protection - Sensitivity label protection policy for Azure SQL, Storage, and Amazon S3
Service
Last Updated
Published May 6, 2024
Tag
Platforms
Summary
After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience. Microsoft Purview's Information Protection introduces a new feature, Protection Policy, for label-based protection on Azure SQL, Data Lake Gen 2, Blob Storage, and Amazon S3. General availability starts late June 2025 with a public preview phase free of cost, followed by pay-as-you-go pricing. Prepare by creating a policy in the Purview Portal. Roadmap ID: 394282.
More information
Updated January 29, 2025: We have updated the rollout timeline below. Thank you for your patience.
In Microsoft Purview, Information Protection will introduce a new feature called Protection Policy to create new protection policies for label-based protection. This enhanced protection can be applied to the following services:
- Azure SQL: Databases hosted on Microsoft’s cloud platform.
- Azure Data Lake Gen 2: Large-scale data storage and analytics service.
- Azure Blob Storage: A service for storing large amounts of unstructured data.
- Amazon S3: Amazon’s cloud storage service.
This message is associated with Microsoft 365 Roadmap ID 394282
When this will happen:
General Availability (Worldwide): We will begin rolling out late June 2025 and expect to complete by late June 2025.
How this will affect your organization:
During the public preview phase, you can use these label-based protections without any extra cost. However, once this period ends, a pay-as-you-go pricing model will be implemented for continued use of these features.
To create your initial protection policy, go to the Microsoft Purview Portal and navigate to the Information Protection application.
This image shows a protection policy created for data sources within Azure:
What you need to do to prepare:
Visit the Information Protection app in Microsoft Purview Portal and try to create your first protection policy. Learn more here:
- Authoring and publishing protection policies (preview) | Microsoft Learn) - https://learn.microsoft.com/en-us/purview/how-to-create-protection-policy