We're pleased to announce General Availability of the Microsoft Information Protection SDK!
Back in April, we revealed the Microsoft Information Protection SDK public preview. Today, we’re happy to announce that the SDK is now generally available and ready for you to build into your own applications!
Microsoft Information Protection
At Ignite 2017, we announced our plans to bring together the management of Azure Information Protection, Office Information Protection, and Windows Information Protection. Microsoft Information Protection is the result of our work to unify the management experience across all these services in Office 365 Security and Compliance Center.
The Microsoft Information Protection SDK brings the classification, labeling, and protection capabilities of Microsoft Information Protection into a simple, lightweight, cross-platform software development kit that enables any application to label and protect information. The labels and protection are consumable by Azure Information Protection, Office apps, Office 365, and any application or service that has integrated the Microsoft Information Protection SDK.
Bringing the labeling and protection capabilities that have existed in Office to line of business applications, as well as third-party PDF viewers, CAD/CAM applications, and other SaaS applications is a critical component of the information protection story. The Microsoft Information Protection SDK enables Microsoft partners and customers to build those integrations to protect data at creation, detect movement across trust boundaries, and to prevent accidental or malicious leakage of sensitive information.
The GA release is supported on the following platforms.
Any supported version of Windows Server and client
MacOS High Sierra and Later
RedHat Enterprise Linux 7
iOS (Public Preview)
Android (Public Preview)
The SDK also requires the use of a C++11 compliant compiler.
The files for each platform and API are named as follows:
mip_sdk_API_OS_1.0.41.zip (or .tar.gz)
For example, the protection API binaries and headers on Debian look like:
Each ZIP or tarball contains three directories:
Bins: The compiled binaries for each platform architecture, where applicable.
Include: The Microsoft Information Protection SDK header files
Samples: Source code for the sample applications
We've published a few sample applications on GitHub to help get you started with the SDK. These first few samples provide examples of authentication and simple examples of the File, Policy, and Protection APIs. We'll continue to add to the set of available samples in the months following GA.