Skip to main content

A Demo On Azure AD B2C Authentication In MVC Application[.NET 6]

In this article, we are going to do a demo on Azure AD B2C authentication in the MVC application[.NET 6].

Azure AD B2C Configuration Steps:

Login into Azure Portal(

Chose the directory that has the subscription(eg: free, student, pay-as-you-go, etc).

(1) Select the 'Directories + Subscriptions' on the azure portal menu.
(2) Left side menu select 'Directories + Subscriptions'. Bottom select 'All Directories' tab where we can select all directories we have the option to 'switch'.
Here I have only one directory that has my subscription. So if we have multiple directories then we can see a 'switch' option.
Step 3:
The 'Microsoft.AzureActiveDirectory' resource provider needs to register with our 'subscription'.

(1) On the Azure portal home page select 'Subscriptions'.

(2) Now select your appropriate subscription.
(3) Search 'Resource Provider' and then 'Microsoft.AzureActiveDirectory' should be registered.
Step 4:
Create Azure AD B2C tenant.

(1)Click on 'Create a resource' on the azure home page.
(2)Search and select 'Azure Active Directory B2C'.

(3) Click on the 'Create' button.

(4) Chose any one option from 'Create New Azure Active Directory B2C' or 'Link an existing  Azure Active Directory B2C into your subscription'.
(5)Create a tenant.
  • Organization Name - Enter the name of your organization.
  • Initial Domain Name - By default, the basic domain name at '' is included with your directory. Later, you can add a domain name that your organization.
  • Country/Region -  Select the nearest server location to you.
  • Subscription - select your subscription.
  • Resource Group - Create a new group if you don't have any existing Resource Group.
  • Resource Grop Location.
Step 5:
So click on the 'Directories + Subscriptions' menu and then 'switch' to our newly-created directory.
Step 6:
After switching to the directory, on the azure landing portal, search and select 'Azure AD B2C'.
Step 7:
Register a web application.

(1) Left menu under 'Manage' select the 'App Registrations' and then click on 'New Registration'.

(2)Fill up the App registration form
  • Name - A display name for the application.
  • Support account types - use the default selection(last radio button option).
  • In the 'Redirect URL' section, select the dropdown value as 'Web', and in the text box enter our MVC(or any web application) URL.(Local development we can register 'localhost' so this URL can be updated any time later also)
  • Check the 'Permission' check box.
(3) After successful Application registration we can observe a generated 'Application Id' which we have to use in our MVC application in later steps.
Step 8:
Create a Client Secret.

(1) Left side menu under 'Manage' select 'Certificates & Secrets'. Next click on 'New Client Secret'. Next on popover enter the description for the secret and click on 'Create'.
(2) On successful creation secrets can be viewed like below.
Step 9:
Enable Tokens

(1) Under 'Manage', select 'Authentication' tab, then enable the 'Access Token' & 'ID Token'.
Step 10:
Create User flow for Sign-in &Sign-up.

(1) In 'Azure AD B2C', under the 'Policies' select 'User Flows'. Next click on the 'New User Flow'.

(2) Now let's create a user profile for Sign-in&Sing-up.
(3) Complete the user flow form.
  • Name - Register a name for our flow
  • Identity Providers - Select 'Email Signup' means option for email & password login.
  • Multifactor authentication & Conditional Access options can be left default.
  • User attributes are values collected on sign-up. Claims are values about the user returned to the application in the token. You can create custom attributes as well.

Create A .NET6 MVC App With Azure AD B2C Authentication:

Let's create a .Net6 MVC sample application with individual Azure AD B2C authentication to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor.
CLI command
dotnet new mvc -o Your_Project_Name -au IndividualB2C

Configure Azure AD B2C Settings In appSettings.json:

let's configure the Azure AD B2C Settings in appSettings.json.
"AzureAdB2C": {
    "Instance": "",
    "ClientId": "",
    "Domain": "",
    "SignedOutCallbackPath": "",
    "SignUpSignInPolicyId": "",
    "ResetPasswordPolicyId": "",
    "EditProfilePolicyId": "",
    "CallbackPath": ""
In 'Azure AD B2C', select 'App registration' next select 'Endpoints'. Copy the domain name from the urls on the popover.
eg: Instance: ""

Registered Application Id
In 'Azure AD B2C', Domain name value.
The 'SignedOutCallbackPath' value must be '/signout/{your_signout_flow_name}'. Here in the path 'signout' keyword is fixed string.
eg: SignedOutCallbackPath: "/signout/B2C_1_Sign_SignUp_1"

So in 'Azure AD B2C' under 'Policies' select 'Users Flows' and copy the name of the signout flow.
Directly assign the name of 'SignIn&SingOut' policy.
eg: SignUpSignInPolicyId : "B2C_1_Sign_Signup_1"

ResetPasswordPolicyId & EditProfilePolicyId:
Similarly like 'SignIn&SingOut' policy we can create for 'ResetPasswor' and 'EditProfile' then asing those policy names

A fixed string that is '/signin-oidc'. This path should be in redirect URLs registered in the 'App Registration' of the 'Azure AD B2C'

Test Authentication Flow:

(1) Run the application and click on 'Login'

(2) Now it redirects us to our Azure AD B2C authentication domain that loads the login page.
and then click on 'Sign-Up'
(3) Register our user into the 'Azure AD B2C'.
(4) Now after registration we successfully logged into the application.

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information on Azure Active Directory B2C Authentication in .NET6 MVC application. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:


Popular posts from this blog

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

.Net5 Web API Managing Files Using Azure Blob Storage

In this article, we are going to understand the different file operations like uploading, reading, downloading, and deleting in .Net5 Web API application using Azure Blob Storage. Azure Blob Storage: Azure blob storage is Microsoft cloud storage. Blob storage can store a massive amount of file data as unstructured data. The unstructured data means not belong to any specific type, which means text or binary data. So something like images or pdf or videos to store in the cloud, then the most recommended is to use the blob store. The key component to creating azure blob storage resource: Storage Account:- A Storage account gives a unique namespace in Azure for all the data we will save. Every object that we store in Azure Storage has an address. The address is nothing but the unique name of our Storage Account name. The combination of the account name and the Azure Storage blob endpoint forms the base address for each object in our Storage account. For example, if our Storage Account is n

.Net5 Web API Redis Cache Using StackExchange.Redis.Extensions.AspNetCore Library

In this article, we are going to explore the integration of Redis cache in .Net5 Web API application using the 'StackExchange.Redis.Exntensions' library. Note:- Microsoft has introduced an 'IDistributedCache' interface in dotnet core which supports different cache stores like In-Memory, Redis, NCache, etc. It is simple and easy to work with  'IDistributedCache', for the Redis store with limited features but if we want more features of the Redis store we can choose to use 'StackExchange.Redis.Extensions'.  Click here for Redis Cache Integration Using IDistributedCache Interface . Overview On StackExchange.Redis.Extnesions Library: The 'StackExchange.Redis.Extension' library extended from the main library 'StackExchange.Redis'. Some of the key features of this library like: Default serialization and deserialization. Easy to save and fetch complex objects. Search key. Multiple Database Access Setup Redis Docker Instance: For this sampl

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library  jQuery Validate . In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples. Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio. Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as bel

NestJS File Upload

In this article, we are going to understand the steps to create a file uploading endpoint in the NestJS application. Key Features In NestJS File Upload: Let us know some key features of NestJS file upload before implementing a sample application. FileInterceptor: The 'FileInterceptor' will be decorated on top of the file upload endpoint. This interceptor will read single file data from the form posted to the endpoint. export declare function FilesInterceptor(fieldName: string, localOptions?: MulterOptions): Type<NestInterceptor>; Here we can observe the 'fieldName' first input parameter this value should be a match with our 'name' attribute value on the form file input field. So our interceptor read our files that are attached to the file input field. Another input parameter of 'MulterOptions' that provides configuration like file destination path, customizing file name, etc. FilesInterceptor: The 'FilesInterceptor' will be decorated on t

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items. The main building block of ion-picker as follows: PickerController PickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker. Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger&quo

.Net Core HttpClient JSON Extension Methods Using System.Net.Http.Json Package

.Net Core 3.0 onwards Microsoft brought up a new package called System.Net.Http.Json. This new package provides JSON extension methods for HttpClient. These JSON extension methods will have a prebuild mechanism for serializing or deserializing response data or payload of HttpClient call. System.Net.Http.Json extension methods that are provided to HttpClient, few of them are mentioned below. GetFromJsonAsync PostAsJsonAsync PutAsJsonAsync ReadFromJsonAsync In this article, we understand System.Net.Http.Json package by implementing the HttpClient samples by with and without JSON extension methods and compare them. Create A .Net Core Web API Sample Application: Let's create a .Net Core sample Web API application, from this application we will consume another Web API by implementing HttpClient calls. We can create a Web API sample application using IDE like Visual Studio 2019(Supports .Net Core 3.0 plus) or  Visual Studio Code . Create A Typed Client: In .Net Core using the Http