Home
%3CLINGO-SUB%20id%3D%22lingo-sub-787898%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-787898%22%20slang%3D%22en-US%22%3E%3CP%3EOffice%20Online%20is%20now%20just%20Office%2C%20or%20on%20the%20web%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-788040%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-788040%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169989%22%20target%3D%22_blank%22%3E%40Nir%20Hendler%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3Ewhat%20do%20I%20do%20with%20the%20Default%20MRM%20Policy%20in%20the%20EAC%20once%20we've%20migrated%20to%20the%20new%20Unified%20Labeling%20system%3F%3C%2FP%3E%3CP%3EWe've%20never%20used%20the%20classic%20exchange%20retention%20policies.%20Do%20I%20just%20delete%20the%20policy%20in%20the%20EAC%3F%20Does%20that%20get%20rid%20of%20the%20Retention%20button%20in%20Outlook%20as%20well%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-788063%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-788063%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1081%22%20target%3D%22_blank%22%3E%40Ivan%20Unger%3C%2FA%3E%26nbsp%3B-%20Everything%20that%20was%20mentioned%20in%20this%20blog%20is%20not%20related%20to%20%22Retention%20labels%22%20and%20doesn't%20affect%20them.%20This%20refers%20to%20%22Sensitivity%22%20labels%20only%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-788183%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-788183%22%20slang%3D%22en-US%22%3E%3CP%3EAm%20I%20understanding%20this%20correctly%2C%20that%20we%20(the%20user)%20are%20not%20supposed%20to%20label%20incoming%20emails%2C%20but%20only%20outgoing%20messages%3F%3C%2FP%3E%3CP%3EAnd%20therefore%20there%20is%20no%20way%20to%20retroactively%20apply%20a%20sensitivity%20label%2C%20like%20%22personal%22%20to%20a%20sent%20message%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783185%22%20slang%3D%22en-US%22%3EUnderstanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783185%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3ETL%3B%20DR%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EUnified%20labeling%20is%20here%20and%20%3C%2FSPAN%3E%3CSPAN%3Eit%20is%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3Enext%20step%20in%20the%20Microsoft%20Information%20Protection%3C%2FSPAN%3E%3CSPAN%3Estor%3C%2FSPAN%3E%3CSPAN%3Ey.%3C%2FSPAN%3E%20%3CSPAN%3EE%3C%2FSPAN%3E%3CSPAN%3Each%3C%2FSPAN%3E%3CSPAN%3Enew%20%3C%2FSPAN%3E%3CSPAN%3EMicrosoft%20%3C%2FSPAN%3E%3CSPAN%3Eproduct%20and%20%3C%2FSPAN%3E%3CSPAN%3Eservice%3C%2FSPAN%3E%3CSPAN%3Ethat%20utilizes%20classification%20and%20protection%20capabilities%3C%2FSPAN%3E%3CSPAN%3E(and%203%3CSUP%3Erd%3C%2FSUP%3Eparty%20ones%20using%20MIP%20%3C%2FSPAN%3E%3CSPAN%3ESDK%20%3C%2FSPAN%3E%3CSPAN%3Ecapabilities)%20%3C%2FSPAN%3E%3CSPAN%3Ewill%20require%20%3C%2FSPAN%3E%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3E%3CSPAN%3E.%20Because%20of%20this%2C%20now%20is%20the%3C%2FSPAN%3E%3CSPAN%3Etime%20to%20execute%20%3C%2FSPAN%3E%3CSPAN%3Ea%3C%2FSPAN%3E%3CSPAN%3Emigration%20%3C%2FSPAN%3E%3CSPAN%3Eto%20this%20service%3C%2FSPAN%3E%3CSPAN%3Eas%3C%2FSPAN%3E%3CSPAN%3Ethere%20is%20%3C%2FSPAN%3E%3CSPAN%3Ezero%3C%2FSPAN%3E%3CSPAN%3Erisk%20when%20done%20properly%20%3C%2FSPAN%3E%3CSPAN%3Efollowing%20our%20recommended%3C%2FSPAN%3E%3CSPAN%3Esteps.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThe%20%3C%2FSPAN%3E%3CSPAN%3Eprimary%3C%2FSPAN%3E%3CSPAN%3Emigration%20plan%20is%20to%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Fconfigure-policy-migrate-labels%23to-migrate-azure-information-protection-labels%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Emigrate%20labels%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Efrom%3C%2FSPAN%3E%3CSPAN%3Ethe%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Fconfigure-policy-migrate-labels%23to-migrate-azure-information-protection-labels%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20blade%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Ein%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3EAzure%20%3C%2FSPAN%3E%3CSPAN%3Ep%3C%2FSPAN%3E%3CSPAN%3Eortal%20to%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2Ftagslibrary%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20365%20Security%20%26amp%3B%20Compliance%20Center%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3E%2C%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FOffice365%2FSecurityCompliance%2Fsensitivity-labels%23what-label-policies-can-do%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ere-create%20your%20label%20policies%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FOffice365%2FSecurityCompliance%2Fapply-sensitivity-label-automatically%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Econditions%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Eand%20deploy%20the%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Funifiedlabelingclient-version-release-history%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Elatest%20unified%20labeling%20client%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Eas%20a%20new%20installation%20or%20in-place%20upgrade%20to%20the%20%3C%2FSPAN%3E%3CSPAN%3EAzure%20Information%20Protection%20client%3C%2FSPAN%3E%3CSPAN%3E(classic)%3C%2FSPAN%3E%3CSPAN%3E.%20If%20you%20want%20to%20understand%20why%20this%20is%20necessary%20and%20why%20t%3C%2FSPAN%3E%3CSPAN%3Ehe%20migration%20plan%20is%20not%20as%20complicated%20as%20it%20initially%20sound%2C%20%3C%2FSPAN%3E%3CSPAN%3Eplease%20%3C%2FSPAN%3E%3CSPAN%3Econtinue%20%3C%2FSPAN%3E%3CSPAN%3Eto%20review%20the%20information%20contained%20in%20this%20blog%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CU%3ENote%3A%20Unified%20labeling%20support%20is%20only%20available%20for%20commercial%20cloud%20tenants.%3C%2FU%3E%3CU%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125561i74C6757FA4CE0EB6%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CSPAN%3EU%3C%2FSPAN%3E%3CSPAN%3Enified%20label%3C%2FSPAN%3E%3CSPAN%3Eing%20Migration%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EBack%20%3CSPAN%3Ei%3C%2FSPAN%3En%202016%20when%20%3CSPAN%3Ethe%20%3C%2FSPAN%3EAzure%20Information%20Protection%20client%20was%20initially%20released%2C%20it%20was%20the%20first%20Microsoft%20product%20that%20introduced%20labeling%20capabilities%20which%20was%20applied%20on%20top%20of%20the%20already%20available%20Azure%20Rights%20Management%20service.%20%3CSPAN%3EThe%20%3C%2FSPAN%3EAzure%20Information%20Protection%20%3CSPAN%3Eblade%20in%20the%20Azure%20%3C%2FSPAN%3Eportal%20replaced%20the%20old%20Azure%20Rights%20Management%20%3CSPAN%3Einterface%20%3C%2FSPAN%3Ewhich%20was%20available%20only%20in%20%3CSPAN%3Ethe%20%3C%2FSPAN%3EAzure%20%3CSPAN%3Eclassic%20%3C%2FSPAN%3Eportal%3CSPAN%3E.%26nbsp%3B%20At%20that%20point%2C%3C%2FSPAN%3EAzure%20Information%20Protection%20was%20the%20only%20product%20that%20supported%20labeling%3CSPAN%3Eof%20sensitive%20content%3C%2FSPAN%3Eas%20part%20of%20Microsoft%20portfolio.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBased%20on%20customer%20feedback%20and%20%3CSPAN%3Ethe%20evolution%20of%20%3C%2FSPAN%3EOffice%20365%2C%20a%20strategic%20decision%3CSPAN%3Ewas%20made%3C%2FSPAN%3Eto%20integrate%20Azure%20Information%20Protection%20labeling%20capabilities%20into%20Office%20365%20services.%20%3CSPAN%3EBecause%20the%3C%2FSPAN%3EOffice%20365%20s%3CSPAN%3Euite%3C%2FSPAN%3Eof%20products%20%3CSPAN%3Ewe%3C%2FSPAN%3Ere%20managed%20from%20the%20Office%20%3CSPAN%3Emanagement%20%3C%2FSPAN%3Eportals%20and%20the%20plan%20included%20a%20big%20initiative%20to%20integrate%20Azure%20Information%20Protection%20labeling%20capabilities%3CSPAN%3Einto%20Office%20365%20and%20many%20other%20Microsoft%20and%203%3CSUP%3Erd%3C%2FSUP%3Eparty%3C%2FSPAN%3Eproducts%2C%20a%20unified%20approach%20has%20been%20agreed%20%3CSPAN%3Eupon%20%3C%2FSPAN%3Eand%20initiated%20these%20changes%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EMicrosoft%20introduce%3CSPAN%3Ed%3C%2FSPAN%3Ea%20unified%20SDK%20to%20be%20implemented%20by%20all%20applications%20and%20services%20that%20want%20to%20use%20Azure%20Information%20Protection%20%3CSPAN%3Eclassification%20and%20%3C%2FSPAN%3Elabeling%20%E2%80%93%20the%20%3CSTRONG%3EMicrosoft%20Information%20Protection%20SDK.%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3EA%20unified%20backend%20in%20the%20Office%20365%20eco-system%20to%20manage%20the%20Azure%20Information%20Protection%20labels%20%E2%80%93%20the%20%3CSTRONG%3EOffice%20365%20Security%20%26amp%3B%20Compliance%20%3C%2FSTRONG%3E%3CSTRONG%3E%3CSPAN%3ECenter%3C%2FSPAN%3E%3C%2FSTRONG%3E(%3CSPAN%3Esame%20%3C%2FSPAN%3E%3CSPAN%3Elabel%20%3C%2FSPAN%3E%3CSPAN%3Eadmin%20capabilities%20are%20%3C%2FSPAN%3E%3CSPAN%3Ealso%20available%20at%3C%2FSPAN%3E%3CSTRONG%3EMicrosoft%20365%20Security%3C%2FSTRONG%3E%3CSPAN%3Eand%20%3C%2FSPAN%3E%3CSTRONG%3EMicrosoft%20365%20Compliance%3C%2FSTRONG%3Eportals).%3C%2FLI%3E%0A%3CLI%3EReferring%20to%20Azure%20Information%20Protection%20labels%20in%20a%20consistent%20and%20short%20name%3CSPAN%3Ewhich%20will%20also%20differentiate%20from%20Retention%20labels%20that%20are%20already%20exist%20in%20Office%20365%20platform%3C%2FSPAN%3E%E2%80%93%20%3CSTRONG%3ESensitivity%20labels%3C%2FSTRONG%3E.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EPerforming%20these%20changes%20caused%20the%20creation%20of%20a%20new%20label%20management%20%3CSPAN%3Etab%3C%2FSPAN%3E%2C%20in%20addition%20to%20a%20new%20client%20that%20is%20based%20on%20the%20Microsoft%20Information%20Protection%20SDK.%20Unlocking%20the%20availability%20of%20Sensitivity%20labels%20across%20the%20complete%20Microsoft%20365%20platform.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAt%20the%20time%20of%20writing%20this%20blog%20(August%202019)%2C%20there%20are%202%20%3CSPAN%3Emain%20%3C%2FSPAN%3Elabel%20management%20portals%20which%20are%20supported%20by%20different%20products%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CSTRONG%3EAzure%20Information%20Protection%20%3CSPAN%3Eblade%20%3C%2FSPAN%3Ein%20%3CSPAN%3Ethe%20%3C%2FSPAN%3EAzure%20%3C%2FSTRONG%3E%3CSTRONG%3E%3CSPAN%3Eportal%3C%2FSPAN%3E%3C%2FSTRONG%3E-%20Supported%20by%3A%3COL%3E%0A%3CLI%3E%3CSPAN%3EThe%20%3C%2FSPAN%3EAzure%20Information%20Protection%20client%3CSPAN%3E(classic)%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20%3C%2FSPAN%3EAzure%20Information%20Protection%20%3CSPAN%3Es%3C%2FSPAN%3Ecanner%3C%2FLI%3E%0A%3CLI%3EMicrosoft%20Cloud%20App%20Security%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EUnified%20label%3CSPAN%3Eing%3C%2FSPAN%3Econsole%20in%20Office%20365%20Security%20%3CSPAN%3E%26amp%3B%20%3C%2FSPAN%3ECompliance%20%3CSPAN%3ECenter%20%3C%2FSPAN%3E%3C%2FSTRONG%3E%E2%80%93%20Supported%20by%3A%3COL%3E%0A%3CLI%3E%3CSPAN%3EThe%20%3C%2FSPAN%3EAzure%20Information%20Protection%20%3CSPAN%3Eunified%20%3C%2FSPAN%3Elabeling%20client%3C%2FLI%3E%0A%3CLI%3EMicrosoft%20Cloud%20App%20Security%3C%2FLI%3E%0A%3CLI%3EOffice%20apps%20for%20MacOS%3C%2FLI%3E%0A%3CLI%3EOffice%20apps%20for%20Android%3C%2FLI%3E%0A%3CLI%3EOffice%20apps%20for%20iOS%3C%2FLI%3E%0A%3CLI%3EMicrosoft%20Information%20Protection%20SDK%20and%20applications%20based%20on%20it%20(For%20example%3A%20Adobe%20Acrobat)%3C%2FLI%3E%0A%3CLI%3EComing%20Soon%3A%3COL%3E%0A%3CLI%3ESharePoint%20Online%3C%2FLI%3E%0A%3CLI%3EOffice%20%3CSPAN%3Efor%20the%20web%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3EBuilt-in%20%3CSPAN%3Elabeling%20in%20%3C%2FSPAN%3EOffice%20for%20Windows%20(no%20need%20%3CSPAN%3Efor%3C%2FSPAN%3Ean%20add-in)%3C%2FLI%3E%0A%3CLI%3EOutlook%20%3CSPAN%3Eweb%20app%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3EOutlook%20%3CSPAN%3EMobile%20%3C%2FSPAN%3E(iOS%20and%20Android)%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20%3C%2FSPAN%3E%3CSPAN%3EAzure%20Information%20Protection%20%3C%2FSPAN%3E%3CSPAN%3Es%3C%2FSPAN%3E%3CSPAN%3Ecanner%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EAs%20you%20can%20see%20and%20understand%2C%20moving%20forward%2C%20every%20app%20and%20service%20that%20implement%20labeling%20capabilities%20in%20Microsoft%20will%20be%20using%20%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3Eexclusively.%20In%20addition%20to%20that%2C%20the%20Azure%20Information%20Protection%20client%20%3CSPAN%3E(classic)%20%3C%2FSPAN%3Eand%20portals%20are%20still%20here%20but%20not%20for%20long%20(a%20separate%20announcement%20will%20be%20published%20with%20specific%20plans).%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3ELastly%2C%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20supports%20advanced%20capabilities%20that%20aren%E2%80%99t%20available%20when%20Azure%20Information%20Protection%20labels%20are%20in%20use%20and%20are%20now%20available%20as%20part%20of%20the%20native%20integration%20with%20the%20Microsoft%20365%20platform%3CSPAN%3E.%20Some%20of%20these%20capabilities%20are%3C%2FSPAN%3E%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FOffice365%2FSecurityCompliance%2Fapply-sensitivity-label-automatically%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAdvanced%20label%20automation%3C%2FA%3Ewith%20the%20same%20logic%20as%20used%20by%20Office%20365%20DLP%20with%20sensitive%20information%20types%2C%20custom%20and%20pre-defined.%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FOffice365%2FSecurityCompliance%2Fsensitivity-labels%23what-label-policies-can-do%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EFlexible%20label%20polices%3C%2FA%3Ewhich%20now%20can%20scope%20%3CSPAN%3Ethe%20%3C%2FSPAN%3Esame%20label%20to%20multiple%20policies.%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FOffice365%2FSecurityCompliance%2Fsensitivity-labels%23where-sensitivity-labels-can-appear%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EUnified%20%3CSPAN%3Eexperience%20%3C%2FSPAN%3Ewith%20applying%20sensitivity%20labels%3C%2FA%3Eacross%20Office%20365%20apps%20and%20services.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3E%3CU%3EThere%20is%20no%20risk%3CSPAN%3Efor%20end%20users%20and%20production%20%3C%2FSPAN%3E%3CSPAN%3Eenvironment%3C%2FSPAN%3E%3C%2FU%3E%3C%2FSTRONG%3Ein%20migrating%20to%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20today%2C%20the%20migration%20process%20copies%20labels%20from%20Azure%20Information%20Protection%20backend%20to%20Security%20and%20Compliance%20backend%20but%20not%20its%20policies.%20So%20as%20long%20you%20didn%E2%80%99t%20publish%20a%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20policy%20or%20didn%E2%80%99t%20deployed%20an%20application%20that%20support%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%2C%20nothing%20happens%20for%20end%20users!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%2C%20what%20now%3F%20%3CSTRONG%3EIt%E2%80%99s%20time%20to%20migrate%20to%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing!%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAre%20you%20a%20%3CSTRONG%3Enew%20customer%3C%2FSTRONG%3Ewho%3CSPAN%3Eis%3C%2FSPAN%3Ejust%20starting%20your%20Information%20Protection%20journey%3F%20Start%20with%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20and%20create%20your%20policies%20and%20labels%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2Ftagslibrary%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20365%20Security%20%3CSPAN%3E%26amp%3B%20%3C%2FSPAN%3ECompliance%3C%2FA%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2Ftagslibrary%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECenter%3C%2FA%3E(Or%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fcompliance.microsoft.com%2Flabels%3Fviewid%3Dsensitivity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20365%20Compliance%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3E%2F%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsecurity.microsoft.com%2Flabels%3Fviewid%3Dsensitivity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20365%20Security%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Eportals%20in%20case%20you%20are%20a%20Microsoft%20365%20customer)%3C%2FSPAN%3E.%20New%20tenants%20are%20already%20enabled%20with%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%2C%20so%20no%20action%20is%20required%20from%20your%20side.%20If%20no%20labels%20are%20already%20created%20and%20you%20wish%20to%20leverage%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Fconfigure-policy-default%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20default%20labels%3C%2FA%3E%2C%20go%20to%20%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%23blade%2FMicrosoft_Azure_InformationProtection%2FDataClassGroupEditBlade%2FglobalBlade%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20%3C%2FA%3E%3CSPAN%3Eblade%3C%2FSPAN%3Ein%20%3CSPAN%3Ethe%20%3C%2FSPAN%3EAzure%20%3CSPAN%3Eportal%20%3C%2FSPAN%3Eand%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Fquickstart-viewpolicy%23create-labels---if-necessary%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Egenerate%20the%20default%20labels%3C%2FA%3E(Fig.%201).%20In%20addition%2C%20verify%20that%20your%20tenant%20is%20already%20migrated%20to%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%2C%20if%20not%2C%20go%20to%20the%20%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%23blade%2FMicrosoft_Azure_InformationProtection%2FDataClassGroupEditBlade%2FmigrationActivationBlade%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20blade%3C%2FA%3Eand%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Fconfigure-policy-migrate-labels%23to-migrate-azure-information-protection-labels%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eactivate%20the%20migration%3C%2FA%3E(Fig.%202).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH6%20style%3D%22text-align%3A%20center%3B%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%20id%3D%22toc-hId-1009276317%22%3EFig%201.%20Generate%20default%20labels%3C%2FH6%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125562i3B69817077D397B1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_1.png%22%20title%3D%22clipboard_image_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH6%20style%3D%22text-align%3A%20center%3B%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%20id%3D%22toc-hId--1542880644%22%3EFig%202.%20Unified%20labeling%20migration%20activated%3C%2FH6%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125563i0E531821A8173773%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_2.png%22%20title%3D%22clipboard_image_2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EAre%20you%20an%20%3CSTRONG%3Eexisting%20Azure%20Information%20Protection%20customer%3C%2FSTRONG%3Ewho%20wish%20to%20migrate%20to%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%3F%20Here%20are%20the%20suggested%20steps%20you%20should%20perform%20to%20plan%20and%20execute%20the%20migration%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPhase%201%20%E2%80%93%20Planning%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EU%3C%2FSPAN%3E%3CSPAN%3Enified%20labels%3C%2FSPAN%3Esupport%20most%20functionalities%20that%20are%20available%20in%20Azure%20Information%20Protection%20labels%2C%20some%20functionalists%20are%20not%20available%20and%20some%20are%20configured%20differently%20when%20managed%20from%20%3CSPAN%3Ethe%20%3C%2FSPAN%3ESecurity%20%3CSPAN%3E%26amp%3B%20%3C%2FSPAN%3ECompliance%20%3CSPAN%3ECenter%3C%2FSPAN%3E.%20Please%20review%20the%20following%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Fconfigure-policy-migrate-labels%23label-settings-that-are-not-supported-in-the-admin-centers%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ELabel%20settings%20that%20are%20not%20supported%20in%20the%20admin%20centers%3C%2FA%3Eand%20learn%20how%20they%20are%20manageable.%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fuse-client%23compare-the-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EClient%20differences%3C%2FA%3Ebetween%20the%20%3CSPAN%3Eclassic%20client%20for%20Azure%20Information%20Protection%2C%20%3C%2FSPAN%3Eand%20the%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20client.%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fuse-client%23features-not-planned-to-be-in-the-azure-information-protection-unified-labeling-client%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EFeatures%20not%20planned%20to%20be%20in%20the%20Azure%20Information%20Protection%20unified%20labeling%20client%3C%2FA%3E.%20As%20a%20clarification%20please%20note%20that%20although%20%3CSPAN%3Ecustom%20%3C%2FSPAN%3E%3CSPAN%3Epermissions%20%3C%2FSPAN%3Eare%20not%20supported%20in%20the%20%3CSPAN%3Eunified%20%3C%2FSPAN%3E%3CSPAN%3Elabeling%20%3C%2FSPAN%3Eclient%20as%20a%20standalone%20action%3CSPAN%3Ewith%20the%20Office%20add-in%3C%2FSPAN%3E%3CSPAN%3E%2C%3C%2FSPAN%3Eit%20is%20supported%20as%20a%20label%20that%20is%20configured%20with%20User%20Defined%20Permissions%20action.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EIf%20one%20of%20the%20documented%20differences%20impact%20your%20end%20users%3CSPAN%3E%E2%80%99%3C%2FSPAN%3Ebehavior%2C%20please%20reflect%20this%20accordingly%20in%20your%20end%20user%20communication%20before%20%3CSPAN%3Edeploying%20%3C%2FSPAN%3Ethe%20latest%20client%20and%20publish%3CSPAN%3Eing%3C%2FSPAN%3Ethe%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3E%3CSPAN%3Eing%3C%2FSPAN%3Epolicy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20%3CSPAN%3Eof%20%3C%2FSPAN%3E%3CSPAN%3Etoday%3C%2FSPAN%3E(August%202019)%2C%20%3CSPAN%3Ethe%20%3C%2FSPAN%3EAzure%20Information%20Protection%20scanner%20support%3CSPAN%3Es%3C%2FSPAN%3Eonly%20labels%20from%20Azure%20Information%20Protection%20%3CSPAN%3Eblade%3C%2FSPAN%3E%3CSPAN%3Ebut%20%3C%2FSPAN%3E%3CSPAN%3Et%3C%2FSPAN%3Ehis%20is%20not%20a%20blocker%20as%20the%20Azure%20Information%20Protection%20label%3CSPAN%3Emetadata%20is%20%3C%2FSPAN%3Eidentical%20to%20%3CSPAN%3Eunified%20labels%3C%2FSPAN%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESame%20applied%20for%20Azure%20Information%20Protection%20%3CSPAN%3Eanalytics%20%3C%2FSPAN%3E(Preview)%20which%20is%20available%20with%20full%20feature%20set%20in%20Azure%20Information%20Protection%20%3CSPAN%3Eblade%20%3C%2FSPAN%3Ebut%20do%20cover%20analytics%20from%20the%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20client%20as%20well.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPhase%202%20%E2%80%93%20Service%20migration%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EAfter%20you%20have%20reviewed%20the%201%3CSUP%3Est%3C%2FSUP%3Ephase%2C%20it%E2%80%99s%20time%20to%20%3CSPAN%20style%3D%22font-weight%3A%20normal%20!msorm%3B%22%3E%3CSTRONG%3Emigrate%20your%20labels%3C%2FSTRONG%3E%3C%2FSPAN%3Eto%20the%20Security%20%3CSPAN%3E%26amp%3B%3C%2FSPAN%3ECompliance%20%3CSPAN%3ECenter%3C%2FSPAN%3E.%20I%3CSPAN%3Et%20is%20i%3C%2FSPAN%3Emportant%20to%20mention%20that%20%3CSPAN%3E%E2%80%9C%3C%2FSPAN%3EMigrate%E2%80%9D%20doesn%E2%80%99t%20mean%20you%20need%20to%20move%20away%20from%20%3CSPAN%3Emanaging%20labels%20and%20policies%20in%20the%20%3C%2FSPAN%3EAzure%20Information%20Protection%20%3CSPAN%3Eblade%20%3C%2FSPAN%3Eand%20%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3EAzure%20Information%20Protection%20%3C%2FSPAN%3Eclient%3CSPAN%3E(classic)%3C%2FSPAN%3E.%20Th%3CSPAN%3Eis%3C%2FSPAN%3Emigration%20can%20happen%20in%20the%20background%20and%20work%3CSPAN%3Es%3C%2FSPAN%3Eside%20by%20side%20with%20no%20additional%20configuration.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20happen%3CSPAN%3Es%3C%2FSPAN%3Ewhen%20you%20migrate%20your%20labels%20to%20%3CSPAN%3Eunified%20labels%3C%2FSPAN%3E%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBefore%20you%20activate%20the%20migration%2C%20both%20Azure%20Information%20Protection%20backend%20and%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20backend%20are%202%20separate%20services%20which%20work%20independently%20(Fig.%203).%20Once%20you%20activate%20the%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20migration%2C%20the%20labels%20are%20copied%20from%20the%20Azure%20Information%20Protection%20backend%20to%20the%20%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3Ebackend%20and%20both%20services%20are%20using%20the%20same%20backend%20to%20store%20labels%20(Fig.%204).%20Th%3CSPAN%3Eis%3C%2FSPAN%3Emean%3CSPAN%3Es%3C%2FSPAN%3Ethat%20every%20change%20you%20perform%20to%20any%20label%20at%20any%20portal%20will%20be%20change%3CSPAN%3Ed%3C%2FSPAN%3Ealso%20in%20the%20other%20portal.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH6%20style%3D%22text-align%3A%20center%3B%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%20id%3D%22toc-hId-199929691%22%3EFig%203.%20Service%20architecture%20%3CSTRONG%3Epre%3C%2FSTRONG%3E-%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20migration%3C%2FH6%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125564i3AFD292140FDCCDD%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_3.png%22%20title%3D%22clipboard_image_3.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH6%20style%3D%22text-align%3A%20center%3B%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%20id%3D%22toc-hId-1942740026%22%3EFig%204.%20Service%20architecture%20%3CSTRONG%3Epost%3C%2FSTRONG%3E%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20migration%3C%2FH6%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125565iFF785EA7C8C71931%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_4.png%22%20title%3D%22clipboard_image_4.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAfter%20you%20activate%20the%20%3C%2FSPAN%3E%3CSPAN%3Eunified%20label%3C%2FSPAN%3E%3CSPAN%3Eing%20migration%2C%20%3C%2FSPAN%3E%3CSPAN%3Eyour%20labels%20are%20expected%20to%20be%20visible%20in%20both%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%23blade%2FMicrosoft_Azure_InformationProtection%2FDataClassGroupEditBlade%2FglobalBlade%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20blade%3C%2FA%3Eand%20%3CA%20href%3D%22https%3A%2F%2Fcompliance.microsoft.com%2Flabels%3Fviewid%3Dsensitivity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eunified%20labeling%20page%20in%20the%20Security%20%26amp%3B%20Compliance%20Center%3C%2FA%3E(Fig%20%3C%2FSPAN%3E%3CSPAN%3E5%3C%2FSPAN%3E%3CSPAN%3E).%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH6%20style%3D%22text-align%3A%20center%3B%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%20id%3D%22toc-hId--609416935%22%3E%3CSPAN%3EFig%205.%20Azure%20Information%20Protection%20and%20%3C%2FSPAN%3E%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3E%3CSPAN%3Ein%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3EMicrosoft%20365%3C%2FSPAN%3E%3CSPAN%3Ec%3C%2FSPAN%3E%3CSPAN%3Eompliance%20%3C%2FSPAN%3E%3CSPAN%3Ec%3C%2FSPAN%3E%3CSPAN%3Eenter%3C%2FSPAN%3E%3CSPAN%3Epost%20migration%20UI.%3C%2FSPAN%3E%3C%2FH6%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125566iEF072A79C0353A68%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_5.png%22%20title%3D%22clipboard_image_5.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EMoving%20forward%20you%20can%20manage%20your%20labels%20at%20one%20place.%20%3C%2FSPAN%3E%3CSPAN%3EAfter%20the%20migration%2C%20when%20you%20edit%20a%20migrated%20label%20in%20the%20Azure%20Information%20Protection%20blade%2C%20the%20same%20change%20is%20automatically%20reflected%20in%20the%20admin%20centers.%20However%2C%20when%20you%20edit%20a%20migrated%20label%20in%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3ESecurity%20%26amp%3B%20Compliance%20Center%3C%2FSPAN%3E%3CSPAN%3E%2C%20you%20must%20return%20to%20the%20Azure%20%3C%2FSPAN%3E%3CSPAN%3EInformation%20Protection%20blade%2C%20go%20to%3C%2FSPAN%3E%3CSPAN%3EAzure%20Information%20Protection%20-%20Unified%20labeling%20blade%2C%20and%20select%20Publish.%20This%20additional%20action%20is%20needed%20for%20the%20Azure%20Information%20Protection%20%3C%2FSPAN%3E%3CSPAN%3Eclients%20%3C%2FSPAN%3E%3CSPAN%3E(classic)%20%3C%2FSPAN%3E%3CSPAN%3Eto%20pick%20up%20the%20label%20changes.%3C%2FSPAN%3E%20%3CSPAN%3EOnce%20you%20are%20fully%20migrated%20to%20the%20unified%20label%3C%2FSPAN%3E%3CSPAN%3Eing%20client%2C%20you%20no%20longer%20need%20to%20do%20this%20step%2C%20so%20migrating%20quickly%20helps%20to%20reduce%20this%20administrative%20overhead.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAs%20you%20%3C%2FSPAN%3E%3CSPAN%3Emay%3C%2FSPAN%3E%3CSPAN%3Enotice%2C%20label%20configuration%20in%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3ESecurity%20%26amp%3B%20Compliance%20Center%3C%2FSPAN%3E%3CSPAN%3Edoesn%E2%80%99t%20include%20some%20of%20the%20advanced%20%3C%2FSPAN%3E%3CSPAN%3Es%3C%2FSPAN%3E%3CSPAN%3Eettings%3C%2FSPAN%3E%3CSPAN%3Ethat%20%3C%2FSPAN%3E%3CSPAN%3Ewere%3C%2FSPAN%3E%3CSPAN%3Eable%20to%20be%20configured%20using%20Azure%20Information%20Protection%20labels.%20%3C%2FSPAN%3E%3CSPAN%3EThese%20configurations%20%3C%2FSPAN%3E%3CSPAN%3Eare%20now%3C%2FSPAN%3E%3CSPAN%3Eapplied%20to%20the%20label%20after%20its%20initial%20creation%20%2F%20migration%20using%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fpowershell%2Fexchange%2Foffice-365-scc%2Fconnect-to-scc-powershell%2Fconnect-to-scc-powershell%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESecurity%20and%20Compliance%20PowerShell%20module%3C%2FA%3E.%20Here%20are%20few%20examples%20%3C%2FSPAN%3E%3CSPAN%3Eof%20these%3C%2FSPAN%3E%3CSPAN%3Econfigurations%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-customizations%23specify-a-color-for-the-label%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESpecify%20a%20color%20for%20the%20label%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-customizations%23specify-a-default-sublabel-for-a-parent-label%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESpecify%20a%20default%20sublabel%20for%20a%20parent%20label%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-customizations%23configure-a-label-to-apply-smime-protection-in-outlook%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EConfigure%20a%20label%20to%20apply%20S%2FMIME%20protection%20in%20Outlook%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EA%20f%3C%2FSPAN%3E%3CSPAN%3Eull%20list%20of%20all%20the%20advanced%20%3C%2FSPAN%3E%3CSPAN%3Elabel%3C%2FSPAN%3E%3CSPAN%3Esettings%20is%20%3C%2FSPAN%3E%3CSPAN%3Epublished%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-customizations%23available-advanced-settings-for-labels%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3Ewith%20instructions%20how%20to%20apply%20them.%20Please%20note%20that%20these%20%3C%2FSPAN%3E%3CSPAN%3Elabel%20%3C%2FSPAN%3E%3CSPAN%3Eadvanced%20settings%20are%20supported%20only%20by%20the%20Azure%20Information%20Protection%20%3C%2FSPAN%3E%3CSPAN%3Eu%3C%2FSPAN%3E%3CSPAN%3Enified%20%3C%2FSPAN%3E%3CSPAN%3El%3C%2FSPAN%3E%3CSPAN%3Eabeling%20client%20%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3Eon%20Windows%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3Eand%20not%20by%20the%20Office%20365%20built-in%20integration%20with%20unified%20labeling.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22font-weight%3A%20normal%20!msorm%3B%22%3E%3CSTRONG%3EWhat%20doesn%E2%80%99t%20migrate%20and%20need%20to%20be%20created%3CSPAN%3Eseparately%3C%2FSPAN%3E%3F%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ELabel%20policies%3C%2FLI%3E%0A%3CLI%3ELabel%20conditions%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3ELabel%20translations%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EWhy%3F%20As%20mentioned%20earlier%20in%20this%20blog%2C%20policies%20and%20conditions%20are%20more%20flexible%20and%20%3CSPAN%3Ehave%20additional%20advanced%20settings.%26nbsp%3B%20Thus%2C%20they%3C%2FSPAN%3E%3CSPAN%3Ecannot%3C%2FSPAN%3Ebe%3CSPAN%3Edirectly%3C%2FSPAN%3E%3CSPAN%3Etranslated%3C%2FSPAN%3Eacross%20the%20services.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EYou%20should%20create%20your%20%3CSTRONG%3ELabel%20policies%3C%2FSTRONG%3Emanually%20in%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3ESecurity%20%3C%2FSPAN%3E%3CSPAN%3E%26amp%3B%3C%2FSPAN%3E%3CSPAN%3ECompliance%20%3C%2FSPAN%3E%3CSPAN%3EC%3C%2FSPAN%3E%3CSPAN%3Eenter%2C%3C%2FSPAN%3E%3CSPAN%3Eso%20they%20reflect%20your%20current%20settings%20as%20they%20are%20configured%20in%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3EAzure%20%3C%2FSPAN%3E%3CSPAN%3Eportal%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%20%3CSPAN%3ETo%20do%20so%2C%20go%20to%20%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2Ftagspolicy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ELabel%20Policies%3C%2FA%3Econsole%20and%20create%20a%20new%20policy%20%3C%2FSPAN%3E%3CSPAN%3Eby%3C%2FSPAN%3E%3CSPAN%3Eclicking%20the%20%E2%80%9CPublish%20labels%E2%80%9D%20button%20(Fig%20%3C%2FSPAN%3E%3CSPAN%3E6%3C%2FSPAN%3E%3CSPAN%3E).%20Follow%20the%20configuration%20steps%20to%20verify%20these%20are%20configured%20pro%3C%2FSPAN%3E%3CSPAN%3Eperly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH6%20style%3D%22text-align%3A%20center%3B%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%20id%3D%22toc-hId-1133393400%22%3E%3CSPAN%3EFig%20%3C%2FSPAN%3E%3CSPAN%3E6%3C%2FSPAN%3E%3CSPAN%3E.%20Label%20policies%20page%20in%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3ESecurity%20%26amp%3B%20Compliance%20Center%3C%2FSPAN%3E%3C%2FH6%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125567i32A14A821A2311B3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_6.png%22%20title%3D%22clipboard_image_6.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAs%20an%20Azure%20Information%20Protection%20admin%2C%20you%20%3C%2FSPAN%3E%3CSPAN%3Eprobably%3C%2FSPAN%3E%3CSPAN%3Enotice%3C%2FSPAN%3E%3CSPAN%3Ed%3C%2FSPAN%3E%3CSPAN%3Ethat%20some%20policy%20configurations%20are%20not%20%3C%2FSPAN%3E%3CSPAN%3Eavailable%3C%2FSPAN%3E%3CSPAN%3Ewhen%20you%20configure%20your%20policy%20in%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3ESecurity%20%26amp%3B%20Compliance%20Center%3C%2FSPAN%3E%3CSPAN%3E.%20%3C%2FSPAN%3E%3CSPAN%3EThese%20configurations%20shou%3C%2FSPAN%3E%3CSPAN%3Eld%20be%20applied%20to%20the%20policy%20you%20created%20in%20%3C%2FSPAN%3E%3CSPAN%3Eth%3C%2FSPAN%3E%3CSPAN%3Ee%20%3C%2FSPAN%3E%3CSPAN%3ESecurity%20%26amp%3B%20Compliance%20Center%3C%2FSPAN%3E%3CSPAN%3Ea%3C%2FSPAN%3E%3CSPAN%3Efter%20its%20initial%20creation%20and%20using%20the%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fpowershell%2Fexchange%2Foffice-365-scc%2Fconnect-to-scc-powershell%2Fconnect-to-scc-powershell%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESecurity%20%26amp%3B%20Compliance%20PowerShell%20module%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3E.%20%3C%2FSPAN%3E%3CSPAN%3EHere%20are%20few%20examples%20for%20such%20co%3C%2FSPAN%3E%3CSPAN%3Enfigurations%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-customizations%23for-email-messages-with-attachments-apply-a-label-that-matches-the-highest-classification-of-those-attachments%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EFor%20email%20messages%20with%20attachments%2C%20apply%20a%20label%20that%20matches%20the%20highest%20classification%20of%20those%20attachments%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-customizations%23implement-pop-up-messages-in-outlook-that-warn-justify-or-block-emails-being-sent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EImplement%20pop-up%20messages%20in%20Outlook%20that%20warn%2C%20justify%2C%20or%20block%20emails%20being%20sent%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-customizations%23add-report-an-issue-for-users%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAdd%20%22Report%20an%20Issue%22%20for%20users%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EThe%20f%3C%2FSPAN%3E%3CSPAN%3Eull%20list%20of%20all%20the%20advanced%20policy%20settings%20%3C%2FSPAN%3E%3CSPAN%3Eis%20%3C%2FSPAN%3E%3CSPAN%3Epublished%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-customizations%23available-advanced-settings-for-label-policies%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Ewith%20instructions%20%3C%2FSPAN%3E%3CSPAN%3Efor%20%3C%2FSPAN%3E%3CSPAN%3Ehow%20to%20apply%20them.%20Please%20note%20that%20these%20advanced%20%3C%2FSPAN%3E%3CSPAN%3Esettings%20(both%20for%20policies%20and%20labels)%20are%20supported%20only%20by%20the%20Azure%20Information%20Protection%20%3C%2FSPAN%3E%3CSPAN%3Eu%3C%2FSPAN%3E%3CSPAN%3Enified%20%3C%2FSPAN%3E%3CSPAN%3El%3C%2FSPAN%3E%3CSPAN%3Eabeling%20client%20and%20not%20by%20the%20Office%20365%20built-in%20integration%20with%20%3C%2FSPAN%3E%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22font-weight%3A%20normal%20!msorm%3B%22%3E%3CSTRONG%3E%3CU%3E%3CSPAN%3EImportant%20Note%3A%3C%2FSPAN%3E%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSPAN%3EIf%20you%20use%20Microsoft%20Cloud%20App%20Security%20and%20Azure%20Information%20Protection%20%3C%2FSPAN%3E%3CSPAN%3El%3C%2FSPAN%3E%3CSPAN%3Eabels%20(or%20inten%3C%2FSPAN%3E%3CSPAN%3Ed%3C%2FSPAN%3E%3CSPAN%3Eto%20do%20so%20in%20the%20future)%2C%20verify%20you%20have%20published%20%3C%2FSPAN%3E%3CSPAN%3Eat%20least%3C%2FSPAN%3E%3CSPAN%3E1%20policy%20with%3C%2FSPAN%3E%3CSPAN%3Eminimal%20set%20of%20labels%20even%20if%20this%20%3C%2FSPAN%3E%3CSPAN%3Eis%3C%2FSPAN%3E%3CSPAN%3Escoped%20to%20a%20%3C%2FSPAN%3E%3CSPAN%3Esingle%3C%2FSPAN%3E%3CSPAN%3Euser.%20This%20is%20required%20for%20Microsoft%20Cloud%20App%20Security%20to%20identify%20all%20labels%20in%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3ESecurity%20%26amp%3B%20Compliance%20Center%3C%2FSPAN%3E%3CSPAN%3Eand%20show%20them%20in%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3EMicrosoft%20Cloud%20App%20Security%3C%2FSPAN%3E%3CSPAN%3Eportal%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22font-weight%3A%20normal%20!msorm%3B%22%3E%3CSTRONG%3ELabel%20%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSTRONG%3E%3CSPAN%3Ec%3CSPAN%20style%3D%22font-weight%3A%20normal%20!msorm%3B%22%3Eonditions%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSTRONG%3Eshould%20be%20created%20manually%20under%20each%20%3CSPAN%3Eunified%20%3C%2FSPAN%3E%3CSPAN%3Elabel%20%3C%2FSPAN%3E%3CSPAN%3Eas%3C%2FSPAN%3Ethey%20are%20far%20more%20flexible%3CSPAN%3Ethan%20their%20Azure%20portal%20counterparts%3C%2FSPAN%3E.%20By%20the%20way%20%E2%80%93%20If%20you%20already%20have%20custom%20sensitive%20information%20types%20that%20w%3CSPAN%3Eere%3C%2FSPAN%3Ebuilt%20to%20use%20with%20Office%20365%20DLP%20or%20Microsoft%20Cloud%20App%20Security%20you%20can%20apply%20them%20as-is%20to%20a%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Ewith%20simple%20configuration.%20Read%20our%20official%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FOffice365%2FSecurityCompliance%2Fapply-sensitivity-label-automatically%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edocumentation%3C%2FA%3Eon%20how%20to%20create%20automated%20and%20recommend%20rules%20for%20%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22font-weight%3A%20normal%20!msorm%3B%22%3E%3CSTRONG%3E%3CSPAN%3ELabel%20translations%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FSPAN%3E%3CSPAN%3Ecan%20be%20%3C%2FSPAN%3E%3CSPAN%3Econfigured%3C%2FSPAN%3E%3CSPAN%3E%2C%3C%2FSPAN%3E%3CSPAN%3Eonce%20labels%20are%20%3C%2FSPAN%3E%3CSPAN%3Emigrated%2C%20using%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fpowershell%2Fexchange%2Foffice-365-scc%2Fconnect-to-scc-powershell%2Fconnect-to-scc-powershell%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESecurity%20%26amp%3B%20Compliance%20PowerShell%20module%3C%2FA%3Eusing%20the%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fpolicy-and-compliance%2Fset-label%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eset-label%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Ecmdlet%3C%2FSPAN%3E%3CSPAN%3Ewith%20the%20-LocaleSettings%20parameter.%20Please%20note%20that%20%3C%2FSPAN%3E%3CSPAN%3Etranslations%20are%20supported%20only%20for%20labels%20and%20with%20the%20Azure%20Information%20Protection%20Unified%20Labeling%20client.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPhase%203%20%E2%80%93%20Client%20deployment%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThe%20last%20part%20is%20to%20verify%20the%20end%20users%20will%20be%20able%20to%20get%20the%20%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3Epolicy%20and%20labels.%20For%20this%20they%20need%20a%20supported%20client%20that%20know%3CSPAN%3Es%3C%2FSPAN%3Eto%20connect%20to%20the%20Security%20%3CSPAN%3E%26amp%3B%20%3C%2FSPAN%3ECompliance%20backend%20and%20pull%20the%20%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3Epolicy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20Windows%20%3CSPAN%3EOffice%20365%20%3C%2FSPAN%3Eand%20%3CSPAN%3Eperpetual%20versions%20of%20Office%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3Bclients%20%3C%2FSPAN%3E(2010%2C%202013%2C%202016%2C%202019)%2C%20install%20the%20Azure%20Information%20Protection%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20client%20which%20can%20be%20downloaded%20from%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Faipclient%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Faipclient%3C%2FA%3E(verify%20you%20download%20the%20AzInfoProtection_ul.exe%20file.%20I%3CSPAN%3Ef%3C%2FSPAN%3Eyou%20currently%20have%20Azure%20Information%20Protection%20client%20%3CSPAN%3E(classic)%20%3C%2FSPAN%3Edeployed%2C%20installing%20the%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20client%20will%20perform%20an%20in-place%20upgrade.%3CSPAN%3E%20In%20the%20future%2C%20%3C%2FSPAN%3E%3CSPAN%3Eunified%20label%3C%2FSPAN%3E%3CSPAN%3Eing%20will%20be%20%3C%2FSPAN%3E%3CSPAN%3Ebuilt%3C%2FSPAN%3E%3CSPAN%3Ein%20%3C%2FSPAN%3E%3CSPAN%3Eto%20%3C%2FSPAN%3E%3CSPAN%3EOffice%20365%20for%20Windows.%20Once%20this%20%3C%2FSPAN%3E%3CSPAN%3Eis%3C%2FSPAN%3E%3CSPAN%3Ereleased%2C%20a%20separate%20announcement%20and%20documentation%20will%20be%20published%20to%20plan%20the%20move%20from%20add-in%20based%20labeling%20to%20built-in%3C%2FSPAN%3E%3CSPAN%3EOffice%20capabilities%3C%2FSPAN%3E%3CSPAN%3E.%20Please%20note%20that%20for%20end%3C%2FSPAN%3E%3CSPAN%3Eusers%20this%20transition%20will%20be%20seamless%2C%20%3C%2FSPAN%3E%3CSPAN%3Eso%3C%2FSPAN%3E%3CSPAN%3Ethere%20is%20no%20%3C%2FSPAN%3E%3CSPAN%3Eneed%20to%20delay%20deployment%20of%20the%20unified%20labeling%20client%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20Mac%3CSPAN%3EOS%3C%2FSPAN%3E%2C%20iO%3CSPAN%3ES%2C%3C%2FSPAN%3EAndroid%20(and%20additional%20applications%20that%20is%20mentioned%20as%20%E2%80%9CComing%20Soon%E2%80%9D%20earlier%20in%20this%20blog)%3CSPAN%3E%2C%3C%2FSPAN%3E%3CSPAN%3En%3C%2FSPAN%3Eo%20action%20is%20needed%20be%3CSPAN%3Eyond%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FOffice365%2FSecurityCompliance%2Fsensitivity-labels%23what-label-policies-can-do%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Epublishing%20the%20%3CSPAN%3Eunified%20labeling%3C%2FSPAN%3Epolicy%3C%2FA%3E.%20These%20clients%20%3CSPAN%3Enatively%20%3C%2FSPAN%3Esupport%20%3CSPAN%3Eunified%20label%3C%2FSPAN%3Eing%20and%20will%20enable%20the%20Sensitivity%20button%20automatically%20when%20policy%20is%20published.%20Click%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Farticle%2Fapply-sensitivity-labels-to-your-documents-and-email-within-office-2f96e7cd-d5a4-403b-8bd7-4cc636bae0f9%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3Eto%20read%20how%20to%20apply%20sensitivity%20label%20in%20each%20platform%20that%20%3CSPAN%3Esupports%20%3C%2FSPAN%3Ebuilt-in%20%3CSPAN%3Elab%3C%2FSPAN%3E%3CSPAN%3Eeling%3C%2FSPAN%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESee%20the%20following%20screenshots%20(Fig.%20%3CSPAN%3E7%3C%2FSPAN%3E)%20that%20describe%20the%20experience%20across%20multiple%20platforms.%3CSPAN%3E%20You%20can%20also%20see%20this%20in%20the%20latest%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Farticle%2Fapply-sensitivity-labels-to-your-documents-and-email-within-office-2f96e7cd-d5a4-403b-8bd7-4cc636bae0f9%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eofficial%20documentation%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%3C%2FSPAN%3E%3CSPAN%3Ef%20%3C%2FSPAN%3E%3CSPAN%3Eyou%20published%20your%20labels%20and%20the%20clients%3C%2FSPAN%3E%3CSPAN%3Ethat%3C%2FSPAN%3E%3CSPAN%3Ehave%20built-in%20%3C%2FSPAN%3E%3CSPAN%3Esupport%20do%3C%2FSPAN%3E%3CSPAN%3Eno%3C%2FSPAN%3E%3CSPAN%3Et%20show%20the%20%E2%80%9CSensitivity%E2%80%9D%20button%2C%20review%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Farticle%2Fknown-issues-with-sensitivity-labels-in-office-b169d687-2bbd-4e21-a440-7da1b2743edc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Etroubleshooting%20guide%3C%2FA%3Ethat%20covers%20this%20topic.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH6%20style%3D%22text-align%3A%20center%3B%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%20id%3D%22toc-hId--1418763561%22%3EFig%20%3CSPAN%3E7%3C%2FSPAN%3E.%20Consistent%20user%20experience%20for%20applying%20Sensitivity%20labels%20across%20different%20platforms.%3C%2FH6%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125570i404FD2785A704E9C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_7.png%22%20title%3D%22clipboard_image_7.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThe%20%3C%2FSPAN%3E%3CSPAN%3Emain%20differences%20for%20end%20users%20who%20use%20the%20%3C%2FSPAN%3E%3CSPAN%3Eclassic%20client%20for%20%3C%2FSPAN%3E%3CSPAN%3EAzure%20Information%20Protection%20today%20and%20move%20to%20use%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3Eunified%20label%3C%2FSPAN%3E%3CSPAN%3Eing%20client%20is%20the%20new%20%E2%80%9CSensitivity%E2%80%9D%20button%20that%20replaces%20the%20%E2%80%9CProtect%E2%80%9D%20button%3C%2FSPAN%3E%3CSPAN%3E(Fig%3C%2FSPAN%3E%3CSPAN%3E.%20%3C%2FSPAN%3E%3CSPAN%3E8%3C%2FSPAN%3E%3CSPAN%3E)%3C%2FSPAN%3E%3CSPAN%3E.%20The%20functionality%20and%20experience%20to%20apply%20labels%20remains%20the%20same%20with%20the%20vertical%20bar%20across%20all%20platforms%20and%20%3C%2FSPAN%3E%3CSPAN%3Ewith%20the%20horizontal%20bar%20which%20is%20exclusive%20to%20the%20Azure%20Information%20Protection%20%3C%2FSPAN%3E%3CSPAN%3Eunified%20label%3C%2FSPAN%3E%3CSPAN%3Eing%20client%20in%20Windows.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH6%20style%3D%22text-align%3A%20center%3B%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%20id%3D%22toc-hId-324046774%22%3E%3CSPAN%3EFig.%20%3C%2FSPAN%3E%3CSPAN%3E8%3C%2FSPAN%3E%3CSPAN%3E%E2%80%93%20End%20user%3C%2FSPAN%3E%3CSPAN%3Es%3C%2FSPAN%3E%3CSPAN%3Echanges%20when%20upgrading%20from%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20c%3C%2FSPAN%3E%3CSPAN%3Elassic%20%3C%2FSPAN%3E%3CSPAN%3Eclient%20%3C%2FSPAN%3E%3CSPAN%3Eto%20%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3Eunified%20label%3C%2FSPAN%3E%3CSPAN%3Eing%20client%3C%2FSPAN%3E%3C%2FH6%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125571i868B5823DAF0CEEA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22clipboard_image_8.png%22%20title%3D%22clipboard_image_8.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EThat%E2%80%99s%20it!%3C%2FSTRONG%3E%3CSPAN%3EO%3C%2FSPAN%3E%3CSPAN%3Ence%20you%20%3C%2FSPAN%3E%3CSPAN%3Ehave%20%3C%2FSPAN%3E%3CSPAN%3Eperformed%20the%20steps%20mentioned%20above%3C%2FSPAN%3E%3CSPAN%3E%2C%3C%2FSPAN%3E%3CSPAN%3Eyou%20have%20completed%20your%20migration%20to%20%3C%2FSPAN%3E%3CSPAN%3Eu%3C%2FSPAN%3E%3CSPAN%3Enif%3C%2FSPAN%3E%3CSPAN%3Eied%20labeling%3C%2FSPAN%3E%3CSPAN%3Eand%3C%2FSPAN%3E%3CSPAN%3Eare%20%3C%2FSPAN%3Enow%20ready%20for%20the%20future%20and%20the%20exciting%20updates%20that%20will%20be%20available%20soon%20across%20the%20Microsoft%20365%20platform!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EYou%20can%20manage%20labels%20in%20one%20place%20which%20is%20the%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2Ftagslibrary%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eunified%20labeling%20console%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Ein%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fprotection.office.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20365%20Security%20%26amp%3B%20Compliance%20Center%3C%2FA%3E.%20%3C%2FSPAN%3E%3CSPAN%3EThe%20only%20reason%20yo%3C%2FSPAN%3E%3CSPAN%3Eu%20may%3C%2FSPAN%3E%3CSPAN%3Estill%3C%2FSPAN%3E%3CSPAN%3Eneed%3C%2FSPAN%3E%3CSPAN%3Eto%20use%20the%20%3C%2FSPAN%3E%3CSPAN%3EAzure%20Portal%20%3C%2FSPAN%3E%3CSPAN%3Efor%20Azure%20Information%20Protection%2C%20%3C%2FSPAN%3E%3CSPAN%3Eis%20to%20%3C%2FSPAN%3E%3CSPAN%3Emanage%3C%2FSPAN%3E%3CSPAN%3Ethe%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%23blade%2FMicrosoft_Azure_InformationProtection%2FDataClassGroupEditBlade%2FscannerNodesBlade%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20scanner%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3Eand%20to%20monitor%20label%20a%3C%2FSPAN%3E%3CSPAN%3Ectivities%20using%20%3C%2FSPAN%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%23blade%2FMicrosoft_Azure_InformationProtection%2FDataClassGroupEditBlade%2FusageReportBlade%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20analytics%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIf%20you%20have%20questions%20%3C%2FSPAN%3E%3CSPAN%3Eor%20want%20to%20follow%20up%20on%20the%20latest%20updates%20from%20Microsoft%20Information%20Protection%2C%20please%20review%20these%20resources%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Faipdag%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20Deployment%20Acceleration%20Guide%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Faipdocs%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20official%20documentation%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Faskipteam%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Information%20Protection%20Yammer%20channel%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-783185%22%20slang%3D%22en-US%22%3E%3CP%3EUnified%20labeling%20is%20here%20and%20it%20is%20the%20next%20step%20in%20the%20Microsoft%20Information%20Protection%20story%2C%20read%20to%20understand%20why.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-783185%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAIP%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Information%20Protection%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Information%20Protection%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMIP%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUnified%20Labeling%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789649%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789649%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169989%22%20target%3D%22_blank%22%3E%40Nir%20Hendler%3C%2FA%3EIf%20I%20migrate%20my%20AIP%20labels%20to%20UL%2C%20and%20afterwards%20I%20apply%20advanced%20settings%20for%20the%20copied%20UL%20labels%20%2F%20Sensitivity%20labels%20using%20the%20PS%20SCC%20Module...%20will%20the%20labels%20keep%20the%20advanced%20configuration%20(e.g.%20colour%20settings)%20in%20UL%20even%20if%20I%20copy%20once%20again%20the%20labels%20from%20AIP%20to%20UL%20(e.g.%20because%20I%20create%20%2F%20change%20a%20label%20in%20AIP)%3F%20Or%20will%20it%20%22overwrite%22%20the%20advanced%20settings%20on%20the%20(existing)%20copied%20labels%20in%20the%20Security%20%26amp%3B%20Compliance%20Center%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%2C%3C%2FP%3E%3CP%3EMartin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789693%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789693%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299339%22%20target%3D%22_blank%22%3E%40MartinZoller%3C%2FA%3E%26nbsp%3B-%20The%20enablement%20of%20Unified%20Labeling%20from%20Azure%20Information%20Protection%20blade%20is%20a%20one%20time%20action.%20The%20backend%20actions%20are%20described%20in%20the%20blog.%20From%20that%20point%2C%20both%20services%20(AIP%20and%20SCC)%20use%20the%20same%20label%20database%20and%20therefor%2C%20there%20is%20no%20option%20to%20%22copy%20labels%20again%22%20as%20they%20are%20connected.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20Unified%20Labeling%20you%20need%20to%20distinguish%20between%26nbsp%3B%3CSTRONG%3EPolicy%20advanced%20settings%3C%2FSTRONG%3Eto%26nbsp%3B%3CSTRONG%3ELabel%20advanced%20settings%3C%2FSTRONG%3Ewhich%20have%20different%20concept%20then%20how%20they%20are%20configured%20in%20AIP%20labels.%20therefor%2C%20if%20a%20new%20label%20is%20created%20in%20AIP%2C%20you%20should%20add%20it's%20relevant%20advanced%20configuration%20using%20SCC%20PS.%3C%2FP%3E%0A%3CP%3EWe%20do%20recommend%20to%20manage%20your%20labels%20at%20one%20place%20after%20the%20migration%2C%20beside%20the%20scanner%20use%20case%2C%20there%20is%20no%20other%20reason%20to%20use%20both%20portals%20for%20label%20and%20policy%20management.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789843%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789843%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20were%20the%20most%20highly%20used%20platforms%20left%20till%20last%3F%20How%20soon%20can%20we%20expect%20it%20to%20be%20available%20in%20office%20and%20SharePoint%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789869%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789869%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F237846%22%20target%3D%22_blank%22%3E%40Sam%20Gray%3C%2FA%3E%26nbsp%3BBoth%20platforms%20are%20expected%20to%20be%20available%20to%20the%20public%20by%20the%20end%20of%20CY2019.%20You%20can%20get%20more%20official%20updates%20in%20the%20Microsoft%20365%20roadmap%20page%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3FSilentAuth%3D1%2526filters%3D%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3FSilentAuth%3D1%2526filters%3D%3C%2FA%3E%3C%2FP%3E%0A%3CP%3ESharePoint%20integration%20is%20already%20in%20Private%20Preview.%3C%2FP%3E%0A%3CP%3EPlease%20note%20that%20these%20time%20frames%20(and%20ones%20the%20roadmap%20mention)%20can%20be%20considered%20only%20as%20estimations.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789940%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789940%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20idea%20when%20this%20will%20roll%20out%20for%20GCC%3F%26nbsp%3B%20We%20were%20given%20the%20impression%20this%20was%20available%20back%20in%20March%20and%20had%20actually%20activated%20Unified%20Labeling%20for%20our%20GCC%20tenant.%26nbsp%3B%20We%20had%20successfully%20migrated%20our%20labels%20from%20AIP%20to%20the%20Security%20%26amp%3B%20Compliance%20center%20and%20were%20testing%20to%20see%20how%20we%20wanted%20to%20fully%20implement%20a%20labeling%20strategy%20when%20Unified%20Labeling%20was%20deactivated%20on%20our%20tenant%20without%20warning.%26nbsp%3B%20This%20led%20to%20multiple%20Premier%20Support%20tickets%20to%20finally%20be%20told%20yesterday%20that%20it's%20not%20available%20in%20GCC.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20checked%20the%20Microsoft%20365%20roadmap%20page%20but%20did%20not%20see%20anything%20related%20to%20Unified%20Labeling%20for%20GCC.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789943%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789943%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F354559%22%20target%3D%22_blank%22%3E%40Generik%3C%2FA%3E%26nbsp%3B-%20This%20is%20a%20roadmap%20item%20with%20no%20ETA%20that%20can%20be%20shared%20at%20the%20moment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-795359%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-795359%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169989%22%20target%3D%22_blank%22%3E%40Nir%20Hendler%3C%2FA%3E%2C%20t%3CFONT%3Ehank%20you%20for%20the%20comprehensive%20information%20regarding%20the%20Unified%20Labeling%20migration.%20Very%20helpful.%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-806610%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-806610%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20looks%20like%20this%20work%20is%20really%20comming%20together.%20What%20I%20am%20missing%20as%20a%20big%20part%20of%20working%20with%20the%20documents%20and%20data%20is%20that%20the%20labels%20have%20to%20be%20able%20to%20Surface%20in%20SharePoint.%20I%20need%20to%20work%20with%20AIP%20labels%20as%20a%20metadatacolumn%20because%20I%20can't%20make%20everyone%20an%20admin.%20We%20need%20to%20be%20able%20to%20work%20with%20the%20labels%20in%20SharePoint%20(and%20OneDrive)%20to%20be%20able%20to%20sort%2C%20filter%2C%20set%20column%20formatting%2C%20Flow%20etc.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-823684%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-823684%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20AIP%20be%20removed%20from%20the%20EMS%20license%20then%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824478%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824478%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F31572%22%20target%3D%22_blank%22%3E%40Mike%20Crowley%3C%2FA%3E%26nbsp%3BNo%20there%20are%20currently%20no%20planned%20changes%20to%20Azure%20Information%20Protection%20licensing%2C%20meaning%20Azure%20Information%20Protection%20will%20continue%20to%20be%20part%20of%20EMS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-825614%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-825614%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F215%22%20target%3D%22_blank%22%3E%40Adam%20Jung%3C%2FA%3ECan%20you%20expand%20on%20that%3F%20Is%20it%20just%20that%20you%20don't%20have%20%22anything%20to%20share%20at%20this%20time%22%20or%20that%20there%20is%20a%20continued%20reason%20a%20customer%20would%20want%20to%20buy%20AIP%20vs%20the%20unified%20labels%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826718%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826718%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F31572%22%20target%3D%22_blank%22%3E%40Mike%20Crowley%3C%2FA%3E%26nbsp%3Bwe%20had%20a%20previous%20FAQ%20similar%20to%20this%20and%20pasted%20below.%20In%20short%2C%20you%20still%20need%20AIP%20licenses%20if%20you%20want%20to%20use%20the%20AIP%20client%20for%20downlevel%20versions%20of%20Office%2C%20to%20use%20the%20AIP%20scanner%20for%20on-premises%20files%2C%20etc.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CBUTTON%20class%3D%22toggler%20open%22%20type%3D%22button%22%20aria-expanded%3D%22true%22%20aria-controls%3D%2266aa35a4%22%3EWith%20the%20unified%20label%20management%20experience%20in%20the%20Security%20%26amp%3B%20Compliance%20Center%2C%20do%20I%20need%20both%20Azure%20Information%20Protection%20P1%2FP2%20and%20Office%20365%20E3%2FE5%20licenses%3F%3C%2FBUTTON%3E%3C%2FP%3E%0A%3CDIV%20id%3D%2266aa35a4%22%20class%3D%22toggled%20open%22%3E%0A%3CP%3EYou%20still%20need%20Azure%20Information%20Protection%20P1%2FP2%20for%20all%20the%20capabilities%20included%20in%20Azure%20Information%20Protection%20before%20the%20unified%20labeling%20experience%20was%20released%20(such%20as%20using%20the%20Azure%20Information%20Protection%20client%2C%20the%20Azure%20Information%20Protection%20scanner%2C%20etc.)To%20be%20able%20to%20configure%20sensitivity%20labels%20in%20the%20Security%20%26amp%3B%20Compliance%20center%2C%20you%20need%20either%20Azure%20Information%20Protection%20P1%2FP2%20licenses%20OR%20Office%20365%20E3%2FE5%20licenses%20(you%20don%E2%80%99t%20need%20both).%20Users%20do%20not%20need%20a%20license%20if%20their%20Azure%20Information%20Protection%20client%20(classic)%20is%20running%20in%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fclient-protection-only-mode%23limitations-for-protection-only-mode%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eprotection-only%20mode%3C%2FA%3E.%3C%2FP%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826781%22%20slang%3D%22en-US%22%3ERe%3A%20Understanding%20Unified%20Labeling%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826781%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F215%22%20target%3D%22_blank%22%3E%40Adam%20Jung%3C%2FA%3E%2C%20I%20had%20seen%20that%20before%2C%20but%20it%20seems%20like%20those%20are%20just%20%22temporary%20problems%22%20until%20everything%20is%20updated%20to%20support%20these%20new%20unified%20labels.%20Anyway%2C%20I'm%20not%20looking%20to%20split%20hairs%20here%2C%20so%20I'll%20just%20wait%20for%20future%20announcements.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

