![]() Performing these changes caused the creation of a new label management tab, in addition to a new client support (via add-in and built-in Office 365 apps) that is based on the Microsoft Information Protection SDK. Referring to Azure Information Protection labels in a consistent and short name which will also differentiate from Retention labels that are already exist in Office 365 platform – Sensitivity labels.A unified backend in the Office 365 eco-system to manage the Azure Information Protection labels – the Office 365 Security & Compliance Center ( same label admin capabilities are also available at Microsoft 365 Security and Microsoft 365 Compliance portals).Microsoft introduce d a unified SDK to be implemented by all applications and services that want to use Azure Information Protection classification and labeling – the Microsoft Information Protection SDK.Because the Office 365 s uite of products were managed from the Office management portals and the plan included a big initiative to integrate Azure Information Protection labeling capabilities into Office 365 and many other Microsoft and 3 rd party products, a unified approach has been agreed upon and initiated these changes: At that point, Azure Information Protection was the only product that supported labeling of sensitive content as part of Microsoft portfolio.īased on customer feedback and the evolution of Office 365, a strategic decision was made to integrate Azure Information Protection labeling capabilities into Office 365 services. The Azure Information Protection blade in the Azure portal replaced the old Azure Rights Management interface which was available only in the Azure classic portal. Note: Unified labeling support is only available for commercial cloud tenants.īack in 2016 when the Azure Information Protection client was initially released, it was the first Microsoft product that introduced labeling capabilities which was applied on top of the already available Azure Rights Management service. If you want to understand why this is necessary and why the migration plan is not as complicated as it initially sound, please continue to review the information contained in this blog. Both can be deployed as a new installation or in-place upgrade to the Azure Information Protection client (classic). The primary migration plan is to migrate labels and policies from the Azure Information Protection blade in the Azure portal to the Office 365 Security & Compliance Center, re-create your label conditions and deploy a Unified Labeling supported client, via an add-in or built-in Office 365 apps. Because of this, now is the time to execute a migration to this service as there is zero risk when done properly following our recommended steps. Each new Microsoft product and service that utilizes classification and protection capabilities (and 3 rd party ones using MIP SDK capabilities) will require unified labeling. Unified labeling is here and it is the next step in the Microsoft Information Protection story. This blog is updated for June 2020 and includes the latest Microsoft Information Protection capabilities that are now available. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |