Edit

Share via

B2B invitation email layout and language settings

  • Article

Applies to: Green circle with a white check mark symbol. Workforce tenants White circle with a gray X symbol. External tenants (learn more)

Invitation emails play a key role in welcoming partners as Microsoft Entra B2B collaboration users. While not mandatory, these emails provide essential information to help recipients make an informed decision about accepting your invitation. They also include a link for easy future access to your resources.

Screenshot showing the B2B invitation email.

Explaining the email

Let's look at a few elements of the email so you know how best to use their capabilities. These elements might look slightly different in some email clients.

Subject

The subject of the email follows this pattern:

<username> invited you to access applications within their organization.

From address

We use a LinkedIn-like pattern for the From address. This pattern should make it clear that although the email comes from invites@microsoft.com, the invitation is from another organization. The format is: Microsoft Invitations invites@microsoft.com or Microsoft invitations on behalf of <tenantname> invites@microsoft.com.

Note

For the Azure service operated by 21Vianet in China, the sender address is Invites@oe.21vianet.com.
For Microsoft Entra ID for government, the sender address is invites@azuread.us.

Reply To

The reply-to email is set to the inviter's email when available, so that replying to the email sends an email back to the inviter.

Phishing warning

The email starts with a brief warning to the user about phishing, alerting them that they should only accept invitations they're expecting. It’s good practice to let partners know in advance to expect your invitation.

Screenshot of the phishing warning in the email.

Inviter's information and invitation message

The email includes the name and primary domain associated with the organization sending the invitation. This information should help the invitee make an informed decision about accepting the invitation. The inviter can include a message as part of their invitation to the directory, group, or app, or when they use the invitation API. The message is highlighted in the main section of the email. The inviter’s name and profile image are also included if they have one. The message itself is a text area, so for security reasons, it doesn't process HTML tags.

Screenshot of the invitation message in the email.

The next section of the email contains information about where the invitee will be taken after they accept the invitation, and a button or link to do so. In the future, the invitee can always use this link to return to your resources directly.

Screenshot of the accept button and redirect URL in the email.

The footer contains more information about the invitation being sent. If the organization configured a privacy statement, the link to the statement is displayed here. Otherwise, a note indicates the organization's privacy statement isn't available.

Screenshot showing the footer section in the email.

How the language is determined

The following settings determine the language that is presented to the guest user in the invitation email. These settings are listed in order of precedence. If a setting isn’t configured, the next setting in the list determines the language.

  • The messageLanguage property of the invitedUserMessageInfo object if the Create invitation API is used
  • The preferredLanguage property specified in the guest's user object
  • The Notification language set in the properties of the guest user’s home tenant (for Microsoft Entra tenants only)
  • The Notification language set in the properties of the resource tenant

If none of these settings are configured, the language defaults to English (US).

Next steps