Jason-Ra I see a few questions - 1. Is it going to work with Identity governance and Lifecycle management. Looking ahead, we do plan to integrate the External Identities flow with the Identity Governance features of Azure AD including lifecycle management for guests. 2. Is this going to work when the other org isn't Azure AD? We currently have functionality that supports direct federation with non Azure AD orgs (via SAML, WS-Fed) in public preview. We are working to make sure future extensibility is available to all types of users. 3. Is this going to replace lifecycle management? No, it won't replace lifecycle management. The API connectors function can be used for a variety of scenarios including ID verification and if desired, connecting with an internal process such as a company's bespoke lifecycle management system (UI strings in this post are representative of how the system can be configured by a customer).