Skip to content

Commit 5bf4cd0

Browse files
authored
Merge pull request #177663 from msmimart/mm-linkhp-edits
[EXID] Email one-time passcode edits from linkhp
2 parents fe43c1d + 441e347 commit 5bf4cd0

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

articles/active-directory/external-identities/one-time-passcode.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: how-to
10-
ms.date: 10/21/2021
10+
ms.date: 10/26/2021
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -154,7 +154,11 @@ For more information about current limitations, see [Azure US Government clouds]
154154

155155
**Why do I still see “Automatically enable email one-time passcode for guests starting October 2021” selected in my email one-time passcode settings?**
156156

157-
Due to our deployment schedules, we will start rolling out the change to enable email one-time passcode by default globally on November 1, 2021. Until then, you might still see “Automatically enable email one-time passcode for guests starting October 2021” selected in my email one-time passcode settings.
157+
Due to our deployment schedules, we will start rolling out the change to enable email one-time passcode by default globally on November 1, 2021. Until then, you might still see “Automatically enable email one-time passcode for guests starting October 2021” selected in your email one-time passcode settings.
158+
159+
**What happens to my existing guest users if I enable email one-time passcode?**
160+
161+
Your existing guest users will not be affected if you enable email one-time passcode, as your existing users are already past the point of redemption. Enabling email one-time passcode will only affect future redemption activities where new guest users are redeeming into the tenant.
158162

159163
**What is the user experience for guests during global rollout?**
160164

@@ -172,20 +176,20 @@ Before the change is rolled out to your region, guests will see the following be
172176

173177
- If a guest has an existing unmanaged Azure AD account, they'll continue signing in with their unmanaged Azure AD account.
174178
- If a guest previously redeemed an invitation to your tenant using an unmanaged Azure AD account, and you reset their redemption status and reinvite them, they'll continue signing in with their unmanaged Azure AD account.
175-
- If a guest doesn't have an existing unmanaged Azure AD account, they'll redeem using an email one-time passcode link, but they may get a sign-in error if they're not added to the Azure portal in advance.
179+
- If a guest doesn't have an existing unmanaged Azure AD account, they'll redeem using an unmanaged Azure AD account, but they may get a sign-in error if they're not added to the Azure portal in advance if redeeming on a direct application link.
176180

177181
After the change is rolled out to your region, guests will see the following behavior.
178182

179183
- With email one-time passcode enabled:
180184

181-
- If a guest has an existing unmanaged Azure AD account, they'll use email one-time passcode to redeem and sign in going forward.
185+
- If a guest has an existing unmanaged Azure AD account, they'll continue signing in with their unmanaged Azure AD account.
182186
- If a guest previously redeemed an invitation to your tenant using an unmanaged Azure AD account, and you reset their redemption status and reinvite them, they'll use email one-time passcode to redeem and sign in going forward.
183187
- If a guest doesn't have an unmanaged Azure AD account, they'll use email one-time passcode to redeem and sign in going forward.
184188

185189
- With email one-time passcode disabled:
186190

187-
- If a guest has an existing unmanaged Azure AD account, they'll use a Microsoft account to redeem. They'll end up with two accounts (the unmanaged Azure AD account and the Microsoft account). To prevent this from happening, we strongly encourage you to enable email one-time passcode.
188-
- If a guest previously redeemed an invitation to your tenant using an unmanaged Azure AD account, and you reset their redemption status and reinvite them, they'll use a Microsoft account to redeem. They'll end up with two accounts (the unmanaged Azure AD account and the Microsoft account). To prevent this from happening, we strongly encourage you to enable email one-time passcode.
191+
- If a guest has an existing unmanaged Azure AD account, they'll continue signing in with their unmanaged Azure AD account.
192+
- If a guest previously redeemed an invitation to your tenant using an unmanaged Azure AD account, and you reset their redemption status and reinvite them, they'll use a Microsoft account to redeem and sign in going forward.
189193
- If a guest doesn't have an unmanaged Azure AD account, they'll use a Microsoft account to redeem and sign in going forward.
190194

191195
For more information about the different redemption pathways, see [B2B collaboration invitation redemption](redemption-experience.md).

0 commit comments

Comments
 (0)