Multi Instance ASP.NET Core 2.2 Data Protection Using Redis and an Azure Key Vault Certificate

Written by Ken Dale

We’re in the process of upgrading our infrastructure to run our Azure Web Apps in multiple datacenter locations behind Azure Traffic Manager instances to achieve high availability. Running multiple instances without using the scale up slider means you’re responsible for any server side state that needs to be shared between instances (or, ensure that traffic always returns to the same instance repeatedly, but we don’t want to do that…).

With ASP.NET Core projects we need to share the data protection keys between our web application instances. That way, items that are encrypted by any instance can be decrypted by any other instance.

For this, we’ve decided to use Redis for storing the key ring, while protecting the keys using a certificate retrived from Azure Key Vault. Here’s how to do it using ASP.NET Core 2.2:

Install packages

You’ll need to install the following packages to support the code below. Try installing the latest versions of all the packages, but if you run into issues working versions here are posted for reference:

Microsoft.AspNetCore.DataProtection.StackExchangeRedis # Version="2.2.0"
Microsoft.Azure.KeyVault                               # Version="3.0.3"
Microsoft.Azure.Services.AppAuthentication             # Version="1.0.3"
StackExchange.Redis                                    # Version="2.0.571"


Now, wiring it all up in Startup.cs:

using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.DataProtection;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Azure.KeyVault;
using Microsoft.Azure.Services.AppAuthentication;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Options;
using StackExchange.Redis;
using System;
using System.Security.Cryptography.X509Certificates;

namespace MyApplication
    public class Startup
        public Startup(IConfiguration configuration, IHostingEnvironment environment)
            Configuration = configuration;
            Environment = environment;

        public IConfiguration Configuration { get; }

        public IHostingEnvironment Environment { get; }

        public void ConfigureServices(IServiceCollection services)

            if (Environment.IsProduction())


        private void ConfigureRedisDataProtection(IServiceCollection services)
            var serviceProvider = services.BuildServiceProvider();
            var dataProtectionConfiguration = serviceProvider

            var azureServiceTokenProvider = new AzureServiceTokenProvider();
            var keyVaultClient = new KeyVaultClient(
                new KeyVaultClient.AuthenticationCallback(

            // GetSecretAsync rather than GetCertificationAsync
            // See:
            var dataProtectionSecretBundle = keyVaultClient

            var dataProtectionCertificate = new X509Certificate2(

            var redis = ConnectionMultiplexer.Connect(

                .PersistKeysToStackExchangeRedis(redis, dataProtectionConfiguration.RedisKey)

        public void Configure(IApplicationBuilder app, IHostingEnvironment env)
            if (env.IsDevelopment())



Some configuration is needed. Here’s a class to represent the required configuration:

namespace MyApplication
    public class DataProtectionConfiguration
        public string ApplicationName { get; set; }

        public string KeyVaultBaseUrl { get; set; }

        public string KeyVaultCertificateName { get; set; }

        public string RedisConnectionStringName { get; set; }

        public string RedisKey { get; set; }

The configuration then looks like this in JSON as appsettings.Production.json or similar (update these as needed):

  "dataProtection": {
    "applicationName": "my-application",
    "keyVaultBaseUrl": "",
    "keyVaultCertificateName": "DataProtection",
    "redisConnectionStringName": "Redis",
    "redisKey": "DataProtection-Keys-my-application"

Key Vault Permissions

Since the Azure Web App is authenticating as itself you’ll need to set each web app to use a managed identity (a system-assigned identity). See for more details.

After the web apps are set with managed identities, you’ll need to give each web application instance access to GET secrets from the key vault.

Required Azure Web Apps Configuration

You’ll also need to set a special app setting on each of the Azure Web App instances to make this work. See


Test it out

Start the app and make sure it starts up correctly. If you want to test roundtripping the encryption and decryption you can do something like this and call it:

using System.Text;
using Microsoft.AspNetCore.DataProtection;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Configuration;

namespace MyApplication
    public class TestController : ControllerBase
        private readonly IDataProtector dataProtector;

        public TestController(IDataProtectionProvider dataProtectorProvider)
            this.dataProtectorProvider = dataProtectorProvider.CreateProtector("Test");

        public ActionResult<string> DataProtection()
            var protectedBytes = DataProtector.Protect(Encoding.UTF8.GetBytes("test"));

            var unprotectedBytes = DataProtector.Unprotect(protectedBytes);
            var unprotectedString = Encoding.UTF8.GetString(unprotectedBytes);

            return unprotectedString;

I hope this helps on the road to high availability!

Published April 01, 2019 by

undefined avatar
Ken Dale Github Senior Application Developer (Former)

Suggested Reading