Maintenance is being performed on Zoom's support site on November 4 that may cause support impact. For more information, please click here.
Everything you need to work together, all in one place.Explore Zoom One's Collaboration Tools
Connect virtually from anywhere with Zoom Meetings
Collaborate together with Zoom Chat
Call the world with Zoom Phone
Create and brainstorm with Zoom Whiteboard
Rich conversation analytics to improve sales
Send and receive messages and calendar invitations
Bring fluid interactions to hybrid teams with Zoom Huddles
Remove the hassle of traditional scheduling with Zoom Scheduler
Innovative video solutions for every meeting space.
Solutions to host impactful virtual and hybrid experiences.Find a Solution for Every Event
An omnichannel cloud solution optimized for video.
Zoom solutions elevate collaboration across vertical use cases.Discover Zoom Industry Solutions
Enabling exciting new ways to teach, learn, and connect globally
Transforming client engagement and employee experiences
Improving collaboration between agencies, ministries and constituents
Connecting care, collaboration, and medical innovation
Real-time communication, anywhere in the world
Bridging the in-store and online experiences
Expert support and services for all your design, strategy, implementation, event, and hardware needs.
An open platform that allows developers to build Zoom apps and integrations.
Zoom Partners bring Zoom's communications platform to market through alliance, sales, and service partnerships.
Discover new ways to use Zoom solutions to power your modern workforce.
Access expert-led tutorials on Zoom products and features.
Network with other Zoom users, and share your own product and industry insights.
Get documentation on deploying, managing, and using the Zoom platform.
I have a requirement to add a SAML Response Mapping to Employee Unique ID to avoid duplicate account creations when end users names change, specifically their email address. This causes duplicate account creation and consumes a Zoom pro license.
If I enter <NameID> into the SAML Response Mapping for Employee Unique ID, what is the net effect to the end users when signing into their Zoom account using SSO? Does <NameID> impact how end users authenticate using SSO or if they attempt to sign in with their email address and password at sign-on?
So using <NameID> (or anything else for that is constant and unique for the user) will have not impact on the user experience. The logic works like this:
1) First time the user signs in after you have mapped the Unique Id, it will associate that value to the user as their unique identifier.
2) User continues to use their email address to sign into SSO.
3) If in the future you change the user's email in your IdP, the user will start signing in using that email address. When the response comes back with a different email but the known Unique Id, it will update the user's email in Zoom.
4) If for some reason you have to change the unique id (e.g. you switch IdPs), the user has to sign in with the known email address and the new Unique Id will be associated to their account.
I hope this helps. If it answers your question, please click on 'Accept as Solution' below.
If I want the Azure EmployeeID attribute to be the Zoom Employee Unique ID how do I complete that mapping? I'm unclear on what needs to be entered in the Zoom Employee Unique ID field under SAML Response Mapping to make that happen.
Do I need to do some work on the Azure end first (e.g. create an additional claim)? Note, I've already followed the basic instructions and SSO is setup in Zoom but have yet to add any users via SSO.
We are working on implementing this and I have a follow-up question. On Step one, We already have 1,200 users and about 1,000 of them are SSO users. When we map the Unique ID, will it create a new account for those 1,000 SSO users? Or will it just sync their new Unique ID to their existing account and moving forward, should a name change occur, it will sync based off the Unique ID?
What unique ID is typically used in a windows Active Directory domain to keep duplicate accounts from being created? Putting <NameID> in the Unique ID field is not preventing the duplicate accounts from being created. I would think that a guid or sid or something like that would be preferred, but how do I reference that mapping?