Home
%3CLINGO-SUB%20id%3D%22lingo-sub-295559%22%20slang%3D%22en-US%22%3EAzure%20Information%20Protection%20Documentation%20Update%20for%20December%202018%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295559%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20color%3D%22%230066cc%22%3EDocumentation%20for%20Azure%20Information%20Protection%3C%2FFONT%3E%3C%2FA%3E%20has%20been%20updated%20on%20the%20web%20and%20the%20latest%20content%20has%20a%20%3CSTRONG%3EDecember%202018%3C%2FSTRONG%3E%20(or%20later)%20date%20at%20the%20top%20of%20the%20article.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20biggest%20impact%20to%20the%20docs%20this%20month%20has%20been%20for%20PDF%20support%20-%20and%20more%20specifically%2C%20updates%20to%20reflect%20that%26nbsp%3Bprotecting%20PDFs%20by%20using%20the%20ISO%20standard%20for%20encryption%20is%20now%20the%20default%20for%20the%20Azure%20Information%20Protection%20client.%26nbsp%3BThe%20docs%20were%20also%20updated%20for%20the%20information%26nbsp%3Bthat%20when%20the%20client%20uses%20this%20format%2C%20the%20scanner%20protects%20PDF%20documents%20by%20default%20(no%20longer%20need%20to%20edit%20the%20registry).%20The%20Adobe%20plug-in%20that%20supports%20viewing%20this%20file%20format%2C%20as%20well%20as%20labels%20for%20protected%20PDFs%2C%20was%20also%20released%20as%20general%20availability%20(GA).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20docs%20were%20also%20updated%20for%20a%26nbsp%3Bcouple%20of%20service-side%20updates%20that%20you%20might%20have%20missed%20if%20you%20didn't%20see%20the%20announcements%20on%20Yammer%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAzure%20Information%20Protection%20analytics%20now%20displays%20data%20from%20Windows%2010%20computers%20running%20Windows%20Defender%20Advanced%20Threat%20Protection%2C%20and%20a%20new%20checkbox%20enables%20reporting%20for%20the%20actual%20data%20that%20triggered%20your%20custom%20conditions%20or%20sensitive%20information%20types.%3C%2FLI%3E%0A%3CLI%3EA%20new%20%3CSTRONG%3EPublish%3C%2FSTRONG%3E%20option%20in%20the%20Azure%20portal%20for%20Azure%20Information%20Protection%20clients%2C%20post%20label%20migration.%20Use%20this%20new%20publish%20option%20for%20these%20clients%20only%20(not%20needed%20for%20unified%20labeling%20clients)%26nbsp%3Bif%20you%20make%20changes%20to%20the%20labels%20in%20the%20Office%20365%20Security%20%26amp%3B%20Compliance%20Center.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EAs%20a%20reminder%2C%20the%20end%20of%20support%20for%20the%20Rights%20Management%20sharing%20application%20for%20Windows%20is%20now%20around%20the%20corner%20-%20January%2031st%2C%202019.%20The%20documentation%20for%20this%20older%20application%20will%20be%20removed%20when%20it's%20no%20longer%20supported.%20However%2C%20to%20help%20transition%20to%20the%20Azure%20Information%20Protection%20client%2C%20we%20will%20keep%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fupgrade-client-app%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ETasks%20that%20you%20used%20to%20do%20with%20the%20RMS%20sharing%20application%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20listen%20to%20your%20feedback%20and%20try%20to%20incorporate%20it%20whenever%20possible.%20If%20you're%20having%20a%20break%20from%20work%20because%20of%20the%20holidays%2C%20enjoy%20your%20well-earned%20break.%20When%20you%20return%2C%20let%20me%20know%20if%20you%20have%20feedback%20about%20the%20technical%20documentation%20for%20Azure%20Information%20Protection.%26nbsp%3BI%20also%20encourage%20you%20to%20head%20over%20to%20our%20%3CA%20href%3D%22http%3A%2F%2Fwww.yammer.com%2FAskIPTeam%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20color%3D%22%230066cc%22%3EYammer%3C%2FFONT%3E%3C%2FA%3E%20site%20to%20see%20what%20others%20are%20discussing.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHappy%20New%20Year!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23333399%22%3E%3CSTRONG%3EWhat's%20new%20in%20the%20documentation%20for%20Azure%20Information%20Protection%2C%20December%202018%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Fconfigure-usage-rights%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EConfiguring%20usage%20rights%20for%20Azure%20Rights%20Management%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E-%20Updated%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Fconfigure-usage-rights%23encrypt-only-option-for-emails%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%3EEncrypt-Only%20option%20for%20emails%3C%2FFONT%3E%3C%2FA%3E%20section%20with%20the%20information%20that%20the%26nbsp%3B%3CFONT%3EDecryptAttachmentFromPortal%3C%2FFONT%3E%20parameter%20is%20now%20deprecated.%20Instead%2C%20use%20the%26nbsp%3B%3CFONT%3EDecryptAttachmentForEncryptOnly%3C%2FFONT%3E%20parameter.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Fconfigure-policy-migrate-labels%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EHow%20to%20migrate%20Azure%20Information%20Protection%20labels%20to%20the%20Office%20365%20Security%20%26amp%3B%20Compliance%20Center%3C%2FA%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3E%3CSPAN%3E-%20At%20the%20end%20of%20the%20migration%20procedure%2C%20added%20a%20note%20about%20the%20new%20%3CSTRONG%3EPublish%3C%2FSTRONG%3E%20option%20on%20the%20%3CSTRONG%3EAzure%20Information%20Protection%20-%20Unified%20labeling%3C%2FSTRONG%3E%20blade.%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FFONT%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Fdeploy-aip-scanner%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20color%3D%22%230066cc%22%3EDeploying%20the%20Azure%20Information%20Protection%20scanner%20to%20automatically%20classify%20and%20protect%20files%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3E-%20Updated%26nbsp%3Bwith%20the%20information%20that%20the%20scanner%20protects%20PDF%20documents%20by%20default%20when%20they%20are%20protected%20by%20using%20the%20ISO%20standard%20for%20encryption.%20For%20these%20documents%2C%20just%20like%20Office%20documents%2C%20you%20do%20not%20have%20to%20edit%20the%20registry%20to%20protect%20them.%20The%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Fdeploy-aip-scanner%23editing-the-registry-for-the-scanner%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EEditing%20the%20registry%20for%20the%20scanner%3C%2FA%3E%20section%20is%20also%20updated%20for%20this%20information%2C%20with%20additional%20details%20about%20how%20and%20when%20you%20need%20to%20edit%20the%20registry%20when%20you%20use%20the%20scanner.%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%3EIn%20addition%2C%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Fdeploy-aip-scanner%23prerequisites-for-the-azure-information-protection-scanner%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Eprerequisites%3C%2FA%3E%20section%20now%20includes%20information%20about%20the%20operating%20system's%20support%20for%20long%20paths%2C%20which%20can%20result%20in%20the%20scanner%20being%20unable%20to%20discover%20or%20label%20files.%20This%20is%20the%20same%20information%20published%20as%20a%20tip%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fclient-admin-guide-powershell%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EPowerShell%20section%3C%2FA%3E%20of%20the%20admin%20guide%2C%20but%20repeated%20here%26nbsp%3Bfor%20convenience.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Freports-aip%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20color%3D%22%230066cc%22%3ECentral%20reporting%20for%20Azure%20Information%20Protection%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3E-%20Updated%20to%20include%20the%20new%20data%20from%20Windows%2010%20computers%2C%20running%20Windows%20Defender%20Azure%20Threat%20Protection%20(Windows%20Defender%20ATP).%20The%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Freports-aip%23information-collected-and-sent-to-microsoft%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EInformation%20collected%20and%20sent%20to%20Microsoft%3C%2FA%3E%20section%20is%20updated%20for%20the%20new%20checkbox%20for%20collecting%20and%20storing%20document%20content%20matches.%20Also%20added%20a%20note%20for%20a%20known%20issue%2C%20when%20question%20marks%20can%20display%20in%20paths%20and%20file%20names.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fclient-version-release-history%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20color%3D%22%230066cc%22%3EAzure%20Information%20Protection%20client%3A%20Version%20release%20history%20and%20support%20policy%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E-%20Updated%20%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fclient-version-release-history%23version-141510%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20color%3D%22%230066cc%22%3EVersion%201.41.51.0%3C%2FFONT%3E%3C%2FA%3E%26nbsp%3Bfor%20information%20about%20the%20new%20PDF%20version%20now%20supported%20by%20default%2C%20and%20as%20an%20additional%20change%2C%20the%20scanner%20no%20longer%20sets%20the%20Rights%20Management%20owner%20for%20an%20already%20protected%20file.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%201.37.19.0%20version%20is%20also%20updated%20now%20that%20%3CSTRONG%3EReport%20an%20Issue%3C%2FSTRONG%3E%20can%20be%20added%20to%20both%20GA%20and%20preview%20versions%20of%20the%20client%2C%20by%20using%20an%20advanced%20client%20property.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%201.26.6.0%20and%20%3CFONT%3E1.27.48.0%3C%2FFONT%3E%20release%20sections%20are%20removed%20now%20that%20these%20versions%20are%20out%20of%20support.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fprotected-pdf-readers%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ESupported%20PDF%20readers%20for%20Microsoft%20Information%20Protection%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E-%20Updated%20with%20the%20new%20link%20to%20download%20the%20GA%20version%20of%20the%20plug-in%20for%20the%20latest%20Adobe%26nbsp%3Breader.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%3EPowerShell%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fazureinformationprotection%2FAdd-AIPScannerRepository%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EAdd-AIPScanner%20Repository%3C%2FA%3E%26nbsp%3Band%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fazureinformationprotection%2FSet-AIPScannerRepository%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ESet-AIPScanner%20Repository%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%3E-%20Updated%20the%20descriptions%20for%20the%20following%20parameters%3A%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%3E%3CSTRONG%3EDefaultOwner%3C%2FSTRONG%3E%3A%26nbsp%3B%20Updated%26nbsp%3Bfor%20the%20information%20that%20the%20Rights%20Management%20owner%20is%20not%20changed%20for%20files%20that%20are%20already%20protected.%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%3E%3CSTRONG%3EPreserveFileDetails%3C%2FSTRONG%3E%3A%20%26nbsp%3B%20Updated%20to%20clarify%20that%20this%20parameter%20is%20for%20file%20attributes%20related%20to%20the%20date%20a%20file%20is%20modified%20because%20a%20label%20is%20applied.%20If%20your%20data%20repository%20displays%20the%20date%20the%20file%20was%20last%20accessed%2C%20this%20PowerShell%20parameter%20has%20no%20effect%20on%20that%20file%20attribute%2C%20which%20will%20be%20changed%20when%20the%20scanner%20discovers%20or%20labels%20files.%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CHR%20%2F%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-295559%22%20slang%3D%22en-US%22%3E%3CP%3ECheck%20what's%20new%20%26amp%3B%20changed%20in%20the%20Azure%20Information%20Protection%20docs%20for%20December%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-295559%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Information%20Protection%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDocs%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUpdates%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308115%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Information%20Protection%20Documentation%20Update%20for%20December%202018%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308115%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F259480%22%20target%3D%22_blank%22%3E%40kaibisnes%3C%2FA%3E%20SharePoint%20IRM-protected%20libraries%20currently%20use%20an%20older%20format%20for%20protected%20PDFs%2C%20and%20to%20the%20best%20of%20my%20knowledge%2C%20Adobe%20Reader%20has%20always%20supported%20this%20older%20format.%26nbsp%3B%20The%20updates%20mentioned%20in%20this%20blog%20post%20are%20for%20supporting%20the%20latest%20(ISO)%20format%20for%20protected%20PDFs.%26nbsp%3B%20If%20you're%20having%20problems%20opening%20PDFs%20from%20IRM-protected%20libraries%2C%20use%20the%20technical%20support%20resources%20for%20the%20vendor.%26nbsp%3B%20On%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fprotected-pdf-readers%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ESupported%20PDF%20readers%20for%20Microsoft%20Information%20Protection%3C%2FA%3E%20page%2C%20we%20have%20a%20section%20that%20lists%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fprotected-pdf-readers%23support-for-previous-formats%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ereaders%20that%20support%20previous%20versions%3C%2FA%3E%20for%20protected%20PDFs.%26nbsp%3B%20You%20might%20want%20to%20try%20some%20of%20the%20alternative%20options%20-%20a%20quick%20web%20search%20should%20provide%20information%20about%20licensing%20and%20downloading.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-307919%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Information%20Protection%20Documentation%20Update%20for%20December%202018%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307919%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20for%20quite%20a%20while%20used%20IRM%20protection%20on%20som%20libraries%20in%20Sharepoint.%26nbsp%3B%20Since%20Acrobat%20PDF%20applications%20(Reader%20or%20Pro)%20have%20not%20been%20supported%20we%20have%20used%20Foxit.%26nbsp%3B%20Does%20this%20mean%20that%20we%20now%20can%20use%20Acrobat%20products%20rather%20than%20Foxit%3F%20and%20then%20with%20no%20register%20change%3F%3CBR%20%2F%3EI%20just%20tested%20it%20with%20an%20Acrobat%20downloaded%20early%20december%2C%20but%20that%20didn't%20work!%3C%2FP%3E%3CP%3EIs%20there%20an%20even%20newer%20version%20-%20preferably%20without%20a%20license%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

