What is the proper way to use DownstreamApi when client secret is stored in an environment variable?

[sbloomfieldtea]

I discovered recently that when using the AZURE_CLIENT_SECRET environment variable, EnableTokenAcquisitionToCallDownstreamApi isn't picking up AZURE_CLIENT_ID or any of the other variables. As a workaround I did this, but was wondering if there was a better way:

services.AddMicrosoftIdentityWebApiAuthentication(configuration)
            .EnableTokenAcquisitionToCallDownstreamApi((options) =>
            {
                options.Instance = configuration.GetValue<string>("AzureAd:Instance");
                options.ClientId = configuration.GetValue<string>("AzureAd:ClientId") ??
                    Environment.GetEnvironmentVariable("AZURE_CLIENT_ID");
                options.ClientSecret = configuration.GetValue<string>("AzureAd:ClientSecret") ??
                    Environment.GetEnvironmentVariable("AZURE_CLIENT_SECRET");
                options.TenantId = configuration.GetValue<string>("AzureAd:TenantId") ??
                    Environment.GetEnvironmentVariable("AZURE_TENANT_ID");
            })
            .AddInMemoryTokenCaches();

[jmprieur]

IT would be AZUREAD__CLIENTSECRET (with 2 __), it should be picked automatically

[sbloomfieldtea]

Oooh ok. I didn't know about the naming convention that maps env vars to appsettings. So AZUREAD__CLIENTSECRET maps to "AzureAd:ClientSecret" in appsettings. Jeez now I'm wondering how my other stuff was working :-P