TL; DR 

Unified labeling is here and it is the next step in the Microsoft Information Protection story. Each new Microsoft product and service that utilizes classification and protection capabilities (and 3rd party ones using MIP SDK capabilities) will require unified labeling. 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.

The primary migration plan is to migrate labels from the Azure Information Protection blade in the Azure portal to the  Office 365 Security & Compliance Center, re-create your label policies, conditions and deploy the latest unified labeling client as a new installation or in-place upgrade to the Azure Information Protection client (classic). 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.

Note: Unified labeling support is only available for commercial cloud tenants.

clipboard_image_0.png

 

Unified labeling Migration

Back 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. 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.  At that point, Azure Information Protection was the only product that supported labeling of sensitive content as part of Microsoft portfolio.

 

Based 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. Because the Office 365 suite 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 3rd party products, a unified approach has been agreed upon and initiated these changes:

  1. Microsoft introduced 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.
  2. 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).
  3. 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 platformSensitivity labels.

Performing these changes caused the creation of a new label management tab, in addition to a new client that is based on the Microsoft Information Protection SDK. Unlocking the availability of Sensitivity labels across the complete Microsoft 365 platform.

 

At the time of writing this blog (August 2019), there are 2 main label management portals which are supported by different products:

  1. Azure Information Protection blade in the Azure portal - Supported by:
    1. The Azure Information Protection client (classic)
    2. The Azure Information Protection scanner
    3. Microsoft Cloud App Security
  2. Unified labeling console in Office 365 Security & Compliance Center – Supported by:
    1. The Azure Information Protection unified labeling client
    2. Microsoft Cloud App Security
    3. Office apps for MacOS
    4. Office apps for Android
    5. Office apps for iOS
    6. Microsoft Information Protection SDK and applications based on it (For example: Adobe Acrobat)
    7. Coming Soon:
      1. SharePoint Online
      2. Office for the web
      3. Built-in labeling in Office for Windows (no need for an add-in)
      4. Outlook web app
      5. Outlook Mobile (iOS and Android)
      6. The Azure Information Protection scanner

