PageRenderTime 89ms CodeModel.GetById 20ms RepoModel.GetById 0ms app.codeStats 0ms

Markdown | 195 lines | 104 code | 91 blank | 0 comment | 0 complexity | 34439beae42115e267c35bdee6569f32 MD5 | raw file
  1. <properties
  2. pageTitle="Azure Multi-Factor Authentication FAQ"
  3. description="Provides a list of frequently asked questions and answers related to Azure Multi-factor authentication (MFA). MFA is a method of verifying who you are that requires the use of more than just a username and password. It provides an additional layer of security to user sign-ins and transactions."
  4. services="multi-factor-authentication"
  5. documentationCenter=""
  6. authors="billmath"
  7. manager="stevenpo"
  8. editor="curtand"/>
  9. <tags
  10. ms.service="multi-factor-authentication"
  11. ms.workload="identity"
  12. ms.tgt_pltfrm="na"
  13. ms.devlang="na"
  14. ms.topic="article"
  17. # Azure Multi-Factor Authentication FAQ
  18. This FAQ answers questions about Azure Multi-Factor Authentication. This FAQ covers questions about using the service, including the billing model and usability.
  19. ## General
  20. **Q: How can I get help with Azure Multi-Factor Authentication?**
  21. [Search the Microsoft Knowledge Base (KB)](
  22. - Search the Microsoft Knowledge Base (KB) for technical solutions to common break-fix issues about Support for Microsoft Azure Multi-Factor Authentication Server (PhoneFactor).
  23. [Microsoft Azure Active Directory Forums](
  24. - You can search and browse for technical questions and answers from the community or ask your own question by clicking [here](
  25. [Password reset](
  26. - Legacy PhoneFactor customers who have any queries around resetting your password or for help to get your password reset, please use the link below to open a support case.
  27. [Microsoft Azure Multi-Factor Authentication Server (PhoneFactor) customer support](
  28. - Use this link to contact a Microsoft support professional. Well ask you a few questions to help us determine what your support options are. The support options may include email, on-line submission or phone support.
  29. **Q: How does the Azure Multi-Factor Authentication Server handle user data?**
  30. When you use the Multi-Factor Authentication (MFA) Server on-premises, a users data is stored in the on-premises servers. No persistent user data is stored in the cloud. When the user performs a two-factor authentication, the MFA Server sends data to the Azure MFA cloud service to perform the authentication. When these authentication requests are sent to the cloud service, the following fields are sent in the request and logs so that they are available in the customer's authentication/usage reports. Some of the fields are optional so they can be enabled or disabled within the Multi-Factor Authentication Server. The communication from the MFA Server to the MFA cloud service uses SSL/TLS over port 443 outbound. These fields are:
  31. - Unique ID - either username or internal MFA server ID
  32. - First and Last Name - optional
  33. - Email Address - optional
  34. - Phone Number - when doing a voice call or SMS authentication
  35. - Device token - when doing mobile app authentication
  36. - Authentication Mode
  37. - Authentication Result
  38. - MFA Server Name
  39. - MFA Server IP
  40. - Client IP if available
  41. In addition to the fields above, the authentication result (success/denial) and reason for any denials is also stored with the authentication data and available through the authentication/usage reports.
  42. ## Billing
  43. **Q: Will my organization be charged for phone calls or text messages used to authenticate my users?**
  44. All costs are rolled into the per-user or per-authentication cost of the service. Organizations are not charged for individual phone calls placed or text messages sent to your end users when using Azure Multi-Factor Authentication. Phone owners may incur roaming-related or other costs from their telephone carriers to receive the phone calls or text messages.
  45. **Q: How is the organization billed for Azure Multi-Factor Authentication?**
  46. Azure Multi-Factor Authentication is available as a stand-alone service with per-user and per-authentication billing options, or bundled with Azure Active Directory Premium, Enterprise Mobility Suite end Enterprise Cloud Suite. The stand-alone service is available on a consumption basis that is billed monthly against Azure monetary commitment, or as a per-user annual license available through a Microsoft Enterprise Agreement, the Open Volume License Program, the Cloud Solution Providers program and Direct.
  48. >The Australia Regions are available to customers with a business presence in Australia or New Zealand.
  49. Billing Model | Price
  50. ------------- | ------------- |
  51. Per-user consumption (Azure monetary commitment)| $1.40 per month (unlimited authentications)
  52. Per-authentication consumption (Azure monetary commitment)|$1.40 per 10 authentications
  53. Per-user annual license (Direct)|$1.40 per month (unlimited authentications)
  54. Per-user annual license (Volume Licensing)|Contact your [Enterprise Agreement representative.](
  55. **Q: Does the per user billing model charge based on the number of users enabled for Multi-Factor Authentication or the number of users who perform the verifications?**
  56. Billing is based on the number of users enabled for Multi-Factor Authentication.
  57. **Q:How does Multi-Factor Authentication billing work?**
  58. When using the per-user or per-authentication consumption billing/usage model, administrators choose the type of usage when creating a Multi-Factor Auth Provider in the Microsoft Azure classic portal. It is a resource that is billed against the organizations Azure subscription, just like virtual machines, websites, etc. When using the license model, Azure Multi-Factor Authentication licenses are purchased and then assigned to users, just like Office 365 and other subscription products.
  59. **Q:Is there a free version of Azure Multi-Factor Authentication for administrators?**
  60. A subset of Azure Multi-Factor Authentication capabilities known as MFA for Azure Admins is offered at no cost to Azure Global Administrators when a consumption-based Azure Multi-Factor Auth Provider has not been linked to the corresponding Azure Active Directory. Using the Multi-Factor Auth Provider upgrades all admins and users in the directory that are enabled for MFA to the full version of Azure Multi-Factor Authentication.
  61. **Q:Is there a free version of Azure Multi-Factor Authentication for Office 365 users?**
  62. A subset of Azure Multi-Factor Authentication capabilities known as MFA for Office 365 is offered at no cost to users that have an O365 license assigned when a consumption-based Azure Multi-Factor Auth Provider has not been linked to the corresponding Azure Active Directory. Using the Multi-Factor Auth Provider upgrades all admins and users in the directory that are enabled for MFA to the full version of Azure Multi-Factor Authentication.
  63. **Q:Can I switch between per-user and per-authentication consumption billing models at any time?**
  64. The billing model is selected during resource creation and cannot be changed once the resource is provisioned. It is possible, however, to create a new Multi-Factor Authentication resource to replace the original. Please note that user settings and configuration options cannot be transferred to the new resource.
  65. **Q:Can I switch between the consumption billing and license models at any time?**
  66. You can purchase Azure Multi-Factor Authentication, Azure Active Directory Premium, Enterprise Mobility Suite and Enterprise Cloud Suite licenses at any time. When licenses are added to a directory that already has a per-user Azure Multi-Factor Auth Provider, the consumption-based billing is decremented by the number of licenses owned. If all users enabled for MFA have licenses assigned, the administrator can delete the Azure Multi-Factor Auth Provider. Organizations cannot mix per-authentication consumption billing with the license model. When a per-authentication Multi-Factor Auth Provider is linked to a directory, the organization is billed for all MFA verification requests, regardless of any licenses owned.
  67. **Q:Does my organization have to use and synchronize identities to use Azure Multi-Factor Authentication?**
  68. When using the consumption-based billing models, Azure Active Directory is not required. Linking a Multi-Factor Authentication provider to a directory is optional. When not linked to a directory, organizations can use the Azure Multi-Factor Authentication Server or SDK on-premises. When using the license model, Azure Active Directory is required since licenses are added to the directory when purchased and assigned to users in the directory.
  69. ## Usability
  70. **Q: What do I do if I dont receive a response on my phone or if I forgot my phone?**
  71. If you previously configured a backup phone, try again by selecting that phone when prompted from the sign in page. If you dont have another method configured, contact your admin and ask them to update the number assigned to your primary phone mobile or office.
  72. **Q: What do I do if a user contacts me, the administrator, with an account that has been locked out?**
  73. You can reset the user by forcing them to go through the registration process again. To do this see [Managing user and device settings with Azure Multi-Factor Authentication in the cloud](
  74. **Q: What do I do if a user has lost or had a device stolen that is using app passwords?**
  75. You can delete all of the users app passwords to prevent any unauthorized access. Once you have a replacement device, the user can recreate them. To do this see [Managing user and device settings with Azure Multi-Factor Authentication in the cloud](
  76. **Q: What if the user is not able to sign into non-browser apps?**
  77. - Users enabled for multi-factor authentication will require app password to sign into some non-browser apps.
  78. - Users will need to clear the sign-in info (delete sign-in info), restart the application and sign-in with the their username and app password.
  79. For information on creating app passwords see [Help with app passwords](
  80. >[AZURE.NOTE] Modern Authentication for the Office 2013 Clients
  81. >
  82. > Office 2013 clients (including Outlook) now support new Authentication Protocols and can be enabled to support Multi-Factor Authentication. This means that once enabled, app passwords are not required for use with Office 2013 clients. For more information see [Office 2013 modern authentication public preview announced](
  83. **Q: What do I do if I do not receive a text message, or I reply to a two-way text message but the verification times out?**
  84. The Azure Multi-Factor Authentication service sends text messages through SMS aggregators. Many factors may impact the reliability of text message delivery and receipt including the aggregator used, destination country, mobile phone carrier and signal strength. Therefore, delivery of text messages and receipt of SMS replies when performing two-way SMS is not guaranteed. Using one-way SMS is recommended over two-way SMS when possible because it is more reliable and prevents users from incurring global SMS charges caused by replying to a text message that was sent from another country.
  85. Text message verifications are also more reliable in some countries such as the United States and Canada. Users that experience difficulty receiving text messages reliably when using Azure Multi-Factor Authentication are encouraged to select the mobile app or phone call methods instead. The mobile app is great because mobile app notifications can be received over both cellular and Wi-Fi connections, and the mobile app passcode is displayed even when the device has no signal at all. The Azure Authenticator app is available for [Windows Phone](, [Android](, and [IOS](
  86. **Q: Can I use hardware tokens with the Azure MFA server?**
  87. If you are using the Azure MFA Server, third-party OATH TOTP tokens can be imported and used for MFA. We currently support the import of third-party OATH TOTP tokens in an older PSKC format that Gemalto can produce for their tokens and support importing tokens in CSV format. When importing tokens in CSV format, the CSV file must contain a serial number, secret key in Base32 format and a time interval (generally 30 seconds).
  88. So, if the ActiveIdentity tokens are OATH TOTP tokens and you can get the secret key file into a CSV file that can be imported into the Azure MFA Server, then you will be able to use them. OATH tokens can be used with AD FS, with RADIUS when the client system can process Access Challenge responses and with IIS Forms-based authentication.
  89. **Q: Can I use the Azure MFA Server to secure Terminal Services?**
  90. Yes, but if you are using Windows Server 2012 R2 or later than this can only be done using a RD Gateway.
  91. The way that the Azure MFA Server hooked into the LSA security package on Windows Server 2012 and earlier versions no longer works on Windows Server 2012 R2 due to some security changes. So for versions of Terminal Services on Windows 2012 or earlier, you can simply follow [To secure an application with Windows Authentication](
  92. However, if you are using Windows Server 2012 R2, then you will need an RD Gateway.
  93. **Q: Why am I receiving an MFA call from an anonymous caller after setting up caller ID?**
  94. Sometimes, when MFA calls are placed through the public telephone network, they are routed through a carrier that doesn't support caller ID. Therefore, caller ID is not guaranteed even though the MFA system always sends it.
  95. ## Errors
  96. **Q: What do I do when I see an Authentication request is not for an activated account error when I authenticate by using mobile application notifications?**
  97. - Go to []( and sign in with your organizational account.
  98. - If needed, click Other verification options and select a different option for completing the account verification.
  99. - Click Additional Security Verification.
  100. - Remove the existing account from your mobile application.
  101. - Click Configure and follow the instructions to re-configure the mobile application.
  102. **Q: What do I do when I see a 0x800434D4L error while attempting to sign-in using a non-browser application?**
  103. Currently, additional security verification can only be used with applications/services that you can access through your browser. Non-browser applications (also referred to as rich client applications) which are installed on your local computer such as Windows Powershell will not work with accounts that are required for additional security verification. In this case, you may see the application generate error 0x800434D4L.
  104. A workaround for this is to have a separate user account for admin-related operations vs. non-admin operations. You can later link mailboxes between your admin account and non-admin account so you can sign-in to outlook using your non-admin account. For more details about this, see [Give an Administrator the Ability to Open and View the Contents of a User's Mailbox](