Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Already exists
Created by Guest
Created on Apr 14, 2023

Hierarchical appsettings support for 'Manage app settings'

After trying out the new 'Manage app settings' feature in the DXP portal.

Not sure if hierarchical named app settings are supported. Due to the app setting name input field not allowing the separator '__' (double underscores). (See .NET 6 environment variables configuration).

Probably mainly because the validation matches with the key vault name restrictions. But it doesn't match with the App Service's app setting name restrictions.

Ideally, if possible, the app setting name validation in the DXP portal should follow the App Service's app setting name restrictions (as it is pushed there anyway) and perhaps transformed to the key vault secret name (double dashes) behind the scenes.

We use hierarchical app settings regularly. Consider the following app setting:


"SomeExternalApi": {

"ApiKey": "(secret)"



Other than that, great feature! If above can be supported, we would use this very often.

  • Guest
    Jun 28, 2023

    Yes, we really need this!

    Microsoft Keyvault doc:
    Azure Key Vault secret names are limited to alphanumeric characters and dashes. Hierarchical values (configuration sections) use -- (two dashes) as a delimiter, as colons aren't allowed in key vault secret names. Colons delimit a section from a subkey in ASP.NET Core configuration. The two-dash sequence is replaced with a colon when the secrets are loaded into the app's configuration.

    Optimizely appsettings UI:

    Please provide a valid secret name. The name must be between 1 and 127 characters long. Secret names can only contain alphanumeric characters.