Description
Ensure the OVHcloud account is connected to the organization's identity provider (for example Microsoft Entra ID, Okta, AD FS, or Google Workspace) through SAML single sign-on, so that users sign in with their company account and access is controlled centrally.
Rationale
With SSO, the company identity provider controls who can sign in, applies its MFA and access rules, and removes access as soon as a user is disabled. Without it, each person needs a separate OVHcloud login that must be managed by hand, so former staff may keep access.
Impact
Users sign in with their company account
Access is removed centrally when a user leaves
Groups in the identity provider must be mapped to OVHcloud groups
Default Value
By default, no SSO connection is configured.
Pre-Requisites
Access to the OVHcloud account owner login
Administrator access to the identity provider
The identity provider's SAML metadata
Test Plan
Log in to the OVHcloud Control Panel at https://www.ovh.com/manager/.
In the left-hand menu, select Identity, Security & Operations.
Under Identity and Access Management, select Identities.
Check whether an SSO connection is configured.
If no SSO connection exists, follow the implementation steps.
Implementation Steps
In your identity provider, create a SAML application for OVHcloud and download its metadata.
Log in to the OVHcloud Control Panel at https://www.ovh.com/manager/.
In the left-hand menu, select Identity, Security & Operations.
Under Identity and Access Management, select Identities.
Select the option to set up an SSO connection, paste the identity provider metadata, and enter the Group attribute name.
Choose whether to keep local OVHcloud users active (tick Keep active OVHcloud users if needed).
Add the identity provider groups to OVHcloud and grant them access through IAM policies.
Sign in with SSO to confirm it works.
Backout Plan
Log in to the OVHcloud Control Panel at https://www.ovh.com/manager/.
In the left-hand menu, select Identity, Security & Operations.
Under Identity and Access Management, select Identities.
Remove the SSO connection. Make sure the owner login or a local user can still sign in first.
Reference