Home

Restricting client access to other Office 365 tenants

%3CLINGO-SUB%20id%3D%22lingo-sub-28612%22%20slang%3D%22en-US%22%3ERestricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-28612%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3BWhen%20allowing%20connectivity%20into%20Office%20365%2C%20is%20there%20a%20way%20to%20restrict%20access%20to%20a%20single%20a%20tenant%3F%20For%20the%20purposes%20of%20DLP%20I%20need%20to%20prevent%20internal%20machines%20logging%20onto%20any%20another%20email%20service%20including%20other%20365%20tenants%2C%20how%20could%20this%20be%20acheived%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGoogle%20offer%20a%20way%20to%20restrict%20this%20by%20using%20additional%20headers%20-%26gt%3B%20%3CA%20href%3D%22https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F1668854%3Fhl%3Den%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F1668854%3Fhl%3Den%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20thanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-Ben%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-28612%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAuthentication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356912%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356912%22%20slang%3D%22en-US%22%3EOne%20way%20to%20keep%20people%20from%20access%20Software%20as%20a%20Service%20systems%20like%20Hotmail%2C%20is%20with%20Cloud%20App%20Security.%20It%20can%20be%20used%20to%20prevent%20access%20to%20thousands%20of%20different%20apps%20like%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356870%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356870%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3Ehow%20to%20block%20non-business%20tenant%20outlook%20access%20(eg.%20Hotmail)%3F%3C%2FSPAN%3E%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284382%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284382%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlthough%20not%20a%20complete%20solution%2C%26nbsp%3Badmins%20can%20configure%20Outlook%20client%20to%20prevent%20users%20from%20adding%20new%20accounts%2Fprofiles.%20This%20would%20stop%26nbsp%3Bemployees%20from%20accessing%20other%20email%20services%20from%20the%20desktop%20client.%20However%2C%20OWA%20and%20other%20browser-based%20services%20would%20still%20be%20accessible%20without%20another%20control%20in%20place.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94060%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94060%22%20slang%3D%22en-US%22%3EYou%20can%20use%20Intune's%20Conditional%20Access%20function%20to%20restrict%20access%20to%20company%20devices.%20Assuming%20that%20your%20definition%20of%20a%20'company%20device'%20is%20one%20that%20is%20enrolled%20in%20Intune.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-93685%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-93685%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20This%20is%20done%20Through%20Tenant%20Restrictions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou'll%20configure%20your%20outbound%20Proxy%20server%2C%20to%20insert%20a%20%22Restrict-Access-To-Tenants%3A%20%3CPERMITTED%20tenant%3D%22%22%20list%3D%22%22%3E%20header%20in%20packets%20bound%20to%20login.microsoftonline.com%2C%20login.microsoft.com%2C%20and%20login.windows.net%3C%2FPERMITTED%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou''%20then%20Go%20to%20your%20O365%20Tenant%2C%20and%20configure%20Tenant%20restrictions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20this%20to%20work%2C%20the%20Proxy%20needs%20to%20support%20SSL%20inspection%2C%20in%20order%20to%20insert%20the%20header.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEnd%20result%20will%20be%3A%3C%2FP%3E%3CP%3EScenario%3A%20User%20tries%20to%20access%20outlook.office.com%20to%20get%20access%20to%20his%20Tenant%20(contractor.onmicrosoft.com)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnce%20he%20enters%20the%20url%2C%20open%20outlook%20%2F%20client%20to%20access%20Saas%20service%2C%20he%20gets%20redirected%20to%20AzureAD%20(url's%20listed%20above%20for%20login)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProxy%20intercepts%20traffic%20to%20AAD%20and%20inserts%20HTTP%20header%2C%20indicating%20yourtenant.onmicrosoft.com%20is%20the%20only%20allowed%20tenant%2C%20and%20controcator.onmicrosoft.com%20is%20not%20allowed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAAD%20does%20not%20issue%20a%20service%20token%20for%20the%20contractor.onmicrosoft.com%20user%2C%20so%20the%20client%20cannot%20Authenticate%20to%20gain%20access%20to%20the%20Saas%20Service.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20works%20for%20controlling%20access%20to%20Microsoft%20Tenants%20from%20your%20Network%2C%20so%20if%20the%20Contractor%20can%20connect%20his%20mobile%20phone%20as%20a%20hotspot%2C%20or%20bypass%20your%20network%20security%20controlls%20(Proxy%20Server)%2C%20then%20this%20wont%20work.%20So%20additional%20controls%20might%20need%20to%20be%20implemented%20to%20ensure%20your%20DLP%20controls%20are%20enforced%20when%20using%20Tenant%20restrictions%20in%20O365.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57338%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57338%22%20slang%3D%22en-US%22%3E%3CP%3ECurrently%20Azure%20AD%20tenant%20restrictions%20is%20the%26nbsp%3Bway%20to%20accomplish%20this.%20Can%20you%20give%20an%20example%20of%20scenario%20where%20you%20would%20have%20to%20restrict%20access%20when%20your%20users%20are%20not%20on%20your%20network%3F%20Say%20for%20example%20that%20one%20of%20your%20employees%20work%20for%20a%20non%20profit%20or%20volunteers%20at%20a%20school%20that%20has%20O365%2C%20or%20they%20get%20invited%20by%20their%20kids%20to%20review%20their%20schoolwork%20on%20their%26nbsp%3Bschool%20OneDrive.%20The%20only%20way%20to%20really%20accomplish%20that%20blocking%20would%20be%20to%20have%20your%20company%20laptops%20limit%20access%20in%20the%20local%20firewall%20(feature%20we%20dont%20have%20today%20to%20do%20what%20tenant%20restriction%20does%20but%20do%20it%20client%20side).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBrjann%3C%2FP%3E%0A%3CP%3E-%20Azure%20AD%20Customer%20Success%20team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51964%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51964%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20an%20bad%20there.%26nbsp%3B%20Only%20works%20with%20your%20network%20as%20the%20accessing%20permiter.%26nbsp%3B%20Off%20your%20LAN%2FVPN%20it%20doesn't%20help.%26nbsp%3B%20Also%20you%20need%20Azure%20AD%20P1%20licensing%20to%20use%20it.%26nbsp%3B%20And%20there%20is%20overhead%20with%20SSL%20decryption%2C%20inject%20a%20header%2C%20and%20encrypt%20to%20send%20it%20on%20its%20way.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51609%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51609%22%20slang%3D%22en-US%22%3E%3CP%3EYup%2C%20now%20we%20do%20have%20options.%20It's%20great%20to%20see%20how%20many%20things%20can%20change%20around%20O365%20in%20just%20few%20months!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51447%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51447%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20article%20is%20pretty%20recent%20and%20describes%20how%20to%20perform%20tenant%20restrictions%20if%20you%20use%20a%20modern%20authentication%20client.%26nbsp%3B%20Enables%20you%20to%20restrict%20what%20tenants%20can%20be%20accessed%20from%20your%20network.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-tenant-restrictions%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-tenant-restrictions%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29437%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29437%22%20slang%3D%22en-US%22%3E%3CP%3EThere's%20no%20way%20to%20do%20this%20in%20O365%2C%20even%20if%20you%20have%20AD%20FS%20in%20place.%20You%20can%20probably%20use%20a%20similar%20solution%20to%20what's%20described%20in%20the%20article%2C%20with%20inspecting%20all%20traffic%20to%20O365%2C%20but%20I%20wouldnt%20really%20recommend%20such%20approach.%20As%20Dean%20mentioned%2C%20there%20are%20plenty%20controls%20available%20as%20part%20of%20O365%20or%20additional%20services%20to%20secure%20access%20to%20your%20data%2C%20one%20of%20them%26nbsp%3B(or%20a%20combination)%20should%20meet%20your%20needs.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29334%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29334%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20Rights%20Management%20had%20been%20enabled%20Snowden%20would%26nbsp%3B%20not%20have%20been%20able%20to%20use%20the%20files%20he%20stole.IRM%2FRMS%20is%20the%20most%20effective%20way%20to%20mitigate%20the%20risks%20associated%20with%20data%20that%20has%20leaked.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Data%20Loss%20Prevention%20policies%20in%20O365%20and%20now%20in%20Flow%20can%20help%20mitigate%20the%20risks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdvanced%20Threat%26nbsp%3BAnalytics%20(ATA)%20can%20be%20used%20to%20identify%20abnormal%20behavior%2C%20such%20as%20large%20number%20of%20file%20downloads%2C%20but%20this%20is%20only%20good%20for%20on-premises%20systems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAzure%20Security%20Center%20can%20be%20used%20to%20monitor%20network%20traffic%26nbsp%3Bfrom%20many%20applications%20for%20suspicios%20behavior%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fdocumentation%2Farticles%2Fsecurity-center-detection-capabilities%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fdocumentation%2Farticles%2Fsecurity-center-detection-capabilities%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29310%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29310%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Dean%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Thanks%20for%20the%20reply.%20Both%20are%20good%20suggestions%20but%20unfortunatley%20I%20can't%20see%20them%20as%20being%20practical%20ways%20to%20prevent%20data%20leakage.%20To%20encrypt%20all%20our%20data%20and%20work%20out%20an%20effective%20rights%20management%20policy%20would%20take%20a%20very%20long%20time%20and%20although%20its%20an%20extreme%20example%2C%20I'm%20pretty%20sure%20Snowden%20filled%20out%20some%20sort%20of%20AUP%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20way%20I%20can%20see%20to%20restrict%20data%20leakage%20to%20another%20tenant%26nbsp%3Bat%20the%20moment%20is%20to%20look%20at%20SSL%20Inspection%20and%20apply%20some%20form%20or%20URL%20filtering%20...%20whilst%20it%20could%20be%20effective%2C%20it's%20not%20a%20supported%20solution%20by%20Microsoft%20and%20they%20activley%20discourage%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-Ben%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29307%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29307%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20way%20to%20prevent%20this%20would%20be%20to%20implement%20Rights%20Management.%20When%20the%20contractor%20has%20finished%20their%20job%2C%20the%20rights%20to%20the%20affected%20files%20will%20no%20longer%20be%20available%20to%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20way%20to%20mititigate%20this%20risk%20is%20to%20ensure%20that%20the%20appropriate%20clauses%20are%20in%20your%20contracts%20and%20to%20have%20the%20contractors%20sign%20an%20appropriate%20%22terms%20of%20use%22%20document.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29304%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29304%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mark%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Thanks%20for%20the%20reply.%20I%20undertstand%20around%20the%20restrictions%26nbsp%3Bfor%20logging%20onto%20our%20own%20tenant%20and%20we%20have%20those%20in%20place.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20scenario%20I'm%20thinking%20about%20is%20when%20say%20for%20example%20a%20contractor%20was%20logged%20on%20to%20one%20of%20our%20corporate%20machines%20and%20they%20had%20their%20own%20tenant.%20Whats%20to%20stop%20them%20from%20spinning%20up%20a%20browser%20or%20outlook%20and%20logging%20on%20to%20their%20own%20account%20and%20emailing%20information%20out%20that%20way.%20All%20we%20would%20see%20at%20the%20proxy%20level%20is%20legitimate%26nbsp%3Bencrypted%20traffic%20to%20outlook.office365.com.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20interested%20to%20see%20how%20other%20people%20have%20dealt%20with%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-Ben%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29301%22%20slang%3D%22en-US%22%3ERe%3A%20Restricting%20client%20access%20to%20other%20Office%20365%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29301%22%20slang%3D%22en-US%22%3E%3CP%3EThat%60s%20something%20I%20have%20to%20deal%20with%2C%20too.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20me%20it%20is%20allowing%20access%20only%20to%20company%20devices.%20Intune%20doesn%60t%20offer%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBen%2C%20for%20other%20Office%20365%20tenants%20you%20simple%26nbsp%3Bgive%20to%20user%20no%20license%20in%20this%20tenant.%20So%20they%20will%20have%20no%20Mail%20account%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20for%20orther%20mail%20systems%20you%20can%20block%20the%20URLs%20for%20example.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20helps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMark%3C%2FP%3E%3C%2FLINGO-BODY%3E
Ben Hicks
Occasional Contributor

Hi,

   When allowing connectivity into Office 365, is there a way to restrict access to a single a tenant? For the purposes of DLP I need to prevent internal machines logging onto any another email service including other 365 tenants, how could this be acheived? 

 

Google offer a way to restrict this by using additional headers -> https://support.google.com/a/answer/1668854?hl=en

 

Many thanks,

 

-Ben

15 Replies

That`s something I have to deal with, too.

 

For me it is allowing access only to company devices. Intune doesn`t offer that.

 

Ben, for other Office 365 tenants you simple give to user no license in this tenant. So they will have no Mail account there.

 

As for orther mail systems you can block the URLs for example.

 

Hope that helps.

 

Mark

Hi Mark,

     Thanks for the reply. I undertstand around the restrictions for logging onto our own tenant and we have those in place.

 

The scenario I'm thinking about is when say for example a contractor was logged on to one of our corporate machines and they had their own tenant. Whats to stop them from spinning up a browser or outlook and logging on to their own account and emailing information out that way. All we would see at the proxy level is legitimate encrypted traffic to outlook.office365.com.

 

I'm interested to see how other people have dealt with this.

 

Cheers,

 

-Ben

 

 

One way to prevent this would be to implement Rights Management. When the contractor has finished their job, the rights to the affected files will no longer be available to them.

 

Another way to mititigate this risk is to ensure that the appropriate clauses are in your contracts and to have the contractors sign an appropriate "terms of use" document.

Hi Dean,

    Thanks for the reply. Both are good suggestions but unfortunatley I can't see them as being practical ways to prevent data leakage. To encrypt all our data and work out an effective rights management policy would take a very long time and although its an extreme example, I'm pretty sure Snowden filled out some sort of AUP :)

 

