%3CLINGO-SUB%20id%3D%22lingo-sub-914227%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-914227%22%20slang%3D%22en-US%22%3E%22You%20can%20find%20detailed%20instructions%20to%20deploy%20this%20new%20scanner%20version%20or%20upgrade%20from%20previous%20version%20in%20the%20updated%20Azure%20Information%20Protection%20unified%20labeling%20client%20administrator%20guide.%20See%20the%20new%20section%2C%20Installing%20the%20Azure%20Information%20Protection%20scanner.%22%20As%20of%2010%2F14%2F2019%2C%20the%20client%20admin%20guide%20does%20*not*%20include%20the%20new%20section%20%22Installing%20the%20Azure%20Information%20Protection%20scanner%22%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-install%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%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%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-install%3C%2FA%3E%20Whereas%20I%20did%20find%20updated%20AIP%20Scanner%20documentation%20in%20this%20page%20instead%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Fdeploy-aip-scanner%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%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%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Fdeploy-aip-scanner%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1362701%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1362701%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI'm%20trying%20to%20setup%20this%20scanner%20and%20the%20installation%20went%20smoothly.%3C%2FP%3E%3CP%3EThe%20node%20is%20automatically%20added%20on%20Azure%20Portal%2C%20but%20i%20get%20this%20error%20%3A%3C%2FP%3E%3CP%3EError%20%3A%20Policy%20does%20not%20include%20any%20labeling%20condition%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20click%20the%20%22Scan%20now%22%20Button%20but%20it%20doesnt%20do%20anything.%3C%2FP%3E%3CP%3EOn%20the%20server%20i%20can%20the%20logs%20%3A%26nbsp%3BMSIP.Scanner%20(6736)%20Failed%20to%20validate%20policy%20and%20confiuguration%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20do%20have%20an%20AD%20Account%20synced%20on%20Azure%20AD%2C%20and%20the%20server%20has%20the%20UL%20Client%20and%20has%20internet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3CP%3EThank%20you%2C%3C%2FP%3E%3CP%3EClement%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1364812%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364812%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EError%20%3A%20Policy%20does%20not%20include%20any%20labeling%20condition%26nbsp%3Bcan%20indicate%20one%20of%20two%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E1.%20You%20did%20not%20create%20any%20automatic%20labeling%20condition%20in%20M365%20S%26amp%3BC%20and%20did%20not%20set%20scanner%20to%20match%20all%20known%20Info%20types%20in%20the%20content%20scan%20job%20configuraiton.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E2.%20You%20failed%20to%20acquire%20policy.%20You%20can%20check%20if%20you%20get%26nbsp%3Bmip.policies.sqlite3%20under%20%25localappdata%25%5CMicrosoft%5CMSIP%5Cmip%5CMSIP.Scanner.exe%5Cmip%20of%20the%20scanner%20account.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EPlease%20verify%20you%20completed%20the%20Set-AIPAuthentication%20command%20using%20the%20app%20token%20as%20explained%20at%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-powershell%23how-to-label-files-non-interactively-for-azure-information-protection%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%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%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Finformation-protection%2Frms-client%2Fclientv2-admin-guide-powershell%23how-to-label-files-non-interactively-for-azure-information-protection%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1476345%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1476345%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Denis!%20This%20feedback%20helped%20me%20find%20resolution%20to%20an%20issue%20I%20was%20having.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1591589%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1591589%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20we%20use%20the%20same%20cluster%20feature%20with%20the%20built%20in%20SQL%20Express%20Data%20Base%20architecture%2C%20or%20does%20this%20require%20a%20centralized%20SQL%20Instance%20per%20cluster%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-862552%22%20slang%3D%22en-US%22%3EUnified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-862552%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22text-align%3A%20left%3B%22%3ESince%20its%20release%2C%20the%20Azure%20Information%20Protection%20scanner%20has%20been%20adopted%20by%20many%20different%20types%20of%20customers.%20For%20example%2C%20some%20small%20businesses%20have%20deployed%20single%20scanners%20to%20address%20all%20their%20data%20at%20rest%2C%20others%20deployed%20a%20few%20machines%20in%20different%20locations%20or%20a%20few%20machines%20for%20the%20purpose%20of%20redundancy%2C%20while%20companies%20that%20needed%20to%20deal%20with%20petabytes%20of%20data%20may%20have%20deployed%20dozens%20of%20scanner%20instances%2C%20%E2%80%93%20such%20as%20internally%20at%20Microsoft%2C%20in%20which%20we%20deployed%20more%20than%2040%20scanners.%20Large%20enterprise%20customers%20faced%20increasing%20TCO%2C%20mainly%20driven%20by%20administration%20overhead%20and%20attempts%20to%20distribute%20the%20load%20between%20scanners.%3CBR%20%2F%3EConsistent%20feedback%20also%20came%20from%20customers%20adopting%20our%20unified%20labeling%20platform%20and%20moving%20to%20the%20Azure%20Information%20Protection%20Unified%20Labeling%20client.%20The%20Unified%20Labeling%20client%20allowed%20customers%20to%20use%20more%20flexible%20automatic%20rules%20on%20their%20endpoints%20but%20they%20could%20not%20leverage%20this%20flexibility%20on%20the%20scanner%20that%20its%20core%20functionality%20is%20discovery%20and%20labeling%20based%20on%20automatic%20rules.%20Customers%20also%20needed%20to%20maintain%20their%20labels%20and%20conditions%20in%20both%20Office%20365Security%20and%20Compliance%20Center%20and%20in%20the%20Azure%20portal%20(in%20order%20to%20manage%20conditions%20used%20by%20Azure%20Information%20Protection%20scanner).%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%3CBR%20%2F%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3EUnified%20labeling%20scanner%20is%20here%20to%20address%20scale%20out%20needs!%3C%2FSTRONG%3E%3C%2FFONT%3E%3CBR%20%2F%3EFinally%2C%20AIP%20scanner%20for%20unified%20labeling%20is%20here!%20Now%20you%20can%20completely%20move%20your%20label%20and%20policy%20management%20to%20O365%20Security%20and%20Compliance%20Center%20and%20complete%20the%20migration%20to%20unified%20labeling%20platform.%20This%20allows%20you%20to%20use%20custom%20info%20types%20and%20dictionaries%20on%20the%20AIP%20scanner%2C%20tweak%20built-in%20info%20types%2C%20define%20confidence%20levels%20etc.%3CBR%20%2F%3EThe%20Azure%20Information%20Protection%20scanner%20architecture%20was%20redesigned%20and%20in%20addition%20to%20adoption%20of%20MIP%20SDK%20that%20improves%20the%20performance%20of%20single%20nodes%20you%20can%20now%20group%20your%20scanners%20in%20clusters%20that%20service%20the%20same%20scanner%20profile.%20You%20no%20longer%20need%20to%20try%20to%20distribute%20repositories%20between%20different%20scanner%20nodes%20in%20order%20to%20achieve%20equal%20volumes%20scanned%20by%20every%20node.%20Now%20you%20can%20just%20set%20one%20profile%20and%20put%20all%20the%20repositories%20in%20the%20same%20profile%20(we%20still%20recommend%20separate%20profiles%20per%20geo%20location%20%2F%20data%20center)%20and%20add%20all%20the%20nodes%20to%20this%20profile.%20SQL%20DB%2C%20now%20holds%20core%20role%20as%20the%20orchestrator%20of%20the%20cluster%2C%20will%20take%20care%20of%20equal%20distribution%20of%20load%2C%20detect%20deactivated%20nodes%2C%20taken%2C%20for%20example%20due%20to%20maintenance%20or%20patching%2C%20and%20reallocate%20incomplete%20jobs%20to%20active%20scanner%20nodes.%20Added%20nodes%20to%20the%20profile%20will%20join%20current%20scan%20effort%20and%20get%20instructions%20to%20scan%20the%20next%20bunch%20of%20files.%20This%20provides%20simplified%20management%20and%20elastic%20growth%20and%20can%20help%20you%20reduce%20the%20number%20nodes%20based%20on%20volume%20that%20is%20needed%20to%20scan.%20For%20example%20you%20can%20start%20with%2050%20scanners%20to%20complete%20the%20initial%20scan%20of%20petabytes%20of%20data%20and%20then%20reduce%20the%20cluster%20to%205%20nodes%20to%20scan%20subsequent%20newly%20created%20files%20in%20the%20repository.%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20center%3B%22%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22scanner%20diagram%20v4.jpg%22%20style%3D%22width%3A%20614px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F132533iDB353598D52284DD%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22scanner%20diagram%20v4.jpg%22%20alt%3D%22scanner%20diagram%20v4.jpg%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CEM%3EFigure%201%3A%20Distributed%20scanner%20architecture%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%3CBR%20%2F%3EWe%20also%20incorporated%20a%20few%20more%20new%20features%20and%20fixes%20to%20the%20new%20scanner%20to%20improve%20overall%20management%20and%20administration.%20You%20can%20now%20decide%20that%20all%2C%20new%20unlabeled%20and%20already%20labeled%20files%20in%20a%20specific%20repository%20are%20labeled%20with%20specific%20label.%20For%20example%2C%20you%20can%20decide%20that%20all%20files%20in%20a%20repository%20be%20labeled%20as%20%E2%80%9CConfidential%E2%80%9D%2C%20and%20scanner%20will%20apply%20this%20label%20on%20all%20files%20that%20have%20no%20label%20or%20have%20a%20lower%20label.%20You%20can%20also%20allow%20scanner%20to%20downgrade%20a%20label%20if%20you%20want.%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20center%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20center%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22f2.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F132534i82A3941124C5217B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22f2.png%22%20alt%3D%22f2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20center%3B%22%3E%3CBR%20%2F%3E%3CEM%3EFigure%202%3A%20Enforce%20Confidential%5CProject%20Samos%20on%20all%20files%20in%20the%20repository%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%3CBR%20%2F%3EWe%20have%20added%20an%20option%20to%20use%20the%20scanner%20to%20remove%20labels%20from%20files%20in%20specific%20repository.%20You%20should%20just%20set%20the%20scanner%20to%20enforce%20default%20label%20%E2%80%9CNone%E2%80%9D%20on%20the%20repository.%3CBR%20%2F%3EAdditionally%2C%20the%20Azure%20Information%20Protection%20scanner%20can%20now%20identify%20if%20the%20current%20protection%20state%20of%20a%20file%20does%20not%20reflect%20the%20current%20protection%20policy%20for%20the%20label%20on%20the%20file%2C%20and%20adjust%20the%20protection%20state.%20For%20example%20if%20you%20started%20with%20classification%20only%20approach%20and%20labeled%20all%20your%20files%20as%20Confidential%20using%20scanner%20and%20later%20enabled%20protection%20on%20the%20file%2C%20now%20the%20scanner%20will%20identify%20this%20change%20and%20reapply%20the%20protection%20on%20already%20labeled%20files.%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%3CBR%20%2F%3EWe%20have%20also%20improved%20the%20installation%20procedure.%20For%20the%20unified%20labeling%20scanner%20you%20should%20only%20create%20one%20Azure%20AD%20registered%20app%20and%20grant%20admin%20consent.%20You%20no%20longer%20need%20to%20login%20with%20the%20scanner%20account%20in%20order%20to%20complete%20the%20deployment.%20You%20can%20use%20%E2%80%9C-onbehalf%E2%80%9D%20switch%20of%20the%20Set-AIPAuthentication%20cmdlet%20which%20allows%20you%20to%20use%20service%20accounts%20that%20no%20longer%20need%20%E2%80%9Clogon%20locally%E2%80%9D%20rights%20in%20any%20step%20of%20the%20deployment.%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%3CBR%20%2F%3EI%20encourage%20you%20to%20download%20the%20new%20preview%20version%20of%20the%20scanner%2C%20review%20it%20and%20share%20your%20feedback.%20You%20can%20find%20detailed%20instructions%20to%20deploy%20this%20new%20scanner%20version%20or%20upgrade%20from%20previous%20version%20in%20the%20updated%20Azure%20Information%20Protection%20unified%20labeling%20client%20administrator%20guide.%20See%20the%20new%20section%2C%20Installing%20the%20Azure%20Information%20Protection%20scanner.%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20left%3B%22%3E%3CBR%20%2F%3ENote%20that%20there%20are%20a%20few%20constraints%20in%20this%20version%3A%20no%20support%20for%20HYOK%2C%20in%20no%20support%20for%20offline%20policy%20and%20if%20you%20upgrade%20from%20your%20existing%20scanner%20the%20new%20scanner%20will%20initiate%20full%20scan%20of%20all%20repositories.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-862552%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EInformation%20Protection%20%26amp%3B%20Governance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Information%20Protection%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1727694%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1727694%22%20slang%3D%22en-US%22%3E%3CP%3ETheoretically%20you%20can%20use%20SQL%20express%20with%20multiple%20nodes%2C%20but%20in%20real%20prod%20deployments%20it%20just%20will%20not%20scale%20and%20SQL%20will%20become%20your%20bottleneck.%20SQL%20express%20is%20also%20limited%20in%20the%20DB%20size%2C%20so%20you%20will%20only%20be%20able%20to%20scan%20limited%20number%20of%20repos%20and%20maintain%20the%20cache%20of%20what%20was%20already%20scanned%20to%20avoid%20full%20rescans%20all%20the%20time%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1785139%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1785139%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Denis%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20also%20getting%20an%20error%20on%20my%20nodes%20stating%20%22Error%3A%20Policy%20does%20not%20include%20any%20automatic%20labeling%20condition%22%20in%20AIP.%26nbsp%3B%20While%20I%20set%20the%20content%20scan%20job%20to%20only%20discover%20info%20types%20defined%20in%20a%20policy%2C%26nbsp%3BI%20do%20have%20a%20label%20in%20the%20Office%20365%20Security%20and%20Compliance%20Center%20that%20automatically%20applies%20protection.%26nbsp%3B%20That%20label%20is%20also%20published%20in%20a%20label%20policy.%26nbsp%3B%20So%20not%20sure%20what's%20going%20on.%26nbsp%3B%20I%20will%20note%20that%20the%20AIP%20Scanner%20service%20account%20is%20not%20part%20of%20that%20label%20policy%20published%20in%20the%20S%26amp%3BC%20Center.%26nbsp%3B%20Could%20that%20be%20my%20issue%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20stop%20the%20AIP%20service%2C%20delete%20the%20'mip'%20folder%20under%20%22C%3A%5CUsers%5CAIP.Scanner%5CAppData%5CLocal%5CMicrosoft%5CMSIP%5Cmip%5CMSIP.Scanner.exe%22%20and%20verified%20it%20was%20recreated%20when%20the%20AIP%20service%20restarted.%26nbsp%3B%20So%20it%20seems%20to%20be%20picking-up%20the%20policy.%26nbsp%3B%20Otherwise%2C%20the%20only%20difference%20between%20my%20dev%20tenant%2C%20where%20targeted%20AIP%20scanning%20works%2C%20and%20the%20prod%20tenant%20is%20the%20difference%20with%20the%20label%20policy%20members.%26nbsp%3B%20In%20dev%20I%20have%20the%20label%20policy%20applied%20to%20all%20users%2C%20while%20prod%20only%20has%20pilot%20users%20defined.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20also%20note%20that%20while%20my%20AIP%20scans%20were%20successful%20when%20searching%20for%20all%20the%20sensitive%20info%20types%2C%20I%20recently%20received%20a%20different%20error%20about%20an%20invalid%20database%20schema.%26nbsp%3B%20Upgrading%20the%20client%20from%202.6.11%20to%202.8.85%20and%20running%20Update-AIPScanner%20all%20seemed%20to%20go%20fine%2C%20but%20maybe%20something%20didn't%20work%20right%20there.%26nbsp%3B%20I%20don't%20need%20to%20obtain%20an%20Azure%20AD%20token%20for%20the%20AIP%20scanner%20service%20again%20after%20a%20UL%20client%20upgrade%2C%20do%20I%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20thanks%20for%20the%20above%20info.%26nbsp%3B%20With%20the%20recent%20changes%20to%20AIP%20with%20the%20UL%20client%2C%20finding%20current%20and%20relevant%20info%20on%20AIP%20is%20like%20finding%20a%20needle%20in%20a%20stack%20of%20slightly%20older%20needles.%26nbsp%3B%20%3A)%3C%2Fimg%3E%26nbsp%3B%20Plenty%20of%20info%20out%20there%2C%20but%20mostly%20outdated%20content%20as%20it%20references%20the%20AIP%20classic%20client%20and%20the%20like.%26nbsp%3B%20And%20almost%20none%20of%20it%20is%20from%20people%20who've%20deployed%20and%20managed%20this%20in%20a%20production%20environment.%26nbsp%3B%20So%20you're%20troubleshooting%20steps%20are%20a%20huge%20help!%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1785210%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1785210%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F834041%22%20target%3D%22_blank%22%3E%40MJL76%3C%2FA%3E%26nbsp%3BYou%20need%20to%20target%20the%20scanner%20service%20account%20in%20a%20label%20policy%20for%20the%20auto-label%20to%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1785879%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1785879%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F834041%22%20target%3D%22_blank%22%3E%40MJL76%3C%2FA%3E%26nbsp%3BNo%20problem.%26nbsp%3B%20If%20you%20want%20to%20enforce%20a%20specific%20label%20on%20a%20repository%2C%20you%20would%20have%20to%20do%20the%20same%20where%20you%20add%20the%20scanner%20account%20to%20a%20policy%20that%20includes%20the%20label%20you%20want%20to%20label%20all%20contents%20of%20the%20repository%20with.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hear%20you%20on%20the%20MCAS%20part.%26nbsp%3B%20I%20need%20to%20figure%20out%20a%20good%20way%20to%20do%20that%20as%20well.%26nbsp%3B%20***Microsoft%20if%20you%20are%20listening***%26nbsp%3B%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1793230%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1793230%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20order%20to%20use%20UL%20scanner%20you%20must%20publish%20at%20least%20one%20policy%20to%20the%20account%20that%20was%20used%20as%20delegated%20user%20for%20getting%20policy%20on%20scanner.%20It%3Bs%20not%20supported%20to%20run%20AIP%20scanner%20with%20no%20published%20policy%20even%20if%20you%20use%20setting%20to%20detect%20any%20info%20type%20rather%20than%20using%20%22policy%20only%22%20setting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1809516%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1809516%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20able%20to%20scan%20all%20of%20my%20on-prem%20content%20with%20the%20AIP%20Scanner%20after%20adding%20that%20service%20account%20to%20a%20label%20policy%2C%20thanks.%26nbsp%3B%20However%2C%20I%E2%80%99ve%20encountered%20a%20bug%20and%20I%E2%80%99m%20not%20sure%20where%20to%20report%20it.%26nbsp%3B%20So%20I%20thought%20I%E2%80%99d%20throw%20it%20out%20here%2C%20in%20case%20anyone%20has%20any%20thoughts%20on%20it%20before%20I%20open%20a%20support%20ticket%20with%20Microsoft.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20AIP%20Scanner%20did%20find%20files%20using%20the%20sensitive%20information%20I%20defined%20in%20my%20auto-labeling%20rules.%26nbsp%3B%20However%2C%20it%E2%80%99s%20not%20honoring%20the%20rule%20conditions.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20example%2C%20I%20have%20a%20rule%20in%20a%20sensitivity%20label%20the%20requires%20both%20a%20US%20Social%20Security%20Number%20%3CEM%3EAND%3C%2FEM%3E%20a%20value%20from%20a%20keywords%20list%20(e.g.%20SSN%2C%20Social%20Security%2C%20SS%23%2C%20etc.)%20to%20be%20considered%20a%20match.%26nbsp%3B%20The%20AIP%20Scanner%2C%20however%2C%20is%20matching%20on%20the%20first%20condition%20and%20second%20condition%20and%20both%20conditions.%26nbsp%3B%20This%20is%20not%20what%20I%20want%20because%20I%20consider%20those%20first%20two%20matches%20to%20be%20false%20positives.%26nbsp%3B%26nbsp%3BIn%20other%20words%2C%20if%20the%20AIP%20Scanner%20finds%20a%20SSN%2C%20don%E2%80%99t%20label%20and%20encrypt%20it%20unless%20there%E2%80%99s%20a%20keyword%20in%20the%20file%2C%20as%20well.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20is%2C%20if%20I%20apply%20labels%20using%20the%20AIP%20Scanner%2C%20it%20will%20label%20and%20encrypt%2098%2C000%20files%20that%20shouldn%E2%80%99t%20be.%26nbsp%3B%26nbsp%3BBelow%20is%20a%20screenshot%20of%20my%20sensitivity%20label%20with%20the%20rules%20and%20their%20conditions.%26nbsp%3B%20The%20second%20screenshot%20is%20a%20pivot%20table%20I%20made%20from%20combing%20the%20AIP%20Scanner%20results.%26nbsp%3B%20As%20you%20can%20see%2C%20it%E2%80%99s%20not%20honoring%20the%20settings%20defined%20where%20BOTH%20conditions%20need%20to%20be%20met%20for%20the%20two%20rules%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AIP%20Sensitivity%20Label.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F228545iE254DF3F205D02BA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22AIP%20Sensitivity%20Label.png%22%20alt%3D%22AIP%20Sensitivity%20Label%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EAIP%20Sensitivity%20Label%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AIP%20Scanner%20Not%20Using%20Rule%20Conditions.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F228546i79F726A04885D2E8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22AIP%20Scanner%20Not%20Using%20Rule%20Conditions.png%22%20alt%3D%22AIP%20Scanner%20Report%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EAIP%20Scanner%20Report%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20thoughts%20on%20how%20I%20can%20get%20the%20AIP%20Scanner%20to%20process%20the%20auto-labeling%20rules%20correctly%2C%20or%20have%20it%20apply%20labels%20only%20if%20certain%20combinations%20of%20sensitive%20info%20types%20are%20discovered%20within%20a%20file%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1815696%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1815696%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%2F834041%22%20target%3D%22_blank%22%3E%40MJL76%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20would%20recommend%20to%20work%20with%20support%20as%20what%20you%20describe%20is%20not%20the%20expected%20behavior.%20Try%20also%20to%20test%20this%20with%20regular%20client%20%2F%20native%20labeling%20and%20see%20if%20same%20%22incorrect%22%20match%20is%20seen%20there%20or%20only%20on%20the%20scanner%20side.%20Share%20your%20finding%20with%20the%20support.%20They%20will%20help%20you%20to%20fix%20your%20settings%2C%20or%20if%20this%20is%20a%20bug%20in%20scanner%20%2F%20classification%20engine%20they%20will%20open%20the%20bug%20to%20relevant%20team.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1785495%22%20slang%3D%22en-US%22%3ERe%3A%20Unified%20labeling%20AIP%20scanner%20preview%20brings%20scaling%20out%20and%20more!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1785495%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Chris%2C%20that%20makes%20sense.%26nbsp%3B%20I%20added%20the%20service%20account%20to%20my%20pilot%20label%20policy%20and%20the%20content%20scan%20job%20is%20running%20great!%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20if%20I%20could%20only%20find%20a%20way%20to%20quickly%20specify%20a%20test%20site%2Fdoclib%20in%20SharePoint%20Online%20to%20apply%20a%20Microsoft%20Cloud%20App%20Security%20file%20policy%20to%2C%20without%20reviewing%20each%20folder%2C%20I'd%20be%20ecstatic.%26nbsp%3B%20%3A)%3C%2Fimg%3E%26nbsp%3B%20Hopefully%20one%20day%20they'll%20include%20a%20search%20function%20so%20I%20can%20specify%20a%20document%20library%20name%20instead%20of%20manually%20reviewing%20everyone%20in%20the%20org.%26nbsp%3B%20But%20that's%20not%20an%20AIP%20issue...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Since its release, the Azure Information Protection scanner has been adopted by many different types of customers. For example, some small businesses have deployed single scanners to address all their data at rest, others deployed a few machines in different locations or a few machines for the purpose of redundancy, while companies that needed to deal with petabytes of data may have deployed dozens of scanner instances, – such as internally at Microsoft, in which we deployed more than 40 scanners. Large enterprise customers faced increasing TCO, mainly driven by administration overhead and attempts to distribute the load between scanners.
Consistent feedback also came from customers adopting our unified labeling platform and moving to the Azure Information Protection Unified Labeling client. The Unified Labeling client allowed customers to use more flexible automatic rules on their endpoints but they could not leverage this flexibility on the scanner that its core functionality is discovery and labeling based on automatic rules. Customers also needed to maintain their labels and conditions in both Office 365Security and Compliance Center and in the Azure portal (in order to manage conditions used by Azure Information Protection scanner).