As you can see and understand, moving forward, every app and service that implement labeling capabilities in Microsoft will be using unified labeling exclusively. In addition to that, the Azure Information Protection client (classic) and portals are still here but not for long (a separate announcement will be published with specific plans).

Lastly, unified labeling supports advanced capabilities that aren’t available when Azure Information Protection labels are in use and are now available as part of the native integration with the Microsoft 365 platform. Some of these capabilities are:

  1. Advanced label automation with the same logic as used by Office 365 DLP with sensitive information types, custom and pre-defined.
  2. Flexible label polices which now can scope the same label to multiple policies.
  3. Unified experience with applying sensitivity labels across Office 365 apps and services.

There is no risk for end users and production environment in migrating to unified labeling today, the migration process copies labels from Azure Information Protection backend to Security and Compliance backend but not its policies. So as long you didn’t publish a unified labeling policy or didn’t deployed an application that support unified labeling, nothing happens for end users!

 

So, what now? It’s time to migrate to unified labeling!

 

Are you a new customer who is just starting your Information Protection journey? Start with unified labeling and create your policies and labels in the Office 365 Security & Compliance Center (Or Microsoft 365 Compliance / Microsoft 365 Security portals in case you are a Microsoft 365 customer). New tenants are already enabled with unified labeling, so no action is required from your side. If no labels are already created and you wish to leverage Azure Information Protection default labels, go to the Azure Information Protection blade in the Azure portal and generate the default labels (Fig. 1). In addition, verify that your tenant is already migrated to unified labeling, if not, go to the unified labeling blade and activate the migration (Fig. 2).

 

