Spent months figuring out why federated SSO breaks for external users accessing Azure Virtual Desktop. Turns out Azure AD ignores custom federation when the user's domain is verified elsewhere—forces B2B routing, kills Windows SSO.
Built a workaround using proxy domains and a federation hub.
Curious—how are others solving this? Or just telling customers SSO isn't possible? I can't find any roadmap agenda.
No CommentsBe the first to comment