Unified labeling scanner is here to address scale out needs!
Finally, AIP scanner for unified labeling is here! Now you can completely move your label and policy management to O365 Security and Compliance Center and complete the migration to unified labeling platform. This allows you to use custom info types and dictionaries on the AIP scanner, tweak built-in info types, define confidence levels etc.
The Azure Information Protection scanner architecture was redesigned and in addition to adoption of MIP SDK that improves the performance of single nodes you can now group your scanners in clusters that service the same scanner profile. You no longer need to try to distribute repositories between different scanner nodes in order to achieve equal volumes scanned by every node. Now you can just set one profile and put all the repositories in the same profile (we still recommend separate profiles per geo location / data center) and add all the nodes to this profile. SQL DB, now holds core role as the orchestrator of the cluster, will take care of equal distribution of load, detect deactivated nodes, taken, for example due to maintenance or patching, and reallocate incomplete jobs to active scanner nodes. Added nodes to the profile will join current scan effort and get instructions to scan the next bunch of files. This provides simplified management and elastic growth and can help you reduce the number nodes based on volume that is needed to scan. For example you can start with 50 scanners to complete the initial scan of petabytes of data and then reduce the cluster to 5 nodes to scan subsequent newly created files in the repository.


scanner diagram v4.jpg
Figure 1: Distributed scanner architecture


