HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Integrate Entra ID using OpenID Connect

Describes how to use OpenID Connect to integrate with Entra ID (formerly Azure AD). It also describes how an Optimizely application can use the OpenID Connect to sign in users from a single/multi-tenant environment, using the ASP.NET OpenID Connect middleware.



If you have EPiServer.CMS.UI.AspNetIdentity installed, make sure you are not calling services.AddCmsAspNetIdentity() in startup.cs. Otherwise, the user interface may not look for synchronized users when setting access rights.

About Entra ID and OpenID

Entra ID (formerly Azure AD) is Microsoft's multi-tenant cloud-based directory and identity management service. Entra ID provides single sign-on (SSO) access to many cloud-based SaaS applications and includes a full suite of identity management capabilities.

OAuth is an open standard for authorization also used by Entra ID. OpenID Connect is built on top of OAuth and extends this so you can use it as an authentication protocol rather than just an authorization protocol.

For information about how the protocols work, see Authentication Scenarios for Entra ID and Secure your application by using OpenID Connect and Entra ID


You can replace virtual roles with roles defined in the manifest to delegate this control from the application to Azure. See Adding application roles in Entra ID.

Install NuGet packages

Open Package Manager in Visual Studio and install the following package:

Install-Package Microsoft.AspNetCore.Authentication.OpenIdConnect

Configure OpenID Connect

To configure the OpenID Connect, add the following code in the startup class. The OnSignedIn event is used to sync the user and group membership to Optimizely. You can also use this event for custom logic (for example, adding custom data to the user profile).

public void ConfigureServices(IServiceCollection services) {
  .AddAuthentication(options => {
    options.DefaultAuthenticateScheme = "azure-cookie";
    options.DefaultChallengeScheme = "azure";
  .AddCookie("azure-cookie", options => {
    options.Events.OnSignedIn = async ctx => {
      if (ctx.Principal?.Identity is ClaimsIdentity claimsIdentity) {
        // Syncs user and roles so they are available to the CMS
        var synchronizingUserService = ctx
          .GetRequiredService < ISynchronizingUserService > ();

        await synchronizingUserService.SynchronizeAsync(claimsIdentity);
  .AddOpenIdConnect("azure", options => {
    options.SignInScheme = "azure-cookie";
    options.SignOutScheme = "azure-cookie";
    options.ResponseType = OpenIdConnectResponseType.Code;
    options.CallbackPath = "/signin-oidc";
    options.ClientSecret = "YOUR CLIENT SECRET";
    options.UsePkce = true;

    // If Entra ID is register for multi-tenant
    //options.Authority = "https://login.microsoftonline.com/" + "common" + "/v2.0";
    options.Authority = "https://login.microsoftonline.com/" + "tenant id" + "/v2.0";
    options.ClientId = "client id";

    options.MapInboundClaims = false;

    options.TokenValidationParameters = new TokenValidationParameters {
      RoleClaimType = "roles",
        NameClaimType = "preferred_username",
        ValidateIssuer = false

    options.Events.OnRedirectToIdentityProvider = ctx => {
      // Prevent redirects from being cached.
			ctx.Response.Headers.CacheControl = "no-cache,no-store";

      // Prevent redirect loop
      if (ctx.Response.StatusCode == 401) {

      return Task.CompletedTask;

    options.Events.OnAuthenticationFailed = context => {
      return Task.CompletedTask;

Add application roles in Entra ID

You must declare application roles in the active directory application, such as WebEditors and WebAdmins. The application owner (developer of the app) or the global administrator of the developer's directory can declare roles for an application.

  1. Go to the Active Directory node and the Applications tab in the Azure Management Portal.
  2. Click to open the application for which you want to declare application roles.
  3. Click App roles.
  4. Create WebAdmins, WebEditors, and Administrators app roles: This is an example of app roles that declare WebAdmins and WebEditors. You can modify it according to your application roles.

Assign users and groups to application roles

When a global administrator of the customer's organization has installed your application, they (or a user accounts administrator) can assign users and groups to your application:

  1. Go to the Users tab under the application you want to assign users and groups.
  2. Select a user and click Assign on the bottom bar to assign the desired role to the user.

Address CDN caching issues

Implement OnRedirectToIdentityProvider to address CDN caching issues. Setting the Cache-Control and CDN-Cache-Control headers to "no-store, no-transform, no-cache" is a good practice for security and data freshness, especially in authentication-related scenarios like redirecting to an identity provider. Also, consider the performance implications because avoiding caching might increase the load on your servers.

options.Events.OnRedirectToIdentityProvider = e => {
  e.Response.Headers["Cache-Control"] = "no-store, no-transform, no-cache";
  e.Response.Headers["CDN-Cache-Control"] = "no-store, no-transform, no-cache";

  var uri = e.ProtocolMessage.RedirectUri ?? "/";

  if (Uri.TryCreate(uri, UriKind.Relative, out Uri _)) {
    var uriBuilder = new UriBuilder(e.Request.Scheme, e.Request.Host.Host, e.Request.Host.Port ?? (-1), uri);
    e.ProtocolMessage.RedirectUri = uriBuilder.ToString();