Fig 1. Generate default labels

clipboard_image_1.png

Fig 2. Unified labeling migration activated

clipboard_image_2.png

Are you an existing Azure Information Protection customer who wish to migrate to unified labeling? Here are the suggested steps you should perform to plan and execute the migration:

 

Phase 1 – Planning

Unified labels support most functionalities that are available in Azure Information Protection labels, some functionalists are not available and some are configured differently when managed from the Security & Compliance Center. Please review the following:

  1. Label settings that are not supported in the admin centers and learn how they are manageable.
  2. Client differences between the classic client for Azure Information Protection, and the unified labeling client.
  3. Features not planned to be in the Azure Information Protection unified labeling client. As a clarification please note that although custom permissions are not supported in the unified labeling client as a standalone action with the Office add-in, it is supported as a label that is configured with User Defined Permissions action.

If one of the documented differences impact your end users behavior, please reflect this accordingly in your end user communication before deploying the latest client and publishing the unified labeling policy.

 

As of today (August 2019), the Azure Information Protection scanner supports only labels from Azure Information Protection blade but this is not a blocker as the Azure Information Protection label metadata is identical to unified labels.

 

Same applied for Azure Information Protection analytics (Preview) which is available with full feature set in Azure Information Protection blade but do cover analytics from the unified labeling client as well.

 