We also incorporated a few more new features and fixes to the new scanner to improve overall management and administration. You can now decide that all, new unlabeled and already labeled files in a specific repository are labeled with specific label. For example, you can decide that all files in a repository be labeled as “Confidential”, and scanner will apply this label on all files that have no label or have a lower label. You can also allow scanner to downgrade a label if you want.

 

f2.png

 


Figure 2: Enforce Confidential\Project Samos on all files in the repository


We have added an option to use the scanner to remove labels from files in specific repository. You should just set the scanner to enforce default label “None” on the repository.
Additionally, the Azure Information Protection scanner can now identify if the current protection state of a file does not reflect the current protection policy for the label on the file, and adjust the protection state. For example if you started with classification only approach and labeled all your files as Confidential using scanner and later enabled protection on the file, now the scanner will identify this change and reapply the protection on already labeled files.


We have also improved the installation procedure. For the unified labeling scanner you should only create one Azure AD registered app and grant admin consent. You no longer need to login with the scanner account in order to complete the deployment. You can use “-onbehalf” switch of the Set-AIPAuthentication cmdlet which allows you to use service accounts that no longer need “logon locally” rights in any step of the deployment.


I encourage you to download the new preview version of the scanner, review it and share your feedback. You can find detailed instructions to deploy this new scanner version or upgrade from previous version in the updated Azure Information Protection unified labeling client administrator guide. See the new section, Installing the Azure Information Protection scanner.


