Skip to main content
McAfee Enterprise MVISION Cloud

Configure Device Management for Office 365 with ADFS

This topic describes the steps to configure Device Management for Office 365 with ADFS.

Prerequisites 

  • Access to functional ADFS SSO setup for Office 365.
  • Create a client certificate (public and private) using an internal Certificate Authority or PKI system.
  • Distribute the client certificate (Cert+Key) to the customer's managed endpoints via an MDM, GPO, or other package management utility.
  • Upload the signing certificate (public only) to the MVISION Cloud Access Security Manager. As an optional step, you can configure the Certificate Revocation List (CRL) URL. This allows the MVISION Cloud Access Control pane to query the CRL and determine if the existing certificates are still valid.
  • Access to MVISION Cloud admin tenant and existing Office 365 managed service.

How it Works

The client device is directed to the MVISION Cloud Control Point (Reverse Proxy) either through an IDP or CSP initiated redirection. The MVISION Cloud Control Point interrogates the Endpoint system for the required client certificate. The client certificate must be signed by the CA public certificate, which is imported into the MVISION Cloud Access Security Manager. If the Endpoint has the client certificate that is signed by the CA, MVISION Cloud considers the Endpoint managed and if the Endpoint does not have the client certificate signed by the CA, MVISION Cloud considers the Endpoint unmanaged.

MVISION Cloud proxy validates the certificate to identify the managed and unmanaged device. For a managed device, proxy instructs the client to go directly to Office 365. For an unmanaged device,  MVISION Cloud reverse proxy blocks the notification page.

NOTE: Before you configure Device Management for Office 365 with ADFS, make sure to redirect the traffic to MVISION Cloud. By default, ADFS and Office 365 uses WS-Fed authentication for SSO. To introduce MVISION Cloud in between endpoint and Office 365, you need to modify the settings in ADFS to redirect the traffic to MVISION Cloud for certificate validation.

Step 1: Configure ADFS

  1. Log In to the ADFS server and open ADFS Management.
    clipboard_ee55eb7da46c95c418b087943e474e0e5.png
  2. Expand the Trust Relationships tab and click Relying Party Trusts.
    clipboard_eab9be12caa502fdd10bfc63f19410acb.png
  3. Click Microsoft Office 365 Identity Platform and open properties. This option is created by default when you establish SSO with Office 365.
    clipboard_eee993e465fdb319638020e2ab488c386.png
  4. Go to the Endpoints tab and double click the WS-Federation Passive Endpoints URL and modify the trusted URL:

NOTES:

  • To get the URL specific to your tenant, contact MVISION Cloud Support.
  • Do not forget to append the “=” symbol towards the end of the new URL. This is an important parameter used to redirect the user to MVISION Cloud.
  1. To apply the settings, click OK.

NOTE: Before you begin to configure device management settings, verify whether your traffic is being redirected to MVISION Cloud Proxy from ADFS. If your traffic is redirected, then you can start with the next step.

Step 2: Configure Device Management for Office 365 in MVISION Cloud

  1. Log In to MVISION Cloud as admin.
  2. Go to Policy > Access Control > Device Management. 
  3. Under Establish Domain, enter the Original Domain as Device.
    clipboard_e96d3b002e07fe3bb427c64c80927a9a0.png
  4. Under Device Certificates, activate the Enable Certificate Checks and configure these fields:
    clipboard_eee7e5472f583bfb7f85b7fb4b93665a1.png
    • Upload Root Certificate (PEM Format). Browse and upload the CA certificate of MDM or CA authority provided by the customer.
    • Maximum chain depth. The chain depth number should be equal to the number of certificates in the chain.

NOTES:

  • If you have more than one certificate (Root and intermediates), combine all of them to make a certificate chain.
  • You don't have to activate the populated Device ID option only if you are performing the certificate checks and not integrating with MDM.
  • Publish tab is required only when you are performing SAML proxy with SAML as an authentication protocol. Portal registration should be turned off when you are performing only Certificate validation.
  1. Click Save Changes.
  • Was this article helpful?