Phase 2 – Service migration

After you have reviewed the 1st phase, it’s time to migrate your labels to the Security & Compliance Center. It is important to mention that Migrate” doesn’t mean you need to move away from managing labels and policies in the Azure Information Protection blade and the Azure Information Protection client (classic). This migration can happen in the background and works side by side with no additional configuration.

 

What happens when you migrate your labels to unified labels?

 

Before you activate the migration, both Azure Information Protection backend and unified labeling backend are 2 separate services which work independently (Fig. 3). Once you activate the unified labeling migration, the labels are copied from the Azure Information Protection backend to the unified labeling backend and both services are using the same backend to store labels (Fig. 4). This means that every change you perform to any label at any portal will be changed also in the other portal.

 

Fig 3. Service architecture pre-unified labeling migration

clipboard_image_3.png

Fig 4. Service architecture post unified labeling migration

clipboard_image_4.png

After you activate the unified labeling migration, your labels are expected to be visible in both the Azure Information Protection blade and unified labeling page in the Security & Compliance Center (Fig 5).

 

Fig 5. Azure Information Protection and unified labeling in the Microsoft 365 compliance center post migration UI.

clipboard_image_5.png

Moving forward you can manage your labels at one place. After the migration, when you edit a migrated label in the Azure Information Protection blade, the same change is automatically reflected in the admin centers. However, when you edit a migrated label in the Security & Compliance Center, you must return to the Azure Information Protection blade, go to Azure Information Protection - Unified labeling blade, and select Publish. This additional action is needed for the Azure Information Protection clients (classic) to pick up the label changes. Once you are fully migrated to the unified labeling client, you no longer need to do this step, so migrating quickly helps to reduce this administrative overhead.

 

