At VMware, we're always looking for new and innovative ways to help organizations simplify their IT operations and boost their Identity security posture. That's why we're excited to announce a new release that enables the use of cloud identities with Workspace ONE—welcome ! This new service utilizes System for Cross-domain Identity Management (SCIM) to provision users from cloud identity sources like Azure AD.
With VMware Identity Services, organizations can now centrally manage their cloud-based identities in Workspace ONE from a single interface, streamlining the process and reducing the risk of errors. Our SCIM-based solution automates the process of adding, updating, and removing user accounts and groups.
We have put together an overview to give you a head start on centralized user management, SCIM, and our new service.
Learn about the challenges faced by many companies nowadays and how SCIM offers a generalized way to address them while growing in popularity. We will look at the philosophy change happening inside the Workspace ONE platform as well as shifting from legacy integrations to a standardized solution.
The current release of the solution is the initial step on the VMware journey to improve user management in Workspace ONE and will be followed by continuous improvements to address all required use cases.
To learn more about the release, head over to VMware docs: VMware Identity Services Release Notes.
Setting up VMware Identity Services with Azure AD
The new service introduces a shift in managing and assigning administrators, users, and groups inside Workspace ONE. This video takes you through setting up administrators in VMware Cloud Services and then setting up end users for Workspace ONE UEM and Access by integrating Microsoft’s Azure AD as an Identity Source.
Setting up VMware Identity Services with Okta
Whilst Azure AD and its integration was the main target for the new service, we also included the capability to integrate with a generic SCIM 2.0 source. As an example of a generic SCIM 2.0 source, we stepped through the configurations required with Okta as an identity source.