How to get Azure Multi-Factor Authentication
When it comes to protecting your accounts, two-step verification should be standard across your organization. This feature is especially important for administrative accounts that have privileged access to resources. For this reason, Microsoft offers basic two-step verification features to Office 365 and Azure administrators for no extra cost. If you want to upgrade the features for your admins or extend two-step verification to the rest of your users, you can purchase Azure Multi-Factor Authentication.
This article explains the difference between the versions offered to administrators and the full Azure MFA version. If you're ready to deploy the complete Azure MFA offering, the later section covers implementation options and how Microsoft calculates consumption.
This article is meant to be a guide to help you understand the different ways to buy Azure Multi-Factor Authentication. For specific details about pricing and billing, you should always refer to the Multi-Factor Authentication pricing page.
Available versions of Azure Multi-Factor Authentication
The following table describes the differences between three versions of multi-factor authentication:
|Multi-Factor Authentication for Office 365||This version works exclusively with Office 365 applications and is managed from the Office 365 portal. Administrators can secure Office 365 resources with two-step verification. This version is part of an Office 365 subscription.|
|Multi-Factor Authentication for Azure Administrators||Global administrators of Azure tenants can enable two-step verification for their global admin accounts at no additional cost.|
|Azure Multi-Factor Authentication||Often referred to as the "full" version, Azure Multi-Factor Authentication offers the richest set of capabilities. It provides additional configuration options via the Azure classic portal, advanced reporting, and support for a range of on-premises and cloud applications. Azure Multi-Factor Authentication is included in Azure Active Directory Premium plans and Enterprise Mobility + Security plans, and can be deployed either in the cloud or on-premises.|
Feature comparison of versions
The following table provides a list of the features that are available in the various versions of Azure Multi-Factor Authentication.
This comparison table discusses the features that are part of each version of Multi-Factor Authentication. If you have the full Azure Multi-Factor Authentication service, some features may not be available depending on whether you use MFA in the cloud or MFA on-premises.
|Feature||Multi-Factor Authentication for Office 365||Multi-Factor Authentication for Azure Administrators||Azure Multi-Factor Authentication|
|Protect admin accounts with MFA||●||● (Global Administrator accounts only)||●|
|Mobile app as a second factor||●||●||●|
|Phone call as a second factor||●||●||●|
|SMS as a second factor||●||●||●|
|App passwords for clients that don't support MFA||●||●||●|
|Admin control over verification methods||●||●||●|
|Custom greetings for phone calls||●|
|Custom caller ID for phone calls||●|
|Remember MFA for trusted devices||●||●||●|
|MFA SDK||● (Requires Multi-Factor Auth provider and full Azure subscription)|
|MFA for on-premises applications||●|
How to get Azure Multi-Factor Authentication
If you would like the full functionality offered by Azure Multi-Factor Authentication, there are several options:
Option 1 - MFA licenses
Purchase Azure Multi-Factor Authentication licenses and assign them to your users in Azure Active Directory.
If you use this option, only create an Azure Multi-Factor Authentication Provider if you need to provide two-step verification for some users that don't have licenses. Otherwise, you might be billed twice.
Option 2 - Bundled licenses that include MFA
Purchase licenses that include Azure Multi-Factor Authentication, like Azure Active Directory Premium or Enterprise Mobility + Security, and assign them to your users in Azure Active Directory.
If you use this option, you should create an Azure Multi-Factor Authentication Provider only if you also need to provide two-step verification for some users that don't have licenses. Otherwise, you might be billed twice.
Option 3 - MFA consumption-based model
Create an Azure Multi-Factor Authentication Provider within an Azure subscription. Azure MFA Providers are Azure resources that are billed against your Enterprise Agreement, Azure monetary commitment, or credit card like all other Azure resources. These providers can only be created in full Azure subscriptions, not limited Azure subscriptions that have a $0 spending limit. Limited subscriptions are created when you activate licenses, like in options 1 and 2.
When using an Azure Multi-Factor Authentication Provider, there are two usage models available that are billed through your Azure subscription:
Per User - For enterprises that want to enable two-step verification for a fixed number of employees who regularly need authentication. Per-user billing is based on the number of users enabled for MFA in your Azure AD tenant and your Azure MFA Server. If users are enabled for MFA in both Azure AD and Azure MFA Server, and domain sync (Azure AD Connect) is enabled, then we count the larger set of users. If domain sync isn't enabled, then we count the sum of all users enabled for MFA in Azure AD and Azure MFA Server. Billing is prorated and reported to the Commerce system daily.
Billing example 1: You have 5,000 users enabled for MFA today. The MFA system divides that number by 31, and reports 161.29 users for that day. Tomorrow you enable 15 more users, so the MFA system reports 161.77 users for that day. By the end of the billing cycle, the total number of users billed against your Azure subscription adds up to around 5,000.
Billing example 2: You have a mixture of users with licenses and users without, so you have a per-user Azure MFA Provider to make up the difference. There are 4,500 Enterprise Mobility + Security licenses on your tenant, but 5,000 users enabled for MFA. Your Azure subscription is billed for 500 users, prorated and reported daily as 16.13 users.
Per Authentication - For enterprises that want to enable two-step verification for a large group of users who infrequently need authentication. Billing is based on the number of two-step verification requests, regardless of whether those verifications succeed or are denied. This billing appears on your Azure usage statement in packs of 10 authentications, and is reported daily.
Billing example 3: Today, the Azure MFA service received 3,105 two-step verification requests. Your Azure subscription is billed for 310.5 authentication packs.
It's important to note that you can have Azure MFA licenses, but still get billed for consumption-based configuration. If you set up a per-authentication Azure MFA Provider, you are billed for every two-step verification request, even those done by users who have licenses. If you set up a per-user Azure MFA Provider on a domain that isn't linked to your Azure AD tenant, you are billed per enabled user even if your users have licenses on Azure AD.