You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next, update the parameters file with the values you recorded earlier. The following JSON snippet shows an example of an Azure Resource Manager template parameters file. For `authorizations.value.roleDefinitionId`, use the [built-in role](../role-based-access-control/built-in-roles.md) value for the *Contributor role*, `b24988ac-6180-42a0-ab88-20f7382dd24c`.
# The elements of the B2B collaboration invitation email - Azure Active Directory
20
20
21
-
Invitation emails are a critical component to bring partners on board as B2B collaboration users in Azure AD. You can use them to increase the recipient's trust. you can add legitimacy and social proof to the email, to make sure the recipient feels comfortable with selecting the **Get Started** button to accept the invitation. This trust is a key means to reduce sharing friction. And you also want to make the email look great!
21
+
Invitation emails are a critical component to bring partners on board as B2B collaboration users in Azure AD. While it’s [not required that you send an email to invite someone using B2B collaboration](add-user-without-invite.md), doing so gives the user all the information they need to make a decision about whether to accept your invite. It also gives them a link they can always refer to in the future when they need to return to your resources.
22
22
23
23
24
24
25
+
> [!NOTE]
26
+
> This new email template is still being rolled out to all tenants, so some tenants are still using an older design. By the end of May 2020, invitations from all tenants will be using this template.
27
+
25
28
## Explaining the email
29
+
26
30
Let's look at a few elements of the email so you know how best to use their capabilities.
27
31
28
32
### Subject
29
-
The subject of the email follows the following pattern:
30
-
You're invited to the <tenantname> organization
33
+
34
+
The subject of the email follows this pattern:
35
+
36
+
<username> invited you to access applications within their organization.
31
37
32
38
### From address
33
-
We use a LinkedIn-like pattern for the From address. You should be clear who the inviter is and from which company, and also clarify that the email is coming from a Microsoft email address. The format is: Microsoft Invitations <[email protected]> or
34
-
<Display name of inviter>from <tenantname> (via Microsoft) <[email protected]>.
39
+
40
+
We use a LinkedIn-like pattern for the From address. This pattern should make it clear that although the email comes from [email protected], the invitation is from another organization. The format is: Microsoft Invitations <[email protected]> or Microsoft invitations on behalf of <tenantname><[email protected]>.
35
41
36
42
### Reply To
43
+
37
44
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.
38
45
39
-
### Branding
40
-
The invitation emails from your tenant use the company branding that you may have set up for your tenant. If you want to take advantage of this capability, [here](https://docs.microsoft.com/azure/active-directory/active-directory-branding-custom-signon-azure-portal) are the details on how to configure it. The banner logo appears in the email. Follow the image size and quality instructions [here](https://docs.microsoft.com/azure/active-directory/active-directory-branding-custom-signon-azure-portal) for best results. In addition, the company name also shows up in the call to action.
46
+
### Phishing warning
41
47
42
-
### Call to action
43
-
The call to action consists of two parts: explaining why the recipient has received the mail and what the recipient is being asked to do about it.
44
-
- The "why" section can be addressed using the following pattern:
45
-
You've been invited to access applications in the <tenantname> organization
48
+
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 make sure the partners you’re inviting will not be surprised by your invitation by mentioning it to them ahead of time.
46
49
47
-
- And the "what you're being asked to do" section is indicated by the presence of the **Get Started** button. When the recipient has been added without the need for invitations, this button doesn't show up.
50
+
48
51
49
52
### Inviter's information
50
-
The inviter's display name is included in the email. And in addition, if you've set up a profile picture for your Azure AD account, the inviting email will include that picture as well. Both are intended to increase your recipient's confidence in the email.
51
53
52
-
If you haven't yet set up your profile picture, an icon with the inviter's initials in place of the picture is shown:
54
+
The email includes information about the inviter and the organization they’re sending the invitation from. This includes the sender’s name and email address, as well as the name and primary domain associated with the organization. All of this information should help the invitee make an informed decision about accepting the invitation.
53
55
54
-
56
+
55
57
56
-
### Body
57
-
The body contains the message that the inviter composes when [inviting a guest user to the directory, group, or app](add-users-administrator.md) or [by using the invitation API](customize-invitation-api.md). It is a text area, so it does not process HTML tags for security reasons.
58
+
### Invitation message
58
59
59
-
60
+
If the inviter includes a message as part of their invitation when they [invite a guest user to the directory, group, or app](add-users-administrator.md) or when they [use the invitation API](customize-invitation-api.md), the message is highlighted in the main section of the email. Also included are the inviter’s name and profile image if they’ve set one. The message itself is a text area, so for security reasons, it doesn't process HTML tags.
60
61
61
-
### Footer section
62
-
The footer contains the Microsoft company brand and lets the recipient know if the email was sent from an unmonitored alias.
63
-
64
-
Special cases:
62
+
65
63
66
-
- The inviter doesn't have an email address in the inviting tenancy
64
+
### Accept button and redirect URL
67
65
68
-
66
+
The next section of the email contains information about where the invitee will be taken after they accept the invitation, as well as a button to do so. In the future, the invitee can always use this link to return to your resources directly.
69
67
68
+
70
69
71
-
- The recipient doesn't need to redeem the invitation
70
+
### Footer section
72
71
73
-
72
+
The footer contains more information about the invitation being sent. There is always an option for the invitee to block future invitations. If the organization has [set a privacy statement](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-properties-area), the link to the statement is displayed here. Otherwise, a note indicates the organization hasn't set a privacy statement.
74
73
74
+
75
+
75
76
## How the language is determined
76
-
The language presented to the guest user in the invitation email is determined by the following settings. These settings are listed in order of precedence. If a setting isn’t configured, the next setting in the list determines the language.
77
+
78
+
The language presented to the guest user in the invitation email is determined by the following settings. These settings are listed in order of precedence. If a setting isn’t configured, the next setting in the list determines the language.
79
+
77
80
- The **messageLanguage** property of the [invitedUserMessageInfo](https://docs.microsoft.com/graph/api/resources/invitedusermessageinfo?view=graph-rest-1.0) object if the Create invitation API is used
78
81
- The **preferredLanguage** property specified in the guest's [user object](https://docs.microsoft.com/graph/api/resources/user?view=graph-rest-1.0)
79
82
- The **Notification language** set in the properties of the guest user’s home tenant (for Azure AD tenants only)
0 commit comments