Blog Post

Microsoft Entra Blog

2 MIN READ

Entra ID B2B collaboration direct federation with SAML and WS-Fed providers now in public preview

Microsoft

Jul 08, 2019

Howdy folks, We’ve been making it easier to work with your partners by enabling you to collaborate with them using their existing identities, regardless of whether they use Azure AD or not. We ...

Updated Dec 04, 2023

Version 9.0

Alex_Simons

Microsoft

Joined May 01, 2017

View Profile

Microsoft Entra Blog

Stay informed on how to secure access for any identity to any resource, anywhere, with comprehensive identity and network access solutions powered by AI.

Visit the homepage

NRuest

Copper Contributor

Aug 06, 2019

Thanks Maria_Lai. From what I understand, if my organization has a verified domain name such as Contoso.Com in Azure, then I cannot use direct federation. I may be wrong, but when I first obtain a subscription in Azure, my domain becomes contoso.onmicrosoft.com. When I add my verified DNS domain, contoso.com, to my subscription, it becomes a verified domain.

The documentation in the link I mentioned clearly states that direct federation does not work with verified DNS names. Does that apply to me as Contoso.com or does that apply to my partners, such as Woodgrove.com who would have verified their names in Azure?

To be clear, my goal is to have multiple partners (possibly over 100) interact with single sign on through direct federation in an Azure AD-based B2B environment to facilitate the use of resources that are accessed through this iteration of Azure AD. Am I going about this the right way?