Skip to content

Commit 80f153d

Browse files
Merge pull request #251335 from Justinha/sms-text-4
edits
2 parents 78fa121 + 36194f7 commit 80f153d

File tree

4 files changed

+17
-20
lines changed

4 files changed

+17
-20
lines changed

articles/active-directory/authentication/how-to-mfa-registration-campaign.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ In addition to choosing who can be nudged, you can define how many days a user c
6262

6363
![Confirmation of approval](./media/how-to-nudge-authenticator-app/approved.png)
6464

65-
1. Authenticator app is now successfully set up as the users default sign-in method.
65+
1. Authenticator app is now successfully set up as the user's default sign-in method.
6666

6767
![Installation complete](./media/how-to-nudge-authenticator-app/finish.png)
6868

@@ -88,7 +88,7 @@ In addition to using the Azure portal, you can also enable the registration camp
8888

8989
To configure the policy using Graph Explorer:
9090

91-
1. Sign in to Graph Explorer and ensure youve consented to the **Policy.Read.All** and **Policy.ReadWrite.AuthenticationMethod** permissions.
91+
1. Sign in to Graph Explorer and ensure you've consented to the **Policy.Read.All** and **Policy.ReadWrite.AuthenticationMethod** permissions.
9292

9393
To open the Permissions panel:
9494

articles/active-directory/authentication/howto-mfa-mfasettings.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ The following table lists more numbers for different countries.
206206
| Vietnam | +84 2039990161 |
207207

208208
> [!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-).
210210
211211
To configure your own caller ID number, complete the following steps:
212212

@@ -215,7 +215,7 @@ To configure your own caller ID number, complete the following steps:
215215
1. Select **Save**.
216216

217217
> [!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-).
219219
220220
### Custom voice messages
221221

articles/active-directory/authentication/multi-factor-authentication-faq.yml

Lines changed: 7 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ sections:
3434
* **Unique ID** (either user name or on-premises Multi-Factor Authentication Server ID)
3535
* **First and Last Name** (optional)
3636
* **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)
3838
* **Device Token** (when using mobile app authentication)
3939
* **Authentication Mode**
4040
* **Authentication Result**
@@ -49,27 +49,24 @@ sections:
4949
For more information, see [Data residency and customer data for Azure AD Multi-Factor Authentication](concept-mfa-data-residency.md).
5050
5151
- 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?
5353
answer: |
54-
In the United States, we use the following SMS short codes:
54+
In the United States, we use the following short codes:
5555
5656
* *97671*
5757
* *69829*
5858
* *51789*
5959
* *99399*
6060
61-
In Canada, we use the following SMS short codes:
61+
In Canada, we use the following short codes:
6262
6363
* *759731*
6464
* *673801*
6565
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.
6767
6868
We don't support short codes for countries or regions besides the United States and Canada.
6969
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-
7370
- question: |
7471
Does Azure AD Multi-Factor Authentication throttle user sign-ins?
7572
answer: |
@@ -135,7 +132,7 @@ sections:
135132
- question: |
136133
What should I tell my users to do if they don't receive a response on their phone?
137134
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.
139136
140137
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.
141138
@@ -168,7 +165,7 @@ sections:
168165
- question: |
169166
My users say that sometimes they don't receive the text message or the verification times out.
170167
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.
172169
173170
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.
174171

articles/active-directory/authentication/passwords-faq.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -95,25 +95,25 @@ sections:
9595
>
9696
> 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.
9797
>
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.
9999
>
100100
> Users can send an email a maximum of 10 times within a 10 minute period before they're locked out for 24 hours.
101101
>
102102
> The counters are reset once a user resets their password.
103103
>
104104
>
105105
- 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?
107107
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.
109109
> If you don't receive the notification in this time frame:
110110
> * Check your junk folder.
111111
> * Check that the number or email being contacted is the one you expect.
112112
> * Check that the authentication data in the directory is correctly formatted, for example, +1 4255551234 or *user\@contoso.com*.
113113
- question: |
114114
What languages are supported by password reset?
115115
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.
117117
>
118118
>
119119
- question: |
@@ -201,9 +201,9 @@ sections:
201201
>
202202
>
203203
- 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?
205205
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.
207207
>
208208
>
209209
- question: |

0 commit comments

Comments
 (0)