The only way I can see to restrict data leakage to another tenant at the moment is to look at SSL Inspection and apply some form or URL filtering ... whilst it could be effective, it's not a supported solution by Microsoft and they activley discourage it.

 

-Ben

If Rights Management had been enabled Snowden would  not have been able to use the files he stole.IRM/RMS is the most effective way to mitigate the risks associated with data that has leaked.

 

The Data Loss Prevention policies in O365 and now in Flow can help mitigate the risks.

 

Advanced Threat Analytics (ATA) can be used to identify abnormal behavior, such as large number of file downloads, but this is only good for on-premises systems.

 

Azure Security Center can be used to monitor network traffic from many applications for suspicios behavior, see https://azure.microsoft.com/en-us/documentation/articles/security-center-detection-capabilities/

 

There's no way to do this in O365, even if you have AD FS in place. You can probably use a similar solution to what's described in the article, with inspecting all traffic to O365, but I wouldnt really recommend such approach. As Dean mentioned, there are plenty controls available as part of O365 or additional services to secure access to your data, one of them (or a combination) should meet your needs.

This article is pretty recent and describes how to perform tenant restrictions if you use a modern authentication client.  Enables you to restrict what tenants can be accessed from your network.

https://docs.microsoft.com/en-us/azure/active-directory/active-directory-tenant-restrictions