As you may notice, label configuration in the Security & Compliance Center doesn’t include some of the advanced settings that were able to be configured using Azure Information Protection labels. These configurations are now applied to the label after its initial creation / migration using the Security and Compliance PowerShell module. Here are few examples of these configurations:

A full list of all the advanced label settings is published here with instructions how to apply them. Please note that these label advanced settings are supported only by the Azure Information Protection unified labeling client on Windows and not by the Office 365 built-in integration with unified labeling.

 

What doesn’t migrate and need to be created separately?

  • Label policies
  • Label conditions
  • Label translations

Why? As mentioned earlier in this blog, policies and conditions are more flexible and have additional advanced settings.  Thus, they cannot be directly translated across the services.

 

You should create your Label policies manually in the Security & Compliance Center, so they reflect your current settings as they are configured in the Azure portal. To do so, go to Label Policies console and create a new policy by clicking the “Publish labels” button (Fig 6). Follow the configuration steps to verify these are configured properly.

 

Fig 6. Label policies page in the Security & Compliance Center

clipboard_image_6.png

As an Azure Information Protection admin, you probably noticed that some policy configurations are not available when you configure your policy in the Security & Compliance Center. These configurations should be applied to the policy you created in the Security & Compliance Center after its initial creation and using the Security & Compliance PowerShell module. Here are few examples for such configurations:

The full list of all the advanced policy settings is published here with instructions for how to apply them. Please note that these advanced settings (both for policies and labels) are supported only by the Azure Information Protection unified labeling client and not by the Office 365 built-in integration with unified labeling.

 

Important Note: If you use Microsoft Cloud App Security and Azure Information Protection labels (or intend to do so in the future), verify you have published at least 1 policy with minimal set of labels even if this is scoped to a single user. This is required for Microsoft Cloud App Security to identify all labels in the Security & Compliance Center and show them in the Microsoft Cloud App Security portal.

 

Label conditions should be created manually under each unified label as they are far more flexible than their Azure portal counterparts. By the way – If you already have custom sensitive information types that were built to use with Office 365 DLP or Microsoft Cloud App Security you can apply them as-is to a unified label with simple configuration. Read our official documentation on how to create automated and recommend rules for unified labeling.

 

Label translations can be configured, once labels are migrated, using Security & Compliance PowerShell module using the set-label cmdlet with the -LocaleSettings parameter. Please note that translations are supported only for labels and with the Azure Information Protection Unified Labeling client.

 

Phase 3 – Client deployment

The last part is to verify the end users will be able to get the unified labeling policy and labels. For this they need a supported client that knows to connect to the Security & Compliance backend and pull the unified labeling policy.

 