Note that there are a few constraints in this version: no support for HYOK, in no support for offline policy and if you upgrade from your existing scanner the new scanner will initiate full scan of all repositories.

13 Comments
Super Contributor
"You can find detailed instructions to deploy this new scanner version or upgrade from previous version in the updated Azure Information Protection unified labeling client administrator guide. See the new section, Installing the Azure Information Protection scanner." As of 10/14/2019, the client admin guide does *not* include the new section "Installing the Azure Information Protection scanner" https://docs.microsoft.com/en-us/azure/information-protection/rms-client/clientv2-admin-guide-instal... Whereas I did find updated AIP Scanner documentation in this page instead: https://docs.microsoft.com/en-us/azure/information-protection/deploy-aip-scanner
Regular Visitor

Hello,

I'm trying to setup this scanner and the installation went smoothly.

The node is automatically added on Azure Portal, but i get this error :

Error : Policy does not include any labeling condition

 

I can click the "Scan now" Button but it doesnt do anything.

On the server i can the logs : MSIP.Scanner (6736) Failed to validate policy and confiuguration

 

I do have an AD Account synced on Azure AD, and the server has the UL Client and has internet.

 

Any ideas?

Thank you,

Clement

Microsoft

Error : Policy does not include any labeling condition can indicate one of two:

1. You did not create any automatic labeling condition in M365 S&C and did not set scanner to match all known Info types in the content scan job configuraiton.

2. You failed to acquire policy. You can check if you get mip.policies.sqlite3 under %localappdata%\Microsoft\MSIP\mip\MSIP.Scanner.exe\mip of the scanner account.

 

Please verify you completed the Set-AIPAuthentication command using the app token as explained at: https://docs.microsoft.com/en-us/azure/information-protection/rms-client/clientv2-admin-guide-powers...

Microsoft

Thank you Denis! This feedback helped me find resolution to an issue I was having.

Senior Member

Can we use the same cluster feature with the built in SQL Express Data Base architecture, or does this require a centralized SQL Instance per cluster?  

Microsoft

Theoretically you can use SQL express with multiple nodes, but in real prod deployments it just will not scale and SQL will become your bottleneck. SQL express is also limited in the DB size, so you will only be able to scan limited number of repos and maintain the cache of what was already scanned to avoid full rescans all the time

Occasional Visitor

Hi Denis, 

 

I am also getting an error on my nodes stating "Error: Policy does not include any automatic labeling condition" in AIP.  While I set the content scan job to only discover info types defined in a policy, I do have a label in the Office 365 Security and Compliance Center that automatically applies protection.  That label is also published in a label policy.  So not sure what's going on.  I will note that the AIP Scanner service account is not part of that label policy published in the S&C Center.  Could that be my issue?  

 

