%3CLINGO-SUB%20id%3D%22lingo-sub-242022%22%20slang%3D%22en-US%22%3EMIP%20SDK%20Public%20Preview%20September%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-242022%22%20slang%3D%22en-US%22%3E%3CH1%20id%3D%22mip-sdk-private-preview-update%22%20id%3D%22toc-hId-1905867301%22%20id%3D%22toc-hId-1928862824%22%3EMIP%20SDK%20Private%20Preview%20Update%3C%2FH1%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22summary%22%20id%3D%22toc-hId--842803165%22%20id%3D%22toc-hId--819807642%22%3ESummary%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUpdating%20to%20this%20new%20build%20is%20required!%20Grab%20the%20latest%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmipsdkbins%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmipsdkbins%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe've%20made%20some%20changes%20to%20the%20policy%20file%20that%20will%20break%20downlevel%20versions%20of%20the%20SDK.%20The%20new%20version%20is%20backward%20compatible.%20You'll%20want%20to%20update%20your%20SDK%20builds%20ASAP%20to%20prevent%20any%20issues!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EService%20components%20related%20to%20labeling%20are%20still%20being%20flighted%20only%20to%20non-production%20tenants.%20If%20you%20have%20a%20dev%2Ftest%20tenant%20that%20you'd%20like%20to%20enable%20for%20the%20labeling%20components%2C%20please%20fill%20out%20the%20form%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmipsdkpreviewaccount%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fmipsdkpreviewaccount%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22change-list%22%20id%3D%22toc-hId-900007170%22%20id%3D%22toc-hId-923002693%22%3EChange%20List%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ESplit%20Binaries%2FLibraries%2FHeaders%20by%20API%3C%2FLI%3E%0A%3CLI%3EMicrosoft%20Information%20Protection%20Sync%20Service%20Preview%3C%2FLI%3E%0A%3CLI%3EThird-Party%20app%20registration%20now%20supported!%3C%2FLI%3E%0A%3CLI%3EVarious%20performance%2C%20and%20stability%20updates%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CHR%20%2F%3E%0A%3CH2%20id%3D%22operating-system-support%22%20id%3D%22toc-hId--1652149791%22%20id%3D%22toc-hId--1629154268%22%3EOperating%20System%20Support%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20this%20version%20we're%20including%20functional%20support%20for%20the%20following%20platforms%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EDebian%209%3C%2FLI%3E%0A%3CLI%3EMacOS%3C%2FLI%3E%0A%3CLI%3ERedHat%20Linux%207%3C%2FLI%3E%0A%3CLI%3EUbuntu%2016.04%3C%2FLI%3E%0A%3CLI%3EWindows%20Server%20and%20client%20(all%20supported%20versions)%3C%2FLI%3E%0A%3CLI%3EiOS%20(UPE%20only)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CHR%20%2F%3E%0A%3CH2%20id%3D%22split-binarieslibraries%22%20id%3D%22toc-hId-90660544%22%20id%3D%22toc-hId-113656067%22%3ESplit%20Binaries%2FLibraries%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPrevious%20releases%20of%20the%20MIP%20SDK%20were%20monolithic%20-%20all%20three%20APIs%20were%20bundled%20into%20a%20single%20package%20and%20it%20was%20somewhat%20difficult%20to%20split%20them%20up.%20The%20good%20news%20is%20that%20we've%20now%20split%20them%20up%20for%20you%2C%20by%20API.%20This%20will%20help%20to%20reduce%20the%20size%20of%20applications%20which%20are%20using%20only%20the%20Policy%20or%20Protection%20APIs.%20The%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmipsdkbins%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Elatest%20release%3C%2FA%3E%20is%20a%20zip%20that%20contains%20several%20other%20ZIPs%20and%20tarballs%20for%20the%20various%20supported%20platforms.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3Emip_sdk_API_PLATFORM_Version.%5Bzip%7C.tar.gz%5D%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFile%20API%20on%20Ubuntu%2016.04%2C%20for%20example%2C%20is%3A%20%3CEM%3Emip_sdk_file_ubuntu1604.0.4.456.0.tar.gz%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3EInside%20each%20archive%2C%20you'll%20find%20bins%2C%20headers%2C%20and%20samples.%3C%2FP%3E%0A%3CHR%20%2F%3E%0A%3CH2%20id%3D%22mip-sync-service%22%20id%3D%22toc-hId-1833470879%22%20id%3D%22toc-hId-1856466402%22%3EMIP%20Sync%20Service%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EA%20new%20service%20component%20has%20been%20added%20that%20will%20allow%20third-party%20clients%20to%20authenticate%20and%20download%20policy.%20This%20new%20service%20is%20called%20the%20%3CSTRONG%3EMicrosoft%20Information%20Protection%20Sync%20Service%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%3EThe%20service%20itself%20requires%20no%20configuration%20or%20setup%3B%20it%20simply%20handles%20making%20all%20of%20the%20labels%2C%20protection%20settings%2C%20content%20marking%2C%20and%20other%20MIP-related%20policy%20settings%20available%20to%20SDK%20clients.%20The%20only%20area%20where%20this%20endpoint%20is%20exposed%20is%20in%20Azure%20Active%20Directory%20under%20the%20%3CSTRONG%3EApp%20Registration%20-%26gt%3B%20Required%20Permissions%3C%2FSTRONG%3E%20section.%20The%20SDK%20changes%20to%20utilize%20this%20endpoint%2C%20excluding%20app%20registration%2C%20are%20completely%20transparent%20and%20require%20only%20that%20you%20use%20the%20latest%20build.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22third-party-app-registration%22%20id%3D%22toc-hId--718686082%22%20id%3D%22toc-hId--695690559%22%3EThird-Party%20App%20Registration%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPreviously%2C%20a%20hard-coded%20client%20ID%20was%20required%20to%20test%20and%20develop%20with%20the%20SDK.%20We've%20completed%20the%20work%20to%20enable%20you%20to%20register%20your%20own%20Azure%20AD%20Applications%20and%20to%20provide%20those%20client%20IDs%20to%20the%20MIP%20SDK%20APIs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20register%20your%20application%2C%20follow%20these%20instructions%20from%20the%20Azure%20AD%20docs%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevelop%2Fquickstart-v1-integrate-apps-with-azure-ad%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevelop%2Fquickstart-v1-integrate-apps-with-azure-ad%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnce%20the%20application%20has%20been%20registered%2C%20you'll%20then%20need%20to%20add%20permissions%20to%20the%20application.%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevelop%2Fquickstart-v1-integrate-apps-with-azure-ad%23updating-an-application%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EUpdate%20the%20application%3C%2FA%3E%20by%20following%20the%20steps%20detailed%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevelop%2Fquickstart-v1-integrate-apps-with-azure-ad%23updating-an-application%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%2C%20but%20using%20the%20API%20names%20listed%20in%20the%20table%20below.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUp%20to%20two%20APIs%20are%20required%20for%20the%20SDK%2C%20depending%20on%20which%20MIP%20SDK%20API%20you're%20using%3A%3C%2FP%3E%0A%3CTABLE%3E%0A%3CTHEAD%3E%0A%3CTR%3E%0A%3CTH%3E%3CSTRONG%3EMIP%20SDK%20API%3C%2FSTRONG%3E%3C%2FTH%3E%0A%3CTH%3EAzure%20AD%20App%20Registration%20API%3C%2FTH%3E%0A%3C%2FTR%3E%0A%3C%2FTHEAD%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3EFile%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CP%3EMicrosoft%20Information%20Protection%20Sync%20Service%3C%2FP%3E%0A%3CP%3EMicrosoft%20Rights%20Management%20Service%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3EPolicy%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3EMicrosoft%20Information%20Protection%20Sync%20Service%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3EProtection%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CP%3EMicrosoft%20Information%20Protection%20Sync%20Service%20(for%20pulling%20labels%2Ftemplate%20IDs)%3C%2FP%3E%0A%3CP%3EMicrosoft%20Rights%20Mangement%20Service%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENative%20applications%20don't%20require%20any%20special%20work.%20Provide%20the%20client%20ID%20and%20resource%2C%20get%20a%20token%20for%20the%20services.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EWeb%20app%20%2F%20API%3C%2FSTRONG%3E%20applications%20are%20%3CSTRONG%3Erequired%20to%20use%20certificate-based%20authentication%3C%2FSTRONG%3E.%20We%20will%20have%20samples%20on%20that%20available%20soon.%20For%20now%2C%20the%20best%20CBA%20sample%20can%20be%20found%20over%20at%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fresources%2Fsamples%2Factive-directory-dotnet-daemon-certificate-credential%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Code%20Samples.%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CHR%20%2F%3E%0A%3CH2%20id%3D%22support%22%20id%3D%22toc-hId-1024124253%22%20id%3D%22toc-hId-1047119776%22%3ESupport%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20MIP%20SDK%20is%20still%20in%20public%20preview%20and%20is%20subject%20to%20preview%20support%20terms.%20The%20SDK%20is%20intended%20for%20non-production%20development%20and%20testing%20use%20only!%20We%20will%20announce%20general%20availability%20soon%20and%20at%20that%20time%20the%20SDK%20will%20be%20fully%20supported.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-242022%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20latest%20update%20covers%20the%20set%20of%20changes%20in%20the%20MIP%20SDK%20Public%20Preview%20September%20Update.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-242022%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Information%20Protection%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%20Resources%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EEnterprise%20Mobility%20%2B%20Security%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Information%20Protection%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