The Documentation for Azure Information Protection has been updated on the web and the latest content has a December 2018 (or later) date at the top of the article.

 

The biggest impact to the docs this month has been for PDF support - and more specifically, updates to reflect that protecting PDFs by using the ISO standard for encryption is now the default for the Azure Information Protection client. The docs were also updated for the information that when the client uses this format, the scanner protects PDF documents by default (no longer need to edit the registry). The Adobe plug-in that supports viewing this file format, as well as labels for protected PDFs, was also released as general availability (GA).

 

The docs were also updated for a couple of service-side updates that you might have missed if you didn't see the announcements on Yammer:

  • Azure Information Protection analytics now displays data from Windows 10 computers running Windows Defender Advanced Threat Protection, and a new checkbox enables reporting for the actual data that triggered your custom conditions or sensitive information types.
  • A new Publish option in the Azure portal for Azure Information Protection clients, post label migration. Use this new publish option for these clients only (not needed for unified labeling clients) if you make changes to the labels in the Office 365 Security & Compliance Center. 

As a reminder, the end of support for the Rights Management sharing application for Windows is now around the corner - January 31st, 2019. The documentation for this older application will be removed when it's no longer supported. However, to help transition to the Azure Information Protection client, we will keep Tasks that you used to do with the RMS sharing application.

 

