Divide Office 365 tenants with Compliance Boundaries

%3CLINGO-SUB%20id%3D%22lingo-sub-100545%22%20slang%3D%22en-US%22%3ERe%3A%20Divide%20Office%20365%20tenants%20with%20Compliance%20Boundaries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100545%22%20slang%3D%22en-US%22%3E%3CP%3EWait%20for%20Ignite%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100476%22%20slang%3D%22en-US%22%3ERe%3A%20Divide%20Office%20365%20tenants%20with%20Compliance%20Boundaries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100476%22%20slang%3D%22en-US%22%3E%3CP%3EHiya%3C%2FP%3E%3CP%3ESeems%20like%20the%20wording%20of%20the%20feature%20has%20changed%20and%20does%20not%20mention%20%22Tenants%22%20anymore%2C%20seems%20like%20only%20searches%20and%20results%20will%20get%20boundaries%20not%20the%20actual%20data%20itself%20(via%20a%20different%20tenant%20located%20at%20a%20local%20region).%20Just%20hiding%20search%20results%20(if%20I%20understand%20this%20feature%20correctly)%20will%20not%20meet%20compliance%20requirements%20that%20everyone%20is%20after%20around%20data%20boundaries%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eregards%3C%2FP%3E%3CP%3EMo%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77158%22%20slang%3D%22en-US%22%3ERe%3A%20Divide%20Office%20365%20tenants%20with%20Compliance%20Boundaries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77158%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20compliance%20security%20filters%20work%20just%20fine%20with%20Exchange%20and%20SPO%20workloads%2C%20and%20they%20are%20relatively%20easy%20to%20set%20up.%20Although%20they%20are%20only%20avaialble%20via%20PowerShell%20for%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20if%20you%20are%20eager%20to%20test%20this%2C%20you%20can%20certainly%20configure%20a%20%22compliance%20boundary%22%20via%20compliance%20security%20filters%2C%20they%20are%20practically%20designed%20with%20this%20in%20mind.%20%26nbsp%3BThey%20support%20a%20huge%20set%20of%20attributes%2C%20and%20you%20can%20even%20apply%20them%20based%20on%20the%20content%20of%20the%20document%2Fitem.%20Really%20cool%20stuff!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-76974%22%20slang%3D%22en-US%22%3EDivide%20Office%20365%20tenants%20with%20Compliance%20Boundaries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76974%22%20slang%3D%22en-US%22%3E%3CP%3EA%20%3CA%20href%3D%22https%3A%2F%2Fproducts.office.com%2Fen-us%2Fbusiness%2Foffice-365-roadmap%3Ffeatureid%3D16145%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Enew%20feature%3C%2FA%3E%20on%20the%20Office%20365%20roadmap%20that's%20worth%20surfacing%20-%26nbsp%3BCompliance%20Boundaries%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Tenants%20can%20be%20divided%20into%20smaller%20tenants%20as%20defined%20by%20geographical%20boundaries%20or%20individual%20business%20units.%20This%20also%20includes%20full%20support%20of%20Compliance%20Security%20Filters%20for%20OneDrive%20for%20Business.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20rather%20than%20a%20monolithic%20approach%20to%20a%20tenant%2C%20it%20can%20actually%20be%20divided%20based%20on%20function%20or%20locales%20for%20management%20purposes.%20This%20can%20work%20with%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt210915(v%3Dexchg.160).aspx%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ECompliance%20Security%20Filters%3C%2FA%3E%2C%20though%20only%26nbsp%3BOneDrive%20is%20mentioned%20they%20also%20apparently%20work%20with%20mailboxes%20and%20SharePoint%20Online.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20filters%20can%20be%20used%20to%20set%20compliance%20search%20actions%20based%20on%20individuals%20or%20groups%20and%20in%20the%20future%20presumably%2C%20can%20be%20associated%20with%20these%20compliance%20boundaries.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20sounds%20like%20a%20welcome%20feature%2C%20especially%20for%20those%20larger%20tenants%20spread%20across%26nbsp%3Bregions%20or%20those%20with%20particular%20compliance%20requirements.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-76974%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECompliance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Office%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Trusted Contributor

A new feature on the Office 365 roadmap that's worth surfacing - Compliance Boundaries:

 

"Tenants can be divided into smaller tenants as defined by geographical boundaries or individual business units. This also includes full support of Compliance Security Filters for OneDrive for Business."

 

So rather than a monolithic approach to a tenant, it can actually be divided based on function or locales for management purposes. This can work with Compliance Security Filters, though only OneDrive is mentioned they also apparently work with mailboxes and SharePoint Online.  

 

These filters can be used to set compliance search actions based on individuals or groups and in the future presumably, can be associated with these compliance boundaries. 

 

This sounds like a welcome feature, especially for those larger tenants spread across regions or those with particular compliance requirements.

3 Replies

The compliance security filters work just fine with Exchange and SPO workloads, and they are relatively easy to set up. Although they are only avaialble via PowerShell for now.

 

But if you are eager to test this, you can certainly configure a "compliance boundary" via compliance security filters, they are practically designed with this in mind.  They support a huge set of attributes, and you can even apply them based on the content of the document/item. Really cool stuff!

Hiya

Seems like the wording of the feature has changed and does not mention "Tenants" anymore, seems like only searches and results will get boundaries not the actual data itself (via a different tenant located at a local region). Just hiding search results (if I understand this feature correctly) will not meet compliance requirements that everyone is after around data boundaries

 

regards

Mo

Wait for Ignite :)