Home

Conditional access to Office portal not just Exchange Online, SharePoint online, etc.

%3CLINGO-SUB%20id%3D%22lingo-sub-21163%22%20slang%3D%22en-US%22%3EConditional%20access%20to%20Office%20portal%20not%20just%20Exchange%20Online%2C%20SharePoint%20online%2C%20etc.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-21163%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20implemented%20a%20solution%20whereby%20through%20the%20use%20of%20Intune%20or%20the%20recentently%20announced%20Azure%20AD%20conditional%20access%20is%20implemented%20so%20that%20access%20to%20portal.office.com%20is%20blocked%20for%20devices%20unknown%20to%20Azure%20AD%20or%20unmanaged%20by%20Intune%3F%20As%20it%20stands%20the%20conditional%20access%20implemented%20by%20Intune%20aloows%20portal%20access%20but%20then%20blocks%20access%20to%20the%20online%20services%2C%20Exchange%2C%20SharePoint%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20tenant%20is%20federated%20so%20I%20am%20thinking%20that%20the%20claims%20issuance%20should%20be%20able%20to%20handle%20this%20type%20of%20restriction%20but%20I%20am%20struggline%20to%20find%20a%20guide%20as%20to%20how%20to%20implement%20the%20requirement.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMT%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPaul%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-21163%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAuthentication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-21171%22%20slang%3D%22en-US%22%3ERe%3A%20Conditional%20access%20to%20Office%20portal%20not%20just%20Exchange%20Online%2C%20SharePoint%20online%2C%20etc.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-21171%22%20slang%3D%22en-US%22%3E%3CP%3EPaul%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20similar%20challenge%20and%20haven't%20quite%20resolved%20this%20fully%20yet.%26nbsp%3B%20Firstly%20let%20me%20start%20by%20stating%20that%20MS%20has%20made%20life%20really%20difficult%20here.%26nbsp%3B%20They%20have%20talken%20an%20approach%20that%20is%20more%20identity%20based%20and%20less%20about%20the%20device%20being%20used.%26nbsp%3BThey%26nbsp%3Bsuggest%20we%20layer%20controls%20like%20IRM%2FDRM%20on%20top%20of%20certain%20services%20for%20further%20device%20level%20control.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20this%20stage%20options%20as%20I%20see%20it%20are%3A%3C%2FP%3E%3CP%3E-%20Enforce%20certificate%20based%20AuthN%20when%20the%20device%20authenticates%20to%20ADFS.%26nbsp%3B%20You'd%20need%20to%20be%20able%20to%20generate%20certs%20for%20each%20authorised%20device%20and%20provision%20those%20certs%2C%20probably%20using%20your%20MDM%20(for%20mobile)%20or%20SCCM%2FGroup%20policy%20(for%20PCs).%26nbsp%3B%20This%20will%20give%20all%20authorised%20devices%20course%20grained%20access%20to%20O365%20(i.e.%20anything%20that%20user%20holds%20a%20license%20for).%26nbsp%3B%20You%20can%20still%20layer%20conditional%20access%20policies%20on%20top%20of%20this%20approach%20(in%20AzureAD%2FInTune)%20to%20get%20more%20fine%20grained%20if%20you%20want%20(but%20that%20gets%20complicated).%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Domain%20joined%20only%20(Windows)%20policy%20(this%20has%20only%20been%20out%20to%20market%20for%20a%20month%20or%20two)%3A%20This%20will%20allow%20devices%20that%20are%20joined%20to%20your%20corporate%20AD%20domain%20to%20have%20access%20(to%20whatever%20resource%20you're%20enabling%20the%20policy%20for)%2C%20and%20those%20that%20are%20not%20will%20be%20blocked.%26nbsp%3B%20You%20also%20need%20to%20think%20about%20preventing%20users%20from%20doing%20a%20%22workplace%20join%22%20for%20their%20personal%20Windows%20devices%20(such%20as%20their%20home%20PC).%26nbsp%3B%20This%20approach%20is%20supported%20for%20Win%20OS's%20%26gt%3B%3D8.1.%26nbsp%3B%20If%20you%20want%20to%20enforce%20this%20policy%20for%20%3CWIN8.1%20you%3D%22%22%3E%3C%2FWIN8.1%3E%3C%2FP%3E%3CP%3E-%20Compliant%20devices%20only%20(Conditional%20access)%3A%26nbsp%3B%20This%20approach%20requires%20InTune%20enrollment%20so%20you%20can't%20be%20using%20another%20MDM%20unless%20they%20support%20conditional%20access%20compliance%20testing%2Freporting.%26nbsp%3B%20This%20approach%20allows%20you%20to%20define%20config%20policies%20for%20lots%20of%20different%20devices%20and%20OS%20versions%20and%20blocks%20them%20if%20they%20aren't%20compliant%20with%20the%20policy.%26nbsp%3B%20However%2C%20this%20approach%20doesn't%20allow%20you%20to%20allow%2Fblock%20devices%20based%20on%20who%20owns%20them%20(i.e.%20corporate%20owned%20vs%20BYOD).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps.%26nbsp%3B%20Let%20me%20know%20how%20you%20go.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EBen%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Paul Bendall
Contributor

Has anyone implemented a solution whereby through the use of Intune or the recentently announced Azure AD conditional access is implemented so that access to portal.office.com is blocked for devices unknown to Azure AD or unmanaged by Intune? As it stands the conditional access implemented by Intune aloows portal access but then blocks access to the online services, Exchange, SharePoint, etc.

 

Our tenant is federated so I am thinking that the claims issuance should be able to handle this type of restriction but I am struggline to find a guide as to how to implement the requirement.

 

MT

 

Paul

1 Reply
Highlighted

Paul,

 

I have a similar challenge and haven't quite resolved this fully yet.  Firstly let me start by stating that MS has made life really difficult here.  They have talken an approach that is more identity based and less about the device being used. They suggest we layer controls like IRM/DRM on top of certain services for further device level control. 

 

At this stage options as I see it are:

- Enforce certificate based AuthN when the device authenticates to ADFS.  You'd need to be able to generate certs for each authorised device and provision those certs, probably using your MDM (for mobile) or SCCM/Group policy (for PCs).  This will give all authorised devices course grained access to O365 (i.e. anything that user holds a license for).  You can still layer conditional access policies on top of this approach (in AzureAD/InTune) to get more fine grained if you want (but that gets complicated). 

- Domain joined only (Windows) policy (this has only been out to market for a month or two): This will allow devices that are joined to your corporate AD domain to have access (to whatever resource you're enabling the policy for), and those that are not will be blocked.  You also need to think about preventing users from doing a "workplace join" for their personal Windows devices (such as their home PC).  This approach is supported for Win OS's >=8.1.  If you want to enforce this policy for <Win8.1 you'll need to deploy an InTune agent to them. (I believe there may also be a Mac agent but don't quote me on that!).

- Compliant devices only (Conditional access):  This approach requires InTune enrollment so you can't be using another MDM unless they support conditional access compliance testing/reporting.  This approach allows you to define config policies for lots of different devices and OS versions and blocks them if they aren't compliant with the policy.  However, this approach doesn't allow you to allow/block devices based on who owns them (i.e. corporate owned vs BYOD).

 

Hope this helps.  Let me know how you go.

 

Regards

Ben

 

 

 

Related Conversations
MS Access
jmtreky in Access on
0 Replies
Office 365 domain using external email server
SimonNZ in Office 365 on
1 Replies
Help! Simple maths not working?
KellieJean-in-Newie in Access on
0 Replies
Group and User Mix-up
Ruby_Monday in Office 365 on
3 Replies