I did stop the AIP service, delete the 'mip' folder under "C:\Users\AIP.Scanner\AppData\Local\Microsoft\MSIP\mip\MSIP.Scanner.exe" and verified it was recreated when the AIP service restarted.  So it seems to be picking-up the policy.  Otherwise, the only difference between my dev tenant, where targeted AIP scanning works, and the prod tenant is the difference with the label policy members.  In dev I have the label policy applied to all users, while prod only has pilot users defined.  

 

I'll also note that while my AIP scans were successful when searching for all the sensitive info types, I recently received a different error about an invalid database schema.  Upgrading the client from 2.6.11 to 2.8.85 and running Update-AIPScanner all seemed to go fine, but maybe something didn't work right there.  I don't need to obtain an Azure AD token for the AIP scanner service again after a UL client upgrade, do I?  

 

And thanks for the above info.  With the recent changes to AIP with the UL client, finding current and relevant info on AIP is like finding a needle in a stack of slightly older needles.  :)  Plenty of info out there, but mostly outdated content as it references the AIP classic client and the like.  And almost none of it is from people who've deployed and managed this in a production environment.  So you're troubleshooting steps are a huge help!  

Senior Member

@MJL76 You need to target the scanner service account in a label policy for the auto-label to work.

Occasional Visitor

