You have an Azure Active Directory (Azure AD) tenant named contoso.com. You plan to bulk invite Azure AD business-to-business (B2B) collaboration…

When performing a bulk invitation for Azure AD B2B collaboration users, a comma-separated values (CSV) file is used. According to the official Microsoft documentation, this CSV file template has two mandatory fields that must be populated for each user you want to invite. The first is the Invited user email address, which is the identity of the external user receiving the invitation. The second is the Redirection url, which is the location the user is sent to after they accept the invitation, such as a specific application or the My Apps portal.

C. username: The User Principal Name (UPN) for a B2B guest is automatically generated from their email address and is not a required input field in the bulk invite CSV file.

D. shared key: Shared keys are credentials used for service principals or applications and are not relevant to the process of inviting individual B2B collaboration users.

E. password: B2B collaboration users authenticate using the credentials from their home identity provider. The inviting tenant does not set or manage a password for them.

1. Microsoft Entra ID Documentation. "Tutorial: Bulk invite Azure AD B2B collaboration users." Microsoft Learn. Under the section "Understand the CSV template

" the table lists "Invited user email address" and "Redirection url" as Required. It states

"The email address of the user to invite" and "The URL to which the invited user is forwarded after accepting the invitation."

2. Microsoft Entra ID Documentation. "Properties of an Azure Active Directory B2B collaboration user." Microsoft Learn. This document clarifies that the User Principal Name (UPN) is typically constructed from the invited user's email address

confirming that the email address is the primary input. It also reinforces that authentication is handled by the user's home directory

making a password from the inviting tenant unnecessary.