Have the ability to merge Adobe ID and Federated ID accounts

[tkat_it_-_0216]

I would like to have the ability to merge these ID types within the admin console when I have duplicated users. This merge should offer the ability to decide which (if any) Admin roles and licences should remain applied.

Types of Adobe identity

Adobe ID:

Created and managed by the individual end user. Authentication is performed by Adobe, and the user manages their own credentials at account.adobe.com. Users manage their own login credentials.

Federated ID:

Created, owned, and managed by the organization. Uses Single Sign-On (SSO) through a SAML2 identity provider (IdP). Examples include using Azure AD or Google Federation to authenticate users.

[Anshul_Nautiyal · Accepted solution]

Hi @tkat_it_-_0216,

Thanks for reaching out and sharing your feedback. Based on your post, it seems you’d like to have the ability to merge Adobe ID and Federated ID accounts directly within the Admin Console, especially in cases where duplicate users exist.

While merging Adobe ID and Federated ID accounts directly is not currently supported, Adobe provides a conversion workflow to transition users from Adobe ID to Federated ID. This process includes:

The supported path is to convert the user’s identity type and migrate assets, then reassign roles and licenses on the target account. The recommended workflow is to:

Prepare directories and SSO by setting up Federated ID and confirming identity configuration before migration. Check out this doc: https://adobe.ly/49eHoGC

Use Edit Identity Type by CSV to convert Adobe ID users to Federated ID in the same Admin Console organization, which enables automated asset migration when requirements are satisfied. You can check out these docs for this: https://adobe.ly/498Y9TH

https://adobe.ly/3J4BSMo

After conversion, verify sign-in with SSO and validate access to apps and services under the Federated ID.

If both an Adobe ID and Federated ID exist for the same person, complete identity conversion, finish asset migration, confirm access, then remove or deprovision the legacy Adobe ID from the organization. For cases where two separate emails exist, use manual transfer for assets and explicitly reassign all required product profiles and roles to the Federated ID. Check this doc: https://adobe.ly/4hfFVlF

Additionally, you can enforce Federated sign-in by applying Domain Enforcement to restrict Adobe ID use on claimed domains, preventing new Adobe IDs on the corporate email. Check out this doc: https://adobe.ly/46XlMxg

Thank you for sharing your feedback. It is valuable and will be shared with the relevant team for future consideration. Your input helps improve the overall product experience. 

Regards,
^AN