How to enable SSO with ADFS?


The high-level steps involved in configuring Zoom for SSO with ADFS are:

  1. Obtain your institutional ADFS SAML metadata (.xml)
  2. Using your Zoom admin account, access the Zoom SSO configuration page and enable SSO
  3. Open the “SAML” tab and enter your institutional SAML metadata (obtained from your ADFS SAML metadata file .xml )
  4. Access your institutional ADFS configuration interface
  5. Configure the source of SAML relying-party metadata
  6. Configure the relying-party display name as “Zoom”
  7. Configure relying-party Assertion Consumer and Logout end-points
  8. Add claim rules:
    1. Map and send attributes for E-Mail-Addresses, User-Principal-Name, Given-Name and Surname.
    2. Configure E-Mail Address as the Name ID outgoing claim type
  9. Test SSO to Zoom

Detailed Steps

  1. Find and download/view your ADFS XML metadata at https://[SERVER]/FederationMetadata/2007-06/FederationMetadata.xml. 
    * [SERVER] is the domain name of your ADFS server (e.g.
  2. From the Zoom Admin page, click on Single Sign-On to vide the SAML tab.
  3. Enter the following information into the SAML tab options:
    1. Sign-in page URL: https://[SERVER]/adfs/ls/idpinitiatedsignon.aspx?logintoRP=[VANITY]
    2. Sign-out page URL: https://[SERVER]/adfs/ls/?wa=wsignout1.0
    3. Identity provider certificate: Note, use the "Signing" certificate.
      * Use the first X509 Certificate in the FederationMetadata.xml file (Step 1)

      <ds:Signature xmlns:ds=""> <KeyInfo zmlns="">

      <X509Data> <X509Certificate>

    4. Issuer: http or https://[SERVER]/adfs/services/trust (entityID in metadata - Step 1)
    5. Binding: HTTP-POST
    6. Default user type: Basic or Corp
  4. Login to you ADFS server, open ADFS 2.0 MMC.
    Open the administrative interface of ADFS.
  5. Add a Relying Party Trust
    Select Import data about the relying party published online or on a local netowrk
    Federation metadata address: https://[VANITY]
  6. Add a display name ("Zoom") and finish the Wizard with the default settings.
  7. Change both Redirect and Post SAML Logout Endpoint URLs to:
    (Right click the new Relying Party Trust > Properties > Endpoints tab)

    * Note: If you are unable to change the logout andpoints, open the Monitor tab and uncheck "Automatically update relying party" and Apply changes.
  8. Add two claim rules
    1. First claim rule ...
      Type: Send LDAP Attributes as Claims
      Name: Zoom-Send to Email
      E-Mail-Addresses > E-Mail Address
      User-Principal-Name > UPN
      Given-Name > urn:oid:
      Surname > urn:oid:

      * if User-Principal-Name has email format and is different from E-Mail-Address, you may want to map the User-Principal-Name to E-Mail Address ...
    2. Second claim rule ...
      Type: Transform Incoming Claim
      Name: Zoom-Email to Name ID
      Incoming claim type: E-Mail Address
      Outgoing claim type: Name ID
      Outgoing name ID format: Email
  9. Test SSO by visiting https://[VANITY]
    You should see your institutional login screen.

Troubleshooting Tips

Issue 1: Unable to log in using Google Chrome or Firefox

If you are unable to log in using Chrome or Firefox, and are seeing an 'Audit Failure' event with "Status: 0xc000035b" in the Event Viewer on the ADFS server, you will need to turn off Extended Protection. Chrome and Firefox do not support the Extended Protection of ADFS (IE does).

  1. Launch IIS Manager
  2. In the left panel, navigate to Sites > Default Web Site > ADFS > LS
  3. Double-click Authentication icon
  4. Right-click Windows Authentication
  5. Select Advanced Settings
  6. Turn OFF Extended Protection.