Zoom supports SAML 2.0 single sign-on with Microsoft Entra ID (formerly Azure AD). Once configured, your users sign into Zoom with their Microsoft credentials — the same ones they use for Outlook, Teams, and everything else in your Microsoft 365 environment. This eliminates separate Zoom passwords, gives you centralized access control through Entra ID, and lets you enforce conditional access policies (MFA, device compliance, location restrictions) on Zoom access.
What SSO Does Once Configured
Here’s exactly what happens after setup:
When a user signs into Zoom:
- User navigates to
yourcompany.zoom.usor opens the Zoom desktop client. - Zoom redirects them to Microsoft’s login page (or the user clicks “Sign in with SSO”).
- User authenticates with their Microsoft credentials (including MFA if configured).
- Microsoft sends a SAML assertion back to Zoom confirming the user’s identity.
- Zoom logs the user in — no separate Zoom password required.
What you control from Entra ID:
- Who can access Zoom — only users assigned to the Zoom enterprise app
- Conditional access — require MFA, compliant device, or specific network location
- Instant deprovisioning — disable a user in Entra ID and they immediately lose Zoom access
- Audit trail — every Zoom login appears in Entra ID sign-in logs
Prerequisites
- Microsoft Entra ID (any tier — Azure AD Free works for basic SAML, Premium P1 for conditional access)
- Zoom Business, Enterprise, or Education plan (Pro plan supports SSO but requires manual configuration)
- Zoom vanity URL configured (e.g.,
yourcompany.zoom.us) - Admin access to both the Azure portal and the Zoom web portal
Step 1: Configure Your Zoom Vanity URL
If you don’t already have a vanity URL, set one up first — SSO requires it.
- Sign in to the Zoom web portal as an admin.
- Go to Account Management > Account Profile.
- Under Vanity URL, enter your desired subdomain (e.g.,
yourcompany). - Click Save. Your vanity URL becomes
yourcompany.zoom.us.
Note: Vanity URL changes can take up to 24 hours to propagate. Set this up before starting the SSO configuration.
Step 2: Add Zoom as an Enterprise Application in Entra ID
- Sign in to the Azure portal.
- Navigate to Entra ID > Enterprise Applications.
- Click New application.
- Search for Zoom in the gallery — select Zoom Meetings (this is the pre-configured SAML template).
- Click Create.
- Once created, go to Single sign-on > select SAML.
Step 3: Configure SAML Settings in Azure
In the SAML configuration page:
Basic SAML Configuration
Click Edit and set:
| Field | Value |
|---|---|
| Identifier (Entity ID) | https://yourcompany.zoom.us |
| Reply URL (ACS URL) | https://yourcompany.zoom.us/saml/SSO |
| Sign on URL | https://yourcompany.zoom.us |
Click Save.
Attributes & Claims
Verify these user attribute mappings (most are pre-configured by the gallery template):
| Claim | Source attribute | Purpose |
|---|---|---|
| NameID | user.userprincipalname | Unique identifier for the user |
| firstName | user.givenname | First name in Zoom profile |
| lastName | user.surname | Last name in Zoom profile |
user.mail | Email address in Zoom profile |
Important: If your organization uses UPN format username@company.com that differs from the user’s actual email, map NameID to user.mail instead of user.userprincipalname. Zoom matches users by this value.
SAML Signing Certificate
- In the SAML Signing Certificate section, find Certificate (Base64) and click Download.
- Also copy the App Federation Metadata URL — you may need this for Zoom.
Copy These Values for Zoom
From the Set up Zoom Meetings section, copy:
| Azure Field | You’ll Paste This In Zoom As |
|---|---|
| Login URL | Sign-in page URL |
| Azure AD Identifier | Issuer (IDP entity ID) |
| Logout URL | Sign-out page URL |
Step 4: Configure SSO in Zoom
- Sign in to the Zoom web portal as an admin.
- Go to Advanced > Single Sign-On.
- If SSO is not yet enabled, click Enable Single Sign-On.
- Fill in the SAML configuration:
| Zoom Field | Value |
|---|---|
| Sign-in page URL | Login URL from Azure |
| Sign-out page URL | Logout URL from Azure |
| Identity provider certificate | Upload the Base64 certificate you downloaded from Azure |
| Service provider (SP) entity ID | https://yourcompany.zoom.us |
| Issuer (IDP entity ID) | Azure AD Identifier from Azure |
| Binding | HTTP-Redirect |
| Signature hash algorithm | SHA-256 |
- Under SAML Response Mapping, verify that
emailmaps correctly. - Click Save.
Step 5: Assign Users in Azure
Users must be assigned to the Zoom enterprise application in Entra ID to use SSO:
- In the Azure portal, go to Entra ID > Enterprise Applications > Zoom Meetings.
- Click Users and groups > Add user/group.
- Choose one of:
- Specific users — select individual users
- Groups — assign an Entra ID group (e.g., “All Employees” or “Zoom Users”)
- Click Assign.
Recommendation: Use a security group like “Zoom Licensed Users” so you can manage access through group membership rather than individual assignments.
Step 6: Test the SSO Connection
Test from Azure
- In the Azure portal, on the Zoom enterprise app’s SAML configuration page, scroll to the Test section.
- Click Test > Test sign in.
- Azure will attempt to sign into Zoom as your current user.
- If successful, you’ll see a confirmation. If not, Azure shows a detailed error.
Test from a Browser
- Open an incognito/private browser window.
- Navigate to
https://yourcompany.zoom.us. - Click Sign in with SSO (or you’ll be automatically redirected to Microsoft login).
- Enter your Microsoft credentials.
- You should be redirected back to Zoom and logged in.
Test from the Zoom Desktop Client
- Open Zoom desktop client.
- Click Sign In > SSO.
- Enter your company domain (e.g.,
yourcompany). - The Microsoft login page opens in a browser.
- After authenticating, the desktop client should show you as logged in.
Step 7: Configure Sign-In Methods (Optional but Recommended)
Once SSO is verified, lock down sign-in methods:
- In the Zoom web portal, go to Advanced > Security > Sign-in methods.
- Set Sign in with SSO to Required (disables password login).
- Keep Sign in with Google and Sign in with Apple disabled unless needed.
This ensures all users authenticate through Entra ID, giving you complete control over access.
Advanced: Conditional Access Policies
With Azure AD Premium P1, you can add security controls to Zoom access:
- In the Azure portal, go to Entra ID > Security > Conditional Access.
- Create a new policy targeting the Zoom Meetings enterprise app.
- Common policies:
| Policy | What It Does |
|---|---|
| Require MFA | Users must complete multi-factor authentication every time they sign into Zoom |
| Require compliant device | Only devices enrolled in Intune and meeting compliance policies can access Zoom |
| Block non-corporate networks | Users can only access Zoom from your corporate network or VPN |
| Require Terms of Use | Users must accept your organization’s ToU before accessing Zoom |
| Session lifetime | Force re-authentication after a set period (e.g., 12 hours) |
Common Issues
- “SAML response is invalid” — The Entity ID must match exactly between Azure and Zoom, including
https://and no trailing slash. Check both sides. Also verify the Reply URL ishttps://yourcompany.zoom.us/saml/SSO(case-sensitive). - Users get “account not found” — The user is not assigned to the Zoom enterprise app in Entra ID. Go to Enterprise Applications > Zoom > Users and groups and assign them. Also check that the email in the SAML assertion matches their Zoom account email.
- Users can’t edit their Zoom profile — This is expected with SSO. Profile fields (name, email) are locked because they’re managed by Entra ID. Users must update their name or email in Microsoft 365, and the changes will sync on next login.
- SSO works in browser but not in desktop client — The Zoom desktop client may need a sign-out and fresh SSO login. Go to the Zoom client settings > sign out > sign back in with SSO. Also check that the vanity URL domain is entered correctly (just
yourcompany, not the full URL). - Conditional access policy not applying — Verify the policy targets the “Zoom Meetings” enterprise application specifically, not just “All cloud apps.” Check the policy assignment (users/groups) and ensure the policy is enabled (not in report-only mode).
- SCIM and SSO confusion — SSO handles authentication (who can sign in). SCIM handles provisioning (creating/deactivating accounts). They are separate features. You can have SSO without SCIM (users must be manually created in Zoom first).