Azure Active Directory B2C pricing

Read our documentation on how to set up your tenant for billing.

Only External Users, as defined by the Commercial Licensing Terms, are eligible for Active Directory B2C pricing. Internal employee users are not eligible and must have an Azure AD license.

If you choose to provide higher levels of assurance using Multi-Factor Authentication (MFA) for Voice and SMS, you will continue to be charged a worldwide flat fee of $- for each MFA attempt that month, whether the log in is successful or unsuccessful. The worldwide flat rate provides greater predictability, by removing the price variations for SMS messages that are dependent on the telecom carrier or destination phone number. For example, if you have 100 monthly active users (MAUs) who make two MFA attempts that month, you would be billed $-, in addition to your usage: 100 MAUs x 2 MFA attempts/each = 200 MFA attempts x $-/attempt = $-

All MAUs will be billed at the selected tier’s pricing. To learn about which features are suitable for your needs, please contact your partner or Microsoft representative.

No, you are not required to purchase Premium P2 licenses for employees in order to provide Active Directory B2C at Premium P2 to external users. You may need to purchase at least one Azure AD Premium P2 license for your admin to enable and manage Premium P2 features.

We worked closely with our customers to develop flexible, predictable, and cost-efficient billing that reflects the usage and features you need, rather than the licenses you have.

With 50,000 free MAU at every tier, the vast majority of customers are able to use Azure AD B2C for free. Incremental pricing for our Premium P1 and Premium P2 features enables organizations the flexibility to offer world-class security to any user, without needing to purchase more Azure AD licenses. All customers benefit from more accurate forecasting, with predictable month-to-month charges.

A monthly active user (MAU) is a unique user that performs an authentication within a given month. For example, a user that authenticates multiple times within a given month is counted as one MAU. Customers are not charged for a MAU’s subsequent authentications during the month, nor for inactive users.

Authentications may include:

• Active, interactive login by the user;
• Passive, non-interactive login (such as single sign-on, sign-up, sign-in, token refresh, and password change)

Additional operations that are counted as an authentication include: login to a portal; redeeming an invitation; authenticating to perform an admin action; and when an application exchanges a refresh token for a new identity token or access token for that user.

Enterprise Agreement customers are eligible to switch to MAU-based billing, with 50,000 free MAU at any tier and a low, flat rate for incremental MAU. For more information, please contact your partner or Microsoft representative.