Thanks Chris, that makes sense.  I added the service account to my pilot label policy and the content scan job is running great!  

 

Now if I could only find a way to quickly specify a test site/doclib in SharePoint Online to apply a Microsoft Cloud App Security file policy to, without reviewing each folder, I'd be ecstatic.  :)  Hopefully one day they'll include a search function so I can specify a document library name instead of manually reviewing everyone in the org.  But that's not an AIP issue...

 

Thanks again! 

Senior Member

@MJL76 No problem.  If you want to enforce a specific label on a repository, you would have to do the same where you add the scanner account to a policy that includes the label you want to label all contents of the repository with.  

 

I hear you on the MCAS part.  I need to figure out a good way to do that as well.  ***Microsoft if you are listening***  :)

Microsoft

In order to use UL scanner you must publish at least one policy to the account that was used as delegated user for getting policy on scanner. It;s not supported to run AIP scanner with no published policy even if you use setting to detect any info type rather than using "policy only" setting.

Occasional Visitor

I was able to scan all of my on-prem content with the AIP Scanner after adding that service account to a label policy, thanks.  However, I’ve encountered a bug and I’m not sure where to report it.  So I thought I’d throw it out here, in case anyone has any thoughts on it before I open a support ticket with Microsoft. 

 

The AIP Scanner did find files using the sensitive information I defined in my auto-labeling rules.  However, it’s not honoring the rule conditions. 

 

