Adobe Experience Cloud
AEM Cloud author SSO needs an IMS migration plan
Plan the author login handoff when moving from Azure OAuth on AEM Managed Services to AEM as a Cloud Service.
November 10, 2026
An AEM team moving from Managed Services may already have Azure-based author login working. A community migration question asks whether that same OAuth setup can serve AEM as a Cloud Service authors. The answer affects access, launch timing and support ownership.
Separate the user experience from the protocol
Adobe's authentication matrix lists Adobe IMS and SAML through Adobe IMS for Author, while direct OAuth and OIDC are listed for Publish, not Author. An author can still experience company SSO, but the trust path changes. Adobe's IMS guidance describes federation through the Admin Console.
Inventory current author groups, identity domains, service accounts and automated integrations. Do not infer that an integration token and a human author session need the same migration path. Record who manages Entra ID, Adobe Admin Console and AEM product profiles.
Prove access before moving content
Test a representative author, administrator and external collaborator in a nonproduction Cloud environment. Verify sign-in, group mapping, permissions, logout and account recovery. Keep the old and new access routes documented until cutover. A successful redirect alone does not prove the author can open the right Sites or Assets workspace.
If an identity exception appears, trace it across the IdP assertion, Adobe IMS identity and Admin Console entitlement before changing AEM permissions. Make the test evidence part of the migration acceptance criteria.
Adovo’s view
Identity is part of the content supply chain. A migration is not ready when only the pages move; the people who govern them must be able to work on day one. Design the author access path early, then rehearse it with real roles.
