> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pd-ag/getting-started/configuring-the-single-sign-on-sso-integration-with-parallels-my-account.md). # \[OPTIONAL] Configuring the Single Sign-On (SSO) integration with Parallels My Account Integration between Parallels My Account and corporate Identity Providers (IdP) like Microsoft Entra ID, Okta, Ping Identity, JumpCloud, or Google Workspace enables Single Sign-On (SSO) login to Parallels My Account and automatic provisioning and revocation of Parallels product licenses to end users in your organization. The organization’s business account admins can log into [My Account](https://my.parallels.com/) using their company's standard authentication procedure, while the end-users can activate Parallels products on their devices via Single Sign-On. {% hint style="info" %} **Note**: In the case of Parallels Desktop for Mac Enterprise Edition, a mixed licensing policy enables administrators to combine fixed per-device license seats and SSO per-user license seats as they see fit. {% endhint %} Even if your organization does not use Parallels Desktop for Mac Enterprise Edition, you may benefit from the SSO integration with My Account. Such integration provides more control over the users with administrative access to the Parallels product licenses stored in the organization’s business account registered with Parallels. {% hint style="danger" %} **Warning**: Once you have completed the integration process and activated the SSO functionality, only users from the Administrators group in your IdP signing in via SSO will retain access to managing the Parallels business account. All previous administrative privileges based on logins and passwords will become inactive. Your designated backup login will continue to work. {% endhint %} Once the integration is configured, you can grant access to the organization’s business account to administrators by adding them to the Parallels Business Account Admins group in your Identity Provider’s directory. At the same time, deleting or blocking an administrator account in your Identity Provider automatically deprives them of access to Parallels My Account. {% hint style="info" %} **Note:** The integration between Parallels My Account and IdPs relies on SAML 2.0 for SSO and SCIM 2.0 for user identity information synchronization. {% endhint %} In this section, we provide detailed instructions on how to set up the SSO integration with Microsoft Azure/Entra ID, Okta, and Ping Identity. Even if your corporate identity provider is not on the list, you can still try setting up the integration, provided your service of choice supports SAML 2.0 and SCIM 2.0 protocols. Once the integration is completed, the administrators will be able to sign into the company's My Account page using the **Continue with SSO** button at , while Parallels Desktop for Mac users will be able to activate their local copies of the app using the SSO option. {% hint style="info" %} **Note**: If members of the Admin group need to also be able to use Parallels Desktop for Mac, they should be explicitly added to the Parallels Desktop users group. {% endhint %} Below is the chart that outlines the setup process. Please note that the [multi-group setup](/landing/pd-ag/getting-started/configuring-the-single-sign-on-sso-integration-with-parallels-my-account/optional-how-to-divide-users-into-groups-and-assign-them-sublicenses.md) is optional.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.parallels.com/landing/pd-ag/getting-started/configuring-the-single-sign-on-sso-integration-with-parallels-my-account.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.