We listen to your feedback and try to incorporate it whenever possible. If you're having a break from work because of the holidays, enjoy your well-earned break. When you return, let me know if you have feedback about the technical documentation for Azure Information Protection. I also encourage you to head over to our Yammer site to see what others are discussing. 

 

Happy New Year!

  

What's new in the documentation for Azure Information Protection, December 2018

 

Configuring usage rights for Azure Rights Management

- Updated the Encrypt-Only option for emails section with the information that the DecryptAttachmentFromPortal parameter is now deprecated. Instead, use the DecryptAttachmentForEncryptOnly parameter.

 

How to migrate Azure Information Protection labels to the Office 365 Security & Compliance Center

- At the end of the migration procedure, added a note about the new Publish option on the Azure Information Protection - Unified labeling blade.

  

Deploying the Azure Information Protection scanner to automatically classify and protect files

- Updated with the information that the scanner protects PDF documents by default when they are protected by using the ISO standard for encryption. For these documents, just like Office documents, you do not have to edit the registry to protect them. The Editing the registry for the scanner section is also updated for this information, with additional details about how and when you need to edit the registry when you use the scanner. 

 

In addition, the prerequisites section now includes information about the operating system's support for long paths, which can result in the scanner being unable to discover or label files. This is the same information published as a tip in the PowerShell section of the admin guide, but repeated here for convenience.

 

