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/howto-mfa-mfasettings.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -206,7 +206,7 @@ The following table lists more numbers for different countries.
206
206
| Vietnam | +84 2039990161 |
207
207
208
208
> [!NOTE]
209
-
> When Azure AD Multi-Factor Authentication calls are placed through the public telephone network, sometimes the calls are routed through a carrier that doesn't support caller ID. Because of this, caller ID isn't guaranteed, even though Azure AD Multi-Factor Authentication always sends it. This applies both to phone calls and text messages provided by Azure AD Multi-Factor Authentication. If you need to validate that a text message is from Azure AD Multi-Factor Authentication, see [What SMS short codes are used for sending messages?](multi-factor-authentication-faq.yml#what-sms-short-codes-are-used-for-sending-sms-messages-to-my-users-).
209
+
> When Azure AD Multi-Factor Authentication calls are placed through the public telephone network, sometimes the calls are routed through a carrier that doesn't support caller ID. Because of this, caller ID isn't guaranteed, even though Azure AD Multi-Factor Authentication always sends it. This applies both to phone calls and text messages provided by Azure AD Multi-Factor Authentication. If you need to validate that a text message is from Azure AD Multi-Factor Authentication, see [What short codes are used for sending messages?](multi-factor-authentication-faq.yml#what-short-codes-are-used-for-sending-text-messages-to-my-users-).
210
210
211
211
To configure your own caller ID number, complete the following steps:
212
212
@@ -215,7 +215,7 @@ To configure your own caller ID number, complete the following steps:
215
215
1. Select **Save**.
216
216
217
217
> [!NOTE]
218
-
> When Azure AD Multi-Factor Authentication calls are placed through the public telephone network, sometimes the calls are routed through a carrier that doesn't support caller ID. Because of this, caller ID isn't guaranteed, even though Azure AD Multi-Factor Authentication always sends it. This applies both to phone calls and text messages provided by Azure AD Multi-Factor Authentication. If you need to validate that a text message is from Azure AD Multi-Factor Authentication, see [What SMS short codes are used for sending messages?](multi-factor-authentication-faq.yml#what-sms-short-codes-are-used-for-sending-sms-messages-to-my-users-).
218
+
> When Azure AD Multi-Factor Authentication calls are placed through the public telephone network, sometimes the calls are routed through a carrier that doesn't support caller ID. Because of this, caller ID isn't guaranteed, even though Azure AD Multi-Factor Authentication always sends it. This applies both to phone calls and text messages provided by Azure AD Multi-Factor Authentication. If you need to validate that a text message is from Azure AD Multi-Factor Authentication, see [What short codes are used for sending messages?](multi-factor-authentication-faq.yml#what-short-codes-are-used-for-sending-text-messages-to-my-users-).
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/multi-factor-authentication-faq.yml
+7-10Lines changed: 7 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ sections:
34
34
* **Unique ID** (either user name or on-premises Multi-Factor Authentication Server ID)
35
35
* **First and Last Name** (optional)
36
36
* **Email Address** (optional)
37
-
* **Phone Number** (when using a voice call or SMS authentication)
37
+
* **Phone Number** (when using a voice call or text message authentication)
38
38
* **Device Token** (when using mobile app authentication)
39
39
* **Authentication Mode**
40
40
* **Authentication Result**
@@ -49,27 +49,24 @@ sections:
49
49
For more information, see [Data residency and customer data for Azure AD Multi-Factor Authentication](concept-mfa-data-residency.md).
50
50
51
51
- question: |
52
-
What SMS short codes are used for sending SMS messages to my users?
52
+
What short codes are used for sending text messages to my users?
53
53
answer: |
54
-
In the United States, we use the following SMS short codes:
54
+
In the United States, we use the following short codes:
55
55
56
56
* *97671*
57
57
* *69829*
58
58
* *51789*
59
59
* *99399*
60
60
61
-
In Canada, we use the following SMS short codes:
61
+
In Canada, we use the following short codes:
62
62
63
63
* *759731*
64
64
* *673801*
65
65
66
-
There's no guarantee of consistent SMS or voice-based 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.
66
+
There's no guarantee of consistent text message or voice-based multifactor 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 text message deliverability.
67
67
68
68
We don't support short codes for countries or regions besides the United States and Canada.
69
69
70
-
## Billing
71
-
Most billing questions can be answered by referring to either the [Multi-Factor Authentication Pricing page](https://azure.microsoft.com/pricing/details/multi-factor-authentication/) or the documentation for [Azure AD Multi-Factor Authentication versions and consumption plans](concept-mfa-licensing.md).
72
-
73
70
- question: |
74
71
Does Azure AD Multi-Factor Authentication throttle user sign-ins?
75
72
answer: |
@@ -135,7 +132,7 @@ sections:
135
132
- question: |
136
133
What should I tell my users to do if they don't receive a response on their phone?
137
134
answer: |
138
-
Have your users attempt up to five times in 5 minutes to get a phone call or SMS for authentication. Microsoft uses multiple providers for delivering calls and SMS messages. If this approach doesn't work, open a support case to troubleshoot further.
135
+
Have your users attempt up to five times in 5 minutes to get a phone call or text message for authentication. Microsoft uses multiple providers for delivering calls and text messages. If this approach doesn't work, open a support case to troubleshoot further.
139
136
140
137
Third-party security apps may also block the verification code text message or phone call. If using a third-party security app, try disabling the protection, then request another MFA verification code be sent.
141
138
@@ -168,7 +165,7 @@ sections:
168
165
- question: |
169
166
My users say that sometimes they don't receive the text message or the verification times out.
170
167
answer: |
171
-
Delivery of SMS messages aren't guaranteed because there are uncontrollable factors that might affect the reliability of the service. These factors include the destination country or region, the mobile phone carrier, and the signal strength.
168
+
Delivery of text messages isn't guaranteed because uncontrollable factors might affect the reliability of the service. These factors include the destination country or region, the mobile phone carrier, and the signal strength.
172
169
173
170
Third-party security apps may also block the verification code text message or phone call. If using a third-party security app, try disabling the protection, then request another MFA verification code be sent.
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/passwords-faq.yml
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -95,25 +95,25 @@ sections:
95
95
>
96
96
> Users can attempt to validate their information (such as their phone number), but if they're unable to prove their identity five times within a 24-hour period, they're locked out for 24 hours.
97
97
>
98
-
> Users can try to validate a phone number, auth app, send a SMS, or validate security questions and answers only five times within an hour before they're locked out for 24 hours.
98
+
> Users can try to validate a phone number, auth app, send a text message, or validate security questions and answers only five times within an hour before they're locked out for 24 hours.
99
99
>
100
100
> Users can send an email a maximum of 10 times within a 10 minute period before they're locked out for 24 hours.
101
101
>
102
102
> The counters are reset once a user resets their password.
103
103
>
104
104
>
105
105
- question: |
106
-
How long should I wait to receive an email, SMS, or phone call from password reset?
106
+
How long should I wait to receive an email, text message, or phone call from password reset?
107
107
answer: |
108
-
> Emails, SMS messages, and phone calls should arrive in under a minute. The normal case is 5 to 20 seconds.
108
+
> Emails, text messages, and phone calls should arrive in under a minute. The normal case is 5 to 20 seconds.
109
109
> If you don't receive the notification in this time frame:
110
110
> * Check your junk folder.
111
111
> * Check that the number or email being contacted is the one you expect.
112
112
> * Check that the authentication data in the directory is correctly formatted, for example, +1 4255551234 or *user\@contoso.com*.
113
113
- question: |
114
114
What languages are supported by password reset?
115
115
answer: |
116
-
> The password reset UI, SMS messages, and voice calls are localized in the same languages that are supported in Microsoft 365.
116
+
> The password reset UI, text messages, and voice calls are localized in the same languages that are supported in Microsoft 365.
117
117
>
118
118
>
119
119
- question: |
@@ -201,9 +201,9 @@ sections:
201
201
>
202
202
>
203
203
- question: |
204
-
How long are the email and SMS one-time passcodes valid?
204
+
How long are the email and text message one-time passcodes valid?
205
205
answer: |
206
-
> The session lifetime for password reset is 15 minutes. From the start of the password reset operation, the user has 15 minutes to reset their password. The email and SMS one-time passcode are valid for 5 minutes during the password reset session.
206
+
> The session lifetime for password reset is 15 minutes. From the start of the password reset operation, the user has 15 minutes to reset their password. The one-time passcodes are valid for 5 minutes during the password reset session.
0 commit comments