Azure App Config - reserved keyword in key name allowed via portal but not via bicep/arm deployment

[TripleBrass]

Hey all,

I'm trying to utilize Azure App Config to centralize - well - all of my application configuration. There is something that bothers me, however. When you create a brand .NET 8 API in Visual Studio, one of the things it does is add a log level to the appsettings.json file like so:

{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.AspNetCore": "Warning"
    }
  },
  "AllowedHosts": "*"
}

I desire to have App Config manage these key values and I perform all deployments of key values with bicep. However, because "Microsoft" is a reserved keyword as per the documentation, trying to deploy a template with a reserved keyword fails. Here is an abbreviated example:

resource configStore 'Microsoft.AppConfiguration/configurationStores@2023-03-01' existing = {
  name: 'YOUR-APPCONFIG'
}

resource configStoreKeyValue 'Microsoft.AppConfiguration/configurationStores/keyValues@2023-03-01' = {
  parent: configStore
  name: 'Logging:LogLevel:Microsoft:AspNetCore'
  properties: {
    value: 'Warning'
  }
}

However, I can create this value with the azure portal manually and I can observe this HTTP request while doing so:

PUT

https://your-appconfig.azconfig.io/kv/Logging%3ALogLevel%3AMicrosoft%3AAspNetCore?label=%00

with a body of:

"{\"content_type\":\"\",\"value\":\"Warning\",\"tags\":{}}"

While I can work around this situation by transforming my configuration in code and not directly deploying a reserved keyword, I would like to better understand why I can create this entry in the portal but not via bicep/ARM. Any advice is appreciated.

[GABRIELNGBTUC]

You can ask the reason directly to the app configuration team here https://github.com/Azure/AppConfiguration/issues

[TripleBrass]

Got it! I wasn't sure if this would be classified as something more specific to bicep/ARM or the app config service itself. I'll head their way.

[joshdanko]

I am struggling with the same thing. Pretty sure it is in fact related to bicep/ARM and not App Configuration like you said. I can also set it fine in the portal or using az appconfig kv set. Did you ever find a solution? I couldn't find this same question in: https://github.com/Azure/AppConfiguration/issues

[jeskew]

@joshdanko The reserved word check is performed by ARM and unfortunately can't be bypassed when the request is being handled by ARM. The portal and CLI must be calling AppConfig APIs directly.