What is Azure Active Directory B2C?
Azure Active Directory B2C provides business-to-customer identity as a service. Your customers use their preferred social, enterprise, or local account identities to get single sign-on access to your applications and APIs.
Azure AD B2C is a customer identity access management (CIAM) solution capable of supporting millions of users and billions of authentications per day. It takes care of the scaling and safety of the authentication platform, monitoring, and automatically handling threats like denial-of-service, password spray, or brute force attacks.
Azure AD B2C is a separate service from Azure Active Directory (Azure AD). It is built on the same technology as Azure AD but for a different purpose. It allows businesses to build customer facing application, and then allow anyone to sign up into those applications with no restrictions on user account.
Who uses Azure AD B2C?
Any business or individual who wishes to authenticate end users to their web/mobile applications using a white-label authentication solution. Apart from authentication, Azure AD B2C service is used for authorization such as access to API resources by authenticated users. Azure AD B2C is meant to be used by IT administrators and developers.
Custom-branded identity solution
Azure AD B2C is a white-label authentication solution. You can customize the entire user experience with your brand so that it blends seamlessly with your web and mobile applications.
Single sign-on access with a user-provided identity
Azure AD B2C uses standards-based authentication protocols including OpenID Connect, OAuth 2.0, and Security Assertion Markup Language (SAML). It integrates with most modern applications and commercial off-the-shelf software.
By serving as the central authentication authority for your web applications, mobile apps, and APIs, Azure AD B2C enables you to build a single sign-on (SSO) solution for them all. Centralize the collection of user profile and preference information, and capture detailed analytics about sign-in behavior and sign-up conversion.
Integrate with external user stores
Azure AD B2C provides a directory that can hold 100 custom attributes per user. However, you can also integrate with external systems. For example, use Azure AD B2C for authentication, but delegate to an external customer relationship management (CRM) or customer loyalty database as the source of truth for customer data.
Another external user store scenario is to have Azure AD B2C handle the authentication for your application, but integrate with an external system that stores user profile or personal data. For example, to satisfy data residency requirements like regional or on-premises data storage policies. However, Azure AD B2C service itself is worldwide via the Azure public cloud.
Azure AD B2C can facilitate collecting the information from the user during registration or profile editing, then hand that data off to the external system via API. Then, during future authentications, Azure AD B2C can retrieve the data from the external system and, if needed, include it as a part of the authentication token response it sends to your application.
Another user journey option includes progressive profiling. Progressive profiling allows your customers to quickly complete their first transaction by collecting a minimal amount of information. Then, gradually collect more profile data from the customer on future sign-ins.
Third-party identity verification and proofing
Use Azure AD B2C to facilitate identity verification and proofing by collecting user data, then passing it to a third-party system to perform validation, trust scoring, and approval for user account creation.
You have learned some of the things you can do with Azure AD B2C as your business-to-customer identity platform. The following sections of this overview walk you through a demo application that uses Azure AD B2C. You're also welcome to move on directly to a more in-depth technical overview of Azure AD B2C.
Example: WoodGrove Groceries
WoodGrove Groceries is a live web application created by Microsoft to demonstrate several Azure AD B2C features. The next few sections review some of the authentication options provided by Azure AD B2C to the WoodGrove website.
WoodGrove is an online grocery store that sells groceries to both individual consumers and business customers. Their business customers buy groceries on behalf of their company, or businesses that they manage.
WoodGrove Groceries offers several sign-in options based on the relationship their customers have with the store:
- Individual customers can sign up or sign in with individual accounts, such as with a social identity provider or an email address and password.
- Business customers can sign up or sign in with their enterprise credentials.
- Partners and suppliers are individuals who supply the grocery store with products to sell. Partner identity is provided by Azure Active Directory B2B.
Authenticate individual customers
When a customer selects Sign in with your personal account, they're redirected to a customized sign-in page hosted by Azure AD B2C. You can see in the following image that we've customized the user interface (UI) to look and feel just like the WoodGrove Groceries website. WoodGrove's customers should be unaware that the authentication experience is hosted and secured by Azure AD B2C.
WoodGrove allows their customers to sign up and sign in by using their Google, Facebook, or Microsoft accounts as their identity provider. Or, they can sign up by using their email address and a password to create what's called a local account.
When a customer selects Sign up with your personal account and then Sign up now, they're presented with a custom sign-up page.
After entering an email address and selecting Send verification code, Azure AD B2C sends them the code. Once they enter their code, select Verify code, and then enter the other information on the form, they must also agree to the terms of service.
Clicking the Create button causes Azure AD B2C to redirect the user back to the WoodGrove Groceries website. When it redirects, Azure AD B2C passes an OpenID Connect authentication token to the WoodGrove web application. The user is now signed-in and ready to go, their display name shown in the top-right corner to indicate they're signed in.
Authenticate business customers
When a customer selects one of the options under Business customers, the WoodGrove Groceries website invokes a different Azure AD B2C policy than it does for individual customers. You learn what a B2C policy is in technical overview of Azure AD B2C
This policy presents the user with an option to use their corporate credentials for sign-up and sign-in. In the WoodGrove example, users are prompted to sign in with any work or school account. This policy uses a multi-tenant Azure AD application and the Azure AD endpoint to federate Azure AD B2C with any Microsoft 365 customer in the world.
The Sign in with your supplier account link uses Azure Active Directory B2B's collaboration functionality. Azure AD B2B is a family of features in Azure Active Directory to manage partner identities. Those identities can be federated from Azure Active Directory for access into Azure AD B2C-protected applications.
Learn more about Azure AD B2B in What is guest user access in Azure Active Directory B2B?.
Now that you have an idea of what Azure AD B2C is and some of the scenarios it can help with, dig a little deeper into its features and technical aspects.
Monthly Active Users (MAU)
Azure Active Directory B2C is priced on a Monthly Active User (MAU) basis, helping customers to reduce costs and plan ahead with confidence. A MAU is counted when a unique user authenticates within a given calendar month.
Azure AD B2C is billed at the following standard tier rates.* Enterprise Agreement customers will be billed at a low, flat rate.
|MONTHLY ACTIVE USERS/MONTH||GENERAL AVAILABILITY PRICE||ENTERPRISE AGREEMENT PRICE|
|First 50,000||Free||Enterprise Agreement customers are eligible to switch to MAU-based billing which includes the Free tier of 50,000 MAUs. Subsequent Azure AD B2C usage will be billed at a low, flat rate per MAU. For more information, please contact your partner or Microsoft representative.|
|Greater than 10,000,000||¥0.0254|
|MFA and SMS/Phone-based Events||¥ 0.305 per SMS/Phone event|
We listened carefully to customers about their needs regarding predictable, intuitive, and cost-efficient billing for customer identity solutions. With MAU-based billing, customers benefit from:
- Expanded Free tier: The new Free tier stretches further by granting customers 50,000 MAUs per month-enabling more authentications per unique user than under the previous free allotment of 50,000 authentications. Most customers-with 50,000 or fewer MAUs per month-will be able to use Azure AD B2C for free.
- Predictable forecasting: Estimating monthly billing on a per MAU basis is simpler and more predictable than trying to forecast the number of monthly authentications.
- Usage-based billing: Pay only for your MAUs. Customers are not charged for a MAU`s subsequent authentications or for storing inactive users within that calendar month.
For example, if you have 100,000 monthly active users (MAUs) using standard features, your monthly bill would be ¥ 2,800 regardless of how many times each MAU authenticates:
(50,000 MAUs x ¥0(Free tier)) + (50,000 MAUs x ¥0.056) = ¥2800
A worldwide flat fee of ¥0.305 is billed for each MFA attempt or SMS/Phone event.
Support & SLA
If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.
The free version of Azure Active Directory doesn’t offer a service level agreement. If you want to learn more about the details of our server level agreement, please visit the Service Level Agreements page.
Technical and feature overview of Azure Active Directory B2C
A companion to About Azure Active Directory B2C, this article provides a more in-depth introduction to the service. Discussed here are the primary resources you work with in the service, its features. Learn how these features enable you to provide a fully custom identity experience for your customers in your applications.
Azure AD B2C tenant
In Azure Active Directory B2C (Azure AD B2C), a tenant represents your organization and is a directory of users. Each Azure AD B2C tenant is distinct and separate from other Azure AD B2C tenants. An Azure AD B2C tenant is different than an Azure Active Directory tenant, which you may already have.
The primary resources you work with in an Azure AD B2C tenant are:
- Directory - The directory is where Azure AD B2C stores your users' credentials, profile data, and your application registrations.
- Application registrations - Register your web, mobile, and native applications with Azure AD B2C to enable identity management. You can also register any APIs you want to protect with Azure AD B2C.
- User flows and custom policies - Create identity experiences for your applications with built-in user flows and fully configurable custom policies:
- User flows help you quickly enable common identity tasks like sign-up, sign-in, and profile editing.
- Custom policies let you build complex identity workflows unique to your organization, customers, employees, partners, and citizens.
- Sign-in options - Azure AD B2C offers various sign-up and sign-in options for users of your applications:
- Username, email, and phone sign-in - Configure your Azure AD B2C local accounts to allow sign-up and sign-in with a username, email address, phone number, or a combination of methods.
- Social identity providers - Federate with social providers like Facebook, LinkedIn, or Twitter.
- External identity providers - Federate with standard identity protocols like OAuth 2.0, OpenID Connect, and more.
- Keys - Add and manage encryption keys for signing and validating tokens, client secrets, certificates, and passwords.
An Azure AD B2C tenant is the first resource you need to create to get started with Azure AD B2C. Learn how to:
Accounts in Azure AD B2C
Azure AD B2C defines several types of user accounts. Azure Active Directory, Azure Active Directory B2B, and Azure Active Directory B2C share these account types.
- Work account - Users with work accounts can manage resources in a tenant, and with an administrator role, can also manage tenants. Users with work accounts can create new consumer accounts, reset passwords, block/unblock accounts, and set permissions or assign an account to a security group.
- Guest account - External users you invite to your tenant as guests. A typical scenario for inviting a guest user to your Azure AD B2C tenant is to share administration responsibilities.
- Consumer account - Accounts that are managed by Azure AD B2C user flows and custom policies.
Figure: User directory within an Azure AD B2C tenant in the Azure portal
With a consumer account, users can sign in to the applications that you've secured with Azure AD B2C. Users with consumer accounts can't, however, access Azure resources, for example the Azure portal.
A consumer account can be associated with these identity types:
- Local identity, with the username and password stored locally in the Azure AD B2C directory. We often refer to these identities as "local accounts."
- Social or enterprise identities, where the identity of the user is managed by a federated identity provider. For example, Facebook, Google, Microsoft, ADFS, or Salesforce.
A user with a consumer account can sign in with multiple identities. For example username, email, employee ID, government ID, and others. A single account can have multiple identities, both local and social.
Figure: A single consumer account with multiple identities in Azure AD B2C
For more information, see Overview of user accounts in Azure Active Directory B2C.
Local account sign-in options
Azure AD B2C provides various ways in which users can authenticate a user. Users can sign-in to a local account, by using username and password, phone verification (also known as password-less authentication). Email sign-up is enabled by default in your local account identity provider settings.
Learn more about sign-in options or how to set up the local account identity provider.
User profile attributes
Azure AD B2C lets you manage common attributes of consumer account profiles. For example display name, surname, given name, city, and others.
You can also extend the Azure AD schema to store additional information about your users. For example, their country/region of residency, preferred language, and preferences like whether they want to subscribe to a newsletter or enable multi-factor authentication. For more information, see:
Sign-in with external identity providers
You can configure Azure AD B2C to allow users to sign in to your application with credentials from social and enterprise identity providers. Azure AD B2C can federate with identity providers that support OAuth 1.0, OAuth 2.0, OpenID Connect, and SAML protocols. For example, Facebook, Microsoft account, Google, Twitter, and AD-FS.
With external identity provider federation, you can offer your consumers the ability to sign in with their existing social or enterprise accounts, without having to create a new account just for your application.
On the sign-up or sign-in page, Azure AD B2C presents a list of external identity providers the user can choose for sign-in. Once they select one of the external identity providers, they're taken (redirected) to the selected provider's website to complete the sign in process. After the user successfully signs in, they're returned to Azure AD B2C for authentication of the account in your application.
To see how to add identity providers in Azure AD B2C, see Add identity providers to your applications in Azure Active Directory B2C.
Identity experiences: user flows or custom policies
In Azure AD B2C, you can define the business logic that users follow to gain access to your application. For example, you can determine the sequence of steps users follow when they sign in, sign up, edit a profile, or reset a password. After completing the sequence, the user acquires a token and gains access to your application.
In Azure AD B2C, there are two ways to provide identity user experiences:
User flows are predefined, built-in, configurable policies that we provide so you can create sign-up, sign-in, and policy editing experiences in minutes.
Custom policies enable you to create your own user journeys for complex identity experience scenarios.
The following screenshot shows the user flow settings UI, versus custom policy configuration files.
Read the User flows and custom policies overview article. It gives an overview of user flows and custom policies, and helps you decide which method will work best for your business needs.
In Azure AD B2C, you can craft your users' identity experiences so that the pages are shown blend seamlessly with the look and feel of your brand. You get nearly full control of the HTML and CSS content presented to your users when they proceed through your application's identity journeys. With this flexibility, you can maintain brand and visual consistency between your application and Azure AD B2C.
For information on UI customization, see:
You can customize your Azure AD B2C domain in the redirect URLs for Azure AD B2C. Custom domain allows you to create a seamless experience so that the pages are shown blend seamlessly with the domain name of your application.
From the user's perspective, they remain in your domain during the sign-in process rather than redirecting to the Azure AD B2C default domain .b2clogin.com. For more information, see Enable custom domains.
Language customization in Azure AD B2C allows you to accommodate different languages to suit your customer needs. Microsoft provides the translations for 36 languages, but you can also provide your own translations for any language. Even if your experience is provided for only a single language, you can customize any text on the pages.
See how localization works in Language customization in Azure Active Directory B2C.
Azure AD B2C ensures valid email addresses by requiring customers to verify them during the sign-up, and password reset flows. It also prevents malicious actors from using automated processes to generate fraudulent accounts in your applications.
You can customize the email to users that sign up to use your applications. By using the third-party email provider, you can use your own email template and From: address and subject, as well as support localization and custom one-time password (OTP) settings. For more information, see:
Add your own business logic
If you choose to use custom policies, you can integrate with a RESTful API in a user journey to add your own business logic to the journey. For example, Azure AD B2C can exchange data with a RESTful service to:
- Display custom user-friendly error messages.
- Validate user input to prevent malformed data from persisting in your user directory. For example, you can modify the data entered by the user, such as capitalizing their first name if they entered it in all lowercase.
- Enrich user data by further integrating with your corporate line-of-business application.
- Using RESTful calls, you can send push notifications, update corporate databases, run a user migration process, manage permissions, audit databases, and more.
Loyalty programs are another scenario enabled by Azure AD B2C's support for calling REST APIs. For example, your RESTful service can receive a user's email address, query your customer database, then return the user's loyalty number to Azure AD B2C.
The return data can be stored in the user's directory account in Azure AD B2C. The data then can be further evaluated in subsequent steps in the policy, or be included in the access token.
You can add a REST API call at any step in the user journey defined by a custom policy. For example, you can call a REST API:
- During sign-in, just before Azure AD B2C validates the credentials
- Immediately after sign-in
- Before Azure AD B2C creates a new account in the directory
- After Azure AD B2C creates a new account in the directory
- Before Azure AD B2C issues an access token
To see how to use custom policies for RESTful API integration in Azure AD B2C, see Integrate REST API claims exchanges in your Azure AD B2C custom policy.
Protocols and tokens
For applications, Azure AD B2C supports the OAuth 2.0, OpenID Connect, and SAML protocols for user journeys. Your application starts the user journey by issuing authentication requests to Azure AD B2C. The result of a request to Azure AD B2C is a security token, such as an ID token, access token, or SAML token. This security token defines the user's identity within the application.
For external identities, Azure AD B2C supports federation with any OAuth 1.0, OAuth 2.0, OpenID Connect, and SAML identity providers.
The following diagram shows how Azure AD B2C can communicate using various protocols within the same authentication flow:
- The relying party application starts an authorization request to Azure AD B2C using OpenID Connect.
- When a user of the application chooses to sign in using an external identity provider that uses the SAML protocol, Azure AD B2C invokes the SAML protocol to communicate with that identity provider.
- After the user completes the sign-in operation with the external identity provider, Azure AD B2C then returns the token to the relying party application using OpenID Connect.
When a user wants to sign in to your application, the application initiates an authorization request to a user flow- or custom policy-provided endpoint. The user flow or custom policy defines and controls the user's experience. When they complete a user flow, for example the sign-up or sign-in flow, Azure AD B2C generates a token, then redirects the user back to your application.
Multiple applications can use the same user flow or custom policy. A single application can use multiple user flows or custom policies.
For example, to sign in to an application, the application uses the sign up or sign in user flow. After the user has signed in, they may want to edit their profile, so the application initiates another authorization request, this time using the profile edit user flow.
Multi-factor authentication (MFA)
Azure AD B2C multi-factor authentication (MFA) helps safeguard access to data and applications while maintaining simplicity for your users. It provides extra security by requiring a second form of authentication, and delivers strong authentication by offering a range of easy-to-use authentication methods.
Your users may or may not be challenged for MFA based on configuration decisions that you can make as an administrator.
See how to enable MFA in user flows in Enable multi-factor authentication in Azure Active Directory B2C.
Azure AD Identity Protection risk-detection features, including risky users and risky sign-ins, are automatically detected and displayed in your Azure AD B2C tenant. You can create Conditional Access policies that use these risk detections to determine remediation actions and enforce organizational policies.
Azure AD B2C evaluates each sign-in event and ensures that all policy requirements are met before granting the user access. Risky users or sign-ins may be blocked, or challenged with a specific remediation like multi-factor authentication (MFA). For more information, see Identity Protection and Conditional Access.
During sign up or password reset, your users must supply a password that meets complexity rules. By default, Azure AD B2C enforces a strong password policy. Azure AD B2C also provides configuration options for specifying the complexity requirements of the passwords your customers use.
For more information, see Configure complexity requirements for passwords in Azure AD B2C.
Force password reset
As an Azure AD B2C tenant administrator, you can reset a user's password if the user forgets their password. Or you would like to force them to reset the password periodically. For more information, see Set up a force password reset flow.
Smart account lockout
To prevent brute-force password guessing attempts, Azure AD B2C uses a sophisticated strategy to lock accounts based on the IP of the request, the passwords entered, and several other factors. The duration of the lockout is automatically increased based on risk and the number of attempts.
For more information about managing password protection settings, see Mitigate credential attacks in Azure AD B2C.
Protect resources and customer identities
Azure AD B2C complies with the security, privacy, and other commitments described in the Microsoft Azure Trust Center.
Sessions are modeled as encrypted data, with the decryption key known only to the Azure AD B2C Security Token Service. A strong encryption algorithm, AES-192, is used. All communication paths are protected with TLS for confidentiality and integrity. Our Security Token Service uses an Extended Validation (EV) certificate for TLS. In general, the Security Token Service mitigates cross-site scripting (XSS) attacks by not rendering untrusted input.
Access to user data
Azure AD B2C tenants share many characteristics with enterprise Azure Active Directory tenants used for employees and partners. Shared aspects include mechanisms for viewing administrative roles, assigning roles, and auditing activities.
You can assign roles to control who can perform certain administrative actions in Azure AD B2C, including:
- Create and manage all aspects of user flows
- Create and manage the attribute schema available to all user flows
- Configure identity providers for use in direct federation
- Create and manage trust framework policies in the Identity Experience Framework (custom policies)
- Manage secrets for federation and encryption in the Identity Experience Framework (custom policies)
For more information about Azure AD roles, including Azure AD B2C administration role support, see Administrator role permissions in Azure Active Directory.
Auditing and logs
Azure AD B2C emits audit logs containing activity information about its resources, issued tokens, and administrator access. You can use the audit logs to understand platform activity and diagnose issues. Audit log entries are available soon after the activity that generated the event occurs.
In an audit log, which is available for your Azure AD B2C tenant or for a particular user, you can find information including:
- Activities concerning the authorization of a user to access B2C resources (for example, an administrator accessing a list of B2C policies)
- Activities related to directory attributes retrieved when an administrator signs in using the Azure portal
- Create, read, update, and delete (CRUD) operations on B2C applications
- CRUD operations on keys stored in a B2C key container
- CRUD operations on B2C resources (for example, policies and identity providers)
- Validation of user credentials and token issuance
For more information on audit logs, see Accessing Azure AD B2C audit logs.
Azure AD B2C allows you to discover when people sign up or sign in to your app, where the users are located, and what browsers and operating systems they use.
By integrating Azure Application Insights into Azure AD B2C custom policies, you can gain insight into how people sign up, sign in, reset their password or edit their profile. With such knowledge, you can make data-driven decisions for your upcoming development cycles.
For more information, see Track user behavior in Azure Active Directory B2C using Application Insights.
Automation using Microsoft Graph API
Use MS graph API to manage your Azure AD B2C directory. You can also create the Azure AD B2C directory itself. You can manage users, identity providers, user flows, custom policies and many more.
Learn more about how to Manage Azure AD B2C with Microsoft Graph.
Azure AD B2C service limits and restrictions
Learn more about Azure AD B2C service limits and restrictions
Now that you have deeper view into the features and technical aspects of Azure Active Directory B2C:
Tutorial: Create an Azure Active Directory B2C tenant
Before your applications can interact with Azure Active Directory B2C (Azure AD B2C), they must be registered in a tenant that you manage.
You can create up to 20 tenants per subscription. This limit helps protect against threats to your resources, such as denial-of-service attacks, and is enforced in both the Azure portal and the underlying tenant creation API. If you need to create more than 20 tenants, please contact Microsoft Support.
If you want to reuse a tenant name that you previously tried to delete, but you see the error "Already in use by another directory" when you enter the domain name, you'll need to follow these steps to fully delete the tenant first. A role of at least Subscription Administrator is required. After deleting the tenant, you might also need to sign out and sign back in before you can reuse the domain name.
In this article, you learn how to:
- Create an Azure AD B2C tenant
- Link your tenant to your subscription
- Switch to the directory containing your Azure AD B2C tenant
- Add the Azure AD B2C resource as a Favorite in the Azure portal
You learn how to register an application in the next tutorial.
An Azure subscription. If you don't have one, create a free account before you begin.
An Azure Azure account that's been assigned at least the Contributor role within the subscription or a resource group within the subscription is required.
Create an Azure AD B2C tenant
Sign in to the Azure portal.
Select the directory that contains your subscription:
- In the Azure portal toolbar, select the Directories + subscriptions filter icon.
- Find the directory that contains your subscription and select the Switch button next to it. Switching a directory reloads the portal.
Add Microsoft.AzureActiveDirectory as a resource provider for the Azure subscription your're using (learn more):
- On the Azure portal menu or from the Home page, select Subscriptions.
- Select your subscription, and then in the left menu, select Resource providers .
- Make sure the Microsoft.AzureActiveDirectory row shows a status of Registered. If it doesn't, select the row, and then select Register.
On the Azure portal menu or from the Home page, select Create a resource.
Search for Azure Active Directory B2C, and then select Create.
Select Create a new Azure AD B2C Tenant.
On the Create a directory page, enter the following:
- Organization name - Enter a name for your Azure AD B2C tenant.
- Initial domain name - Enter a domain name for your Azure AD B2C tenant.
- Country or region - Select your country or region from the list. This selection can't be changed later.
- Subscription - Select your subscription from the list.
- Resource group - Select or search for the resource group that will contain the tenant.
Select Review + create.
Review your directory settings. Then select Create. Learn more about troubleshooting deployment errors.
You can link multiple Azure AD B2C tenants to a single Azure subscription for billing purposes. To link a tenant, you must be an admin in the Azure AD B2C tenant and be assigned at least a Contributor role within the Azure subscription. See Link an Azure AD B2C tenant to a subscription.
Select your B2C tenant directory
To start using your new Azure AD B2C tenant, you need to switch to the directory that contains the tenant:
- In the Azure portal toolbar, select the Directories + subscriptions filter icon.
- On the All Directories tab, find the directory that contains your Azure AD B2C tenant and then select the Switch button next to it.
If at first you don't see your new Azure B2C tenant in the list, refresh your browser window or sign out and sign back in. Then in the Azure portal toolbar, select the Directories + subscriptions filter again.
Add Azure AD B2C as a favorite (optional)
This optional step makes it easier to select your Azure AD B2C tenant in the following and all subsequent tutorials.
Instead of searching for Azure AD B2C in All services every time you want to work with your tenant, you can instead favorite the resource. Then, you can select it from the portal menu's Favorites section to quickly browse to your Azure AD B2C tenant.
You only need to perform this operation once. Before performing these steps, make sure you've switched to the directory containing your Azure AD B2C tenant as described in the previous section, Select your B2C tenant directory.
Sign in to the Azure portal.
In the Azure portal menu, select All services.
In the All services search box, search for Azure AD B2C, hover over the search result, and then select the star icon in the tooltip. Azure AD B2C now appears in the Azure portal under Favorites.
If you want to change the position of your new favorite, go to the Azure portal menu, select Azure AD B2C, and then drag it up or down to the desired position.
In this article, you learned how to:
- Create an Azure AD B2C tenant
- Link your tenant to your subscription
- Switch to the directory containing your Azure AD B2C tenant
- Add the Azure AD B2C resource as a Favorite in the Azure portal
Next, learn how to register a web application in your new tenant.
Ad b2c azure
From his face, ice appeared in his eyes: No one asks you - and left, tightly locking the door. At first, his last words angered me, but then an electric discharge seemed to run down my spine - the imperiousness of his voice, his strong strong hands excited me utterly in a couple of moments. I could not restrain myself, lay on my back and began to rub my clitoris, thrusting my fingers into my current.
Pussy and dreaming about Andrei. Orgasm in a bright flash pierced me in a minute.Azure AD B2C Webinar Series: Custom Policies Part 1
Can I ask you something. whispered Tanya, interrupted by her own moans. Do you want to fuck you like that every day. Almost.
You will also like:
- Top warframes 2020
- Evil money tattoo
- Dachshund puppies nj
- Gravity falls games
- Group by splunk
- College station dodge
When I arrived, he was waiting for me at the checkpoint, our first meeting was unforgettable, as soon as I saw him I wanted to touch him, feel his kisses, his warmth. I approached him, gently hugged him, without saying a word, and began to kiss him. He was not taken aback and immediately began to respond to my kisses.
It was magical, his warm wet tongue penetrated my mouth and instantly turned me on. The kiss made me dizzy and I was ready to surrender to him.