An organization implements Microsoft Entra ID Governance entitlement management for a partner company that needs access to an AI analytics portal. The partner company does not have Microsoft Entra ID. How should external access be configured?

Create a connected organization in Entitlement Management pointing to the partner's email domain and configure an access policy for external requestors. Microsoft Entra ID Governance Entitlement Management supports connected organizations, which can be configured with a partner company's verified domain. Access package policies can include a 'for users not in your directory' option that allows external users from the connected organization's domain to request access. When approved, they are invited as business-to-business guests with automatic access package provisioning. Creating local Entra ID accounts for all partner company employees and adding them to the access package is incorrect because it bypasses the partner's own identity management and creates an administrative burden. Configuring the access package to allow requests from users not yet in the directory, enabling business-to-business guest invitation during access request, is incorrect because while it enables guest invitations, configuring a connected organization first provides better governance with pre-verified domain trust. Setting up Microsoft Entra External ID customer identity and configuring the AI analytics portal to use it for partner authentication is incorrect because Microsoft Entra External ID customer identity is designed for customer/consumer identity scenarios with social logins, not for business-to-business partner access to enterprise applications.