For example, I have a rule in a sensitivity label the requires both a US Social Security Number AND a value from a keywords list (e.g. SSN, Social Security, SS#, etc.) to be considered a match.  The AIP Scanner, however, is matching on the first condition and second condition and both conditions.  This is not what I want because I consider those first two matches to be false positives.  In other words, if the AIP Scanner finds a SSN, don’t label and encrypt it unless there’s a keyword in the file, as well. 

 

As is, if I apply labels using the AIP Scanner, it will label and encrypt 98,000 files that shouldn’t be.  Below is a screenshot of my sensitivity label with the rules and their conditions.  The second screenshot is a pivot table I made from combing the AIP Scanner results.  As you can see, it’s not honoring the settings defined where BOTH conditions need to be met for the two rules: 

 

AIP Sensitivity LabelAIP Sensitivity LabelAIP Scanner ReportAIP Scanner Report

 

Any thoughts on how I can get the AIP Scanner to process the auto-labeling rules correctly, or have it apply labels only if certain combinations of sensitive info types are discovered within a file?  

Microsoft

Hi @MJL76 

 

I would recommend to work with support as what you describe is not the expected behavior. Try also to test this with regular client / native labeling and see if same "incorrect" match is seen there or only on the scanner side. Share your finding with the support. They will help you to fix your settings, or if this is a bug in scanner / classification engine they will open the bug to relevant team.