Yup, now we do have options. It's great to see how many things can change around O365 in just few months!

Good an bad there.  Only works with your network as the accessing permiter.  Off your LAN/VPN it doesn't help.  Also you need Azure AD P1 licensing to use it.  And there is overhead with SSL decryption, inject a header, and encrypt to send it on its way.

Currently Azure AD tenant restrictions is the way to accomplish this. Can you give an example of scenario where you would have to restrict access when your users are not on your network? Say for example that one of your employees work for a non profit or volunteers at a school that has O365, or they get invited by their kids to review their schoolwork on their school OneDrive. The only way to really accomplish that blocking would be to have your company laptops limit access in the local firewall (feature we dont have today to do what tenant restriction does but do it client side).

 

Brjann

- Azure AD Customer Success team

Hi This is done Through Tenant Restrictions.

 

You'll configure your outbound Proxy server, to insert a "Restrict-Access-To-Tenants: <permitted tenant list> header in packets bound to login.microsoftonline.com, login.microsoft.com, and login.windows.net

 

You'' then Go to your O365 Tenant, and configure Tenant restrictions.

 

For this to work, the Proxy needs to support SSL inspection, in order to insert the header.

 

End result will be:

Scenario: User tries to access outlook.office.com to get access to his Tenant (contractor.onmicrosoft.com)

 

Once he enters the url, open outlook / client to access Saas service, he gets redirected to AzureAD (url's listed above for login)

 

Proxy intercepts traffic to AAD and inserts HTTP header, indicating yourtenant.onmicrosoft.com is the only allowed tenant, and controcator.onmicrosoft.com is not allowed.

 

AAD does not issue a service token for the contractor.onmicrosoft.com user, so the client cannot Authenticate to gain access to the Saas Service.

 

 

This works for controlling access to Microsoft Tenants from your Network, so if the Contractor can connect his mobile phone as a hotspot, or bypass your network security controlls (Proxy Server), then this wont work. So additional controls might need to be implemented to ensure your DLP controls are enforced when using Tenant restrictions in O365.

You can use Intune's Conditional Access function to restrict access to company devices. Assuming that your definition of a 'company device' is one that is enrolled in Intune.

Hi everyone,

 

Although not a complete solution, admins can configure Outlook client to prevent users from adding new accounts/profiles. This would stop employees from accessing other email services from the desktop client. However, OWA and other browser-based services would still be accessible without another control in place. 

how to block non-business tenant outlook access (eg. Hotmail)?


One way to keep people from access Software as a Service systems like Hotmail, is with Cloud App Security. It can be used to prevent access to thousands of different apps like this.