MIP SDK Private Preview Update

 

Summary

 

Updating to this new build is required! Grab the latest here: https://aka.ms/mipsdkbins

 

We've made some changes to the policy file that will break downlevel versions of the SDK. The new version is backward compatible. You'll want to update your SDK builds ASAP to prevent any issues!

 

Service components related to labeling are still being flighted only to non-production tenants. If you have a dev/test tenant that you'd like to enable for the labeling components, please fill out the form here: https://aka.ms/mipsdkpreviewaccount

 

Change List

 

  • Split Binaries/Libraries/Headers by API
  • Microsoft Information Protection Sync Service Preview
  • Third-Party app registration now supported!
  • Various performance, and stability updates

Operating System Support

 

In this version we're including functional support for the following platforms:

  • Debian 9
  • MacOS
  • RedHat Linux 7
  • Ubuntu 16.04
  • Windows Server and client (all supported versions)
  • iOS (UPE only)

Split Binaries/Libraries

 

Previous releases of the MIP SDK were monolithic - all three APIs were bundled into a single package and it was somewhat difficult to split them up. The good news is that we've now split them up for you, by API. This will help to reduce the size of applications which are using only the Policy or Protection APIs. The latest release is a zip that contains several other ZIPs and tarballs for the various supported platforms.

 

mip_sdk_API_PLATFORM_Version.[zip|.tar.gz]

 

File API on Ubuntu 16.04, for example, is: mip_sdk_file_ubuntu1604.0.4.456.0.tar.gz

Inside each archive, you'll find bins, headers, and samples.


MIP Sync Service

 

A new service component has been added that will allow third-party clients to authenticate and download policy. This new service is called the Microsoft Information Protection Sync Service.

The service itself requires no configuration or setup; it simply handles making all of the labels, protection settings, content marking, and other MIP-related policy settings available to SDK clients. The only area where this endpoint is exposed is in Azure Active Directory under the App Registration -> Required Permissions section. The SDK changes to utilize this endpoint, excluding app registration, are completely transparent and require only that you use the latest build.

 

Third-Party App Registration

 

Previously, a hard-coded client ID was required to test and develop with the SDK. We've completed the work to enable you to register your own Azure AD Applications and to provide those client IDs to the MIP SDK APIs.

 

To register your application, follow these instructions from the Azure AD docs: https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v1-integrate-apps-with-az...

 

Once the application has been registered, you'll then need to add permissions to the application. Update the application by following the steps detailed here, but using the API names listed in the table below.

 

Up to two APIs are required for the SDK, depending on which MIP SDK API you're using:

MIP SDK API Azure AD App Registration API
File

Microsoft Information Protection Sync Service

Microsoft Rights Management Service

Policy Microsoft Information Protection Sync Service
Protection

Microsoft Information Protection Sync Service (for pulling labels/template IDs)

Microsoft Rights Mangement Service

 

  • Native applications don't require any special work. Provide the client ID and resource, get a token for the services.
  • Web app / API applications are required to use certificate-based authentication. We will have samples on that available soon. For now, the best CBA sample can be found over at Azure Code Samples.

Support

 

The MIP SDK is still in public preview and is subject to preview support terms. The SDK is intended for non-production development and testing use only! We will announce general availability soon and at that time the SDK will be fully supported.