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
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/concept-authentication-phone-options.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: active-directory
6
6
ms.service: active-directory
7
7
ms.subservice: authentication
8
8
ms.topic: conceptual
9
-
ms.date: 06/23/2023
9
+
ms.date: 07/17/2023
10
10
11
11
ms.author: justinha
12
12
author: justinha
@@ -23,15 +23,10 @@ For direct authentication using text message, you can [Configure and enable user
23
23
24
24
Users can also verify themselves using a mobile phone or office phone as secondary form of authentication used during Azure AD Multi-Factor Authentication or self-service password reset (SSPR).
25
25
26
-
> [!NOTE]
27
-
> Phone call verification is not available for Azure AD tenants with trial subscriptions. For example, signing up for a trial EMS licenses, will not provide the capability for phone call verification.
28
-
29
-
To work properly, phone numbers must be in the format *+CountryCode PhoneNumber*, for example, *+1 4251234567*.
30
-
31
-
> [!NOTE]
32
-
> There needs to be a space between the country/region code and the phone number.
33
-
>
34
-
> Password reset and Azure AD Multi-Factor Authentication support phone extensions only in office phone.
26
+
> [!NOTES]
27
+
> - Phone call verification isn't available for Azure AD tenants with trial subscriptions. For example, if you sign up for a trial Microsoft Enterprise Mobility and Security license, phone call verification isn't available.
28
+
> - Password reset and Azure AD Multi-Factor Authentication only support phone extensions for office phones.
29
+
> - Phone numbers must be provided in the format *+CountryCode PhoneNumber*, for example, *+1 4251234567*. There must be a space between the country/region code and the phone number.
35
30
36
31
## Mobile phone verification
37
32
@@ -44,7 +39,7 @@ If users don't want their mobile phone number to be visible in the directory but
44
39
Microsoft doesn't guarantee consistent SMS or voice-based Azure AD Multi-Factor Authentication prompt delivery by the same number. In the interest of our users, we may add or remove short codes at any time as we make route adjustments to improve SMS deliverability. Microsoft doesn't support short codes for countries/regions besides the United States and Canada.
45
40
46
41
> [!NOTE]
47
-
> Starting July 2023, we apply delivery method optimization such that tenants with a free or trial subscription may receive an SMS message or voice call.
42
+
> Starting July 2023, we will apply delivery method optimizations such that tenants with a free or trial subscription may receive an SMS message or voice call.
48
43
49
44
### SMS message verification
50
45
@@ -58,6 +53,8 @@ Android users can enable Rich Communication Services (RCS) on their devices. RCS
58
53
59
54
With phone call verification during SSPR or Azure AD Multi-Factor Authentication, an automated voice call is made to the phone number registered by the user. To complete the sign-in process, the user is prompted to press # on their keypad.
60
55
56
+
The calling number that a user receives the voice call from differs for each country. See [phone call settings](howto-mfa-mfasettings.md#phone-call-settings) to view all possible voice call numbers.
57
+
61
58
## Office phone verification
62
59
63
60
With office phone call verification during SSPR or Azure AD Multi-Factor Authentication, an automated voice call is made to the phone number registered by the user. To complete the sign-in process, the user is prompted to press # on their keypad.
0 commit comments