Central reporting for Azure Information Protection

- Updated to include the new data from Windows 10 computers, running Windows Defender Azure Threat Protection (Windows Defender ATP). The Information collected and sent to Microsoft section is updated for the new checkbox for collecting and storing document content matches. Also added a note for a known issue, when question marks can display in paths and file names.

 

Azure Information Protection client: Version release history and support policy

- Updated  Version 1.41.51.0 for information about the new PDF version now supported by default, and as an additional change, the scanner no longer sets the Rights Management owner for an already protected file.

 

The 1.37.19.0 version is also updated now that Report an Issue can be added to both GA and preview versions of the client, by using an advanced client property.

 

The 1.26.6.0 and 1.27.48.0 release sections are removed now that these versions are out of support.

 

Supported PDF readers for Microsoft Information Protection

- Updated with the new link to download the GA version of the plug-in for the latest Adobe reader.

 

PowerShell: Add-AIPScanner​Repository and Set-AIPScanner​Repository

- Updated the descriptions for the following parameters:

  • DefaultOwner:  Updated for the information that the Rights Management owner is not changed for files that are already protected.
  • PreserveFileDetails:   Updated to clarify that this parameter is for file attributes related to the date a file is modified because a label is applied. If your data repository displays the date the file was last accessed, this PowerShell parameter has no effect on that file attribute, which will be changed when the scanner discovers or labels files.

 

 

2 Comments
Occasional Visitor

We have for quite a while used IRM protection on som libraries in Sharepoint.  Since Acrobat PDF applications (Reader or Pro) have not been supported we have used Foxit.  Does this mean that we now can use Acrobat products rather than Foxit? and then with no register change?
I just tested it with an Acrobat downloaded early december, but that didn't work!

Is there an even newer version - preferably without a license?

Microsoft

@kaibisnes SharePoint IRM-protected libraries currently use an older format for protected PDFs, and to the best of my knowledge, Adobe Reader has always supported this older format.  The updates mentioned in this blog post are for supporting the latest (ISO) format for protected PDFs.  If you're having problems opening PDFs from IRM-protected libraries, use the technical support resources for the vendor.  On the Supported PDF readers for Microsoft Information Protection page, we have a section that lists readers that support previous versions for protected PDFs.  You might want to try some of the alternative options - a quick web search should provide information about licensing and downloading.