For Windows Office 365 and perpetual versions of Office clients (2010, 2013, 2016, 2019), install the Azure Information Protection unified labeling client which can be downloaded from http://aka.ms/aipclient (verify you download the AzInfoProtection_ul.exe file. If you currently have Azure Information Protection client (classic) deployed, installing the unified labeling client will perform an in-place upgrade. In the future, unified labeling will be built in to Office 365 for Windows. Once this is released, a separate announcement and documentation will be published to plan the move from add-in based labeling to built-in Office capabilities. Please note that for end users this transition will be seamless, so there is no need to delay deployment of the unified labeling client.

 

For MacOS, iOS, Android (and additional applications that is mentioned as “Coming Soon” earlier in this blog), no action is needed beyond publishing the unified labeling policy. These clients natively support unified labeling and will enable the Sensitivity button automatically when policy is published. Click here to read how to apply sensitivity label in each platform that supports built-in labeling.

 

See the following screenshots (Fig. 7) that describe the experience across multiple platforms. You can also see this in the latest official documentation.

 

If you published your labels and the clients that have built-in support do not show the “Sensitivity” button, review the troubleshooting guide that covers this topic.

 

Fig 7. Consistent user experience for applying Sensitivity labels across different platforms.

clipboard_image_7.png

The main differences for end users who use the classic client for Azure Information Protection today and move to use the unified labeling client is the new “Sensitivity” button that replaces the “Protect” button (Fig. 8). The functionality and experience to apply labels remains the same with the vertical bar across all platforms and with the horizontal bar which is exclusive to the Azure Information Protection unified labeling client in Windows.

 

Fig. 8 – End users changes when upgrading from the classic client to the unified labeling client

clipboard_image_8.png

That’s it! Once you have performed the steps mentioned above, you have completed your migration to unified labeling and are now ready for the future and the exciting updates that will be available soon across the Microsoft 365 platform!

 

You can manage labels in one place which is the unified labeling console in Office 365 Security & Compliance Center. The only reason you may still need to use the Azure Portal for Azure Information Protection, is to manage the Azure Information Protection scanner and to monitor label activities using Azure Information Protection analytics.

 

If you have questions or want to follow up on the latest updates from Microsoft Information Protection, please review these resources:

17 Comments
Super Contributor

Office Online is now just Office, or on the web :)

Valued Contributor

Hi @Nir Hendler ,

what do I do with the Default MRM Policy in the EAC once we've migrated to the new Unified Labeling system?

We've never used the classic exchange retention policies. Do I just delete the policy in the EAC? Does that get rid of the Retention button in Outlook as well?

Microsoft

@Ivan Unger - Everything that was mentioned in this blog is not related to "Retention labels" and doesn't affect them. This refers to "Sensitivity" labels only,

Valued Contributor

Am I understanding this correctly, that we (the user) are not supposed to label incoming emails, but only outgoing messages?

And therefore there is no way to retroactively apply a sensitivity label, like "personal" to a sent message?

Occasional Contributor

@Nir HendlerIf I migrate my AIP labels to UL, and afterwards I apply advanced settings for the copied UL labels / Sensitivity labels using the PS SCC Module... will the labels keep the advanced configuration (e.g. colour settings) in UL even if I copy once again the labels from AIP to UL (e.g. because I create / change a label in AIP)? Or will it "overwrite" the advanced settings on the (existing) copied labels in the Security & Compliance Center?

 

Thanks in advance,

Martin

Microsoft

@MartinZoller - The enablement of Unified Labeling from Azure Information Protection blade is a one time action. The backend actions are described in the blog. From that point, both services (AIP and SCC) use the same label database and therefor, there is no option to "copy labels again" as they are connected. 

In Unified Labeling you need to distinguish between Policy advanced settings to Label advanced settings which have different concept then how they are configured in AIP labels. therefor, if a new label is created in AIP, you should add it's relevant advanced configuration using SCC PS.

We do recommend to manage your labels at one place after the migration, beside the scanner use case, there is no other reason to use both portals for label and policy management.

Senior Member

Why were the most highly used platforms left till last? How soon can we expect it to be available in office and SharePoint?

Microsoft

@Sam Gray Both platforms are expected to be available to the public by the end of CY2019. You can get more official updates in the Microsoft 365 roadmap page: https://www.microsoft.com/en-us/microsoft-365/roadmap?SilentAuth=1%26filters=

SharePoint integration is already in Private Preview.

Please note that these time frames (and ones the roadmap mention) can be considered only as estimations.

Regular Visitor

Any idea when this will roll out for GCC?  We were given the impression this was available back in March and had actually activated Unified Labeling for our GCC tenant.  We had successfully migrated our labels from AIP to the Security & Compliance center and were testing to see how we wanted to fully implement a labeling strategy when Unified Labeling was deactivated on our tenant without warning.  This led to multiple Premier Support tickets to finally be told yesterday that it's not available in GCC.

 

I checked the Microsoft 365 roadmap page but did not see anything related to Unified Labeling for GCC.

Microsoft

@Generik - This is a roadmap item with no ETA that can be shared at the moment.

Frequent Contributor

@Nir Hendler, thank you for the comprehensive information regarding the Unified Labeling migration. Very helpful. 

Regular Visitor

It looks like this work is really comming together. What I am missing as a big part of working with the documents and data is that the labels have to be able to Surface in SharePoint. I need to work with AIP labels as a metadatacolumn because I can't make everyone an admin. We need to be able to work with the labels in SharePoint (and OneDrive) to be able to sort, filter, set column formatting, Flow etc. 

Occasional Contributor

Will AIP be removed from the EMS license then?

Microsoft

@Mike Crowley No there are currently no planned changes to Azure Information Protection licensing, meaning Azure Information Protection will continue to be part of EMS.

Occasional Contributor

@Adam JungCan you expand on that? Is it just that you don't have "anything to share at this time" or that there is a continued reason a customer would want to buy AIP vs the unified labels?

Microsoft

@Mike Crowley we had a previous FAQ similar to this and pasted below. In short, you still need AIP licenses if you want to use the AIP client for downlevel versions of Office, to use the AIP scanner for on-premises files, etc. 

 

You still need Azure Information Protection P1/P2 for all the capabilities included in Azure Information Protection before the unified labeling experience was released (such as using the Azure Information Protection client, the Azure Information Protection scanner, etc.)To be able to configure sensitivity labels in the Security & Compliance center, you need either Azure Information Protection P1/P2 licenses OR Office 365 E3/E5 licenses (you don’t need both). Users do not need a license if their Azure Information Protection client (classic) is running in protection-only mode.

Occasional Contributor

Thanks @Adam Jung , I had seen that before, but it seems like those are just "temporary problems" until everything is updated to support these new unified labels. Anyway, I'm not looking to split hairs here, so I'll just wait for future announcements.