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-methods.md
+27-6Lines changed: 27 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
2
title: Authentication methods - Azure Active Directory
3
-
description: What authentication methods are available in Azure AD for MFA and SSPR
3
+
description: Authentication methods available in Azure AD for MFA and SSPR
4
4
5
5
services: active-directory
6
6
ms.service: active-directory
7
7
ms.subservice: authentication
8
8
ms.topic: conceptual
9
-
ms.date: 02/20/2019
9
+
ms.date: 06/17/2019
10
10
11
11
ms.author: joflore
12
12
author: MicrosoftGuyJFlo
@@ -177,7 +177,9 @@ Once any errors have been addressed, the administrator then can activate each ke
177
177
178
178
Users may have a combination of up to five OATH hardware tokens or authenticator applications such as the Microsoft Authenticator app configured for use at any time.
179
179
180
-
## Mobile phone
180
+
## Phone options
181
+
182
+
### Mobile phone
181
183
182
184
Two options are available to users with mobile phones.
183
185
@@ -190,18 +192,18 @@ To work properly, phone numbers must be in the format *+CountryCode PhoneNumber*
190
192
>
191
193
> Password reset does not support phone extensions. Even in the +1 4255551234X12345 format, extensions are removed before the call is placed.
192
194
193
-
### Text message
195
+
####Text message
194
196
195
197
An SMS is sent to the mobile phone number containing a verification code. Enter the verification code provided in the sign-in interface to continue.
196
198
197
-
### Phone call
199
+
####Phone call
198
200
199
201
An automated voice call is made to the phone number you provide. Answer the call and press # in the phone keypad to authenticate
200
202
201
203
> [!IMPORTANT]
202
204
> Starting in March of 2019 the phone call options will not be available to MFA and SSPR users in free/trial Azure AD tenants. SMS messages are not impacted by this change. Phone call will continue to be available to users in paid Azure AD tenants. This change only impacts free/trial Azure AD tenants.
203
205
204
-
## Office phone
206
+
###Office phone
205
207
206
208
An automated voice call is made to the phone number you provide. Answer the call and presses # in the phone keypad to authenticate.
207
209
@@ -217,6 +219,25 @@ The office phone attribute is managed by your administrator.
217
219
>
218
220
> Password reset does not support phone extensions. Even in the +1 4255551234X12345 format, extensions are removed before the call is placed.
219
221
222
+
### Troubleshooting phone options
223
+
224
+
Common problems related to authentication methods using a phone number:
225
+
226
+
* Blocked caller ID on a single device
227
+
* Troubleshoot device
228
+
* Wrong phone number, incorrect country code, home phone number versus work phone number
229
+
* Troubleshoot user object and configured authentication methods. Ensure correct phone numbers are registered.
230
+
* Wrong PIN entered
231
+
* Confirm user has used the correct PIN registered in Azure MFA Server.
232
+
* Call forwarded to voicemail
233
+
* Ensure user has phone turned on and that service is available in their area or use alternate method.
234
+
* User is blocked
235
+
* Have administrator unblock the user in the Azure portal.
236
+
* SMS is not subscribed on the device
237
+
* Have the user change methods or activate SMS on the device.
238
+
* Faulty telecom providers (No phone input detected, missing DTMF tones issues, blocked caller ID on multiple devices, or blocked SMS across multiple devices)
239
+
* Microsoft uses multiple telecom providers to route phone calls and SMS messages for authentication. If you are seeing any of the above issues have a user attempt to use the method at least 5 times within 5 minutes and have that user's information available when contacting Microsoft support.
240
+
220
241
## App Passwords
221
242
222
243
Certain non-browser apps do not support multi-factor authentication, if a user has been enabled for multi-factor authentication and attempt to use non-browser apps, they are unable to authenticate. An app password allows users to continue to authenticate
0 commit comments