App configuration applies reserved word rule incorrectly

[TobiasBunyan-TPR]

Problem

Trying to add an app configuration ending in the word "login" causes the "reserved word" error.

The reserved word documentation states that "login" can be used as long as it is not at the start of the resource name:
https://docs.azure.cn/en-us/azure-resource-manager/troubleshooting/error-reserved-resource-name

We already have other resources (resource group, web app) ending in "login" which deployed without error.

This issue occurs both when using terraform azurerm provider (400 bad request) AND using the azure UI.

Issue

This is blocking us from keeping a consistent name for a platform across the azure namespace.

[jimmyca15]

Looking into it, thanks for reporting!

[austintolani]

Hi @TobiasBunyan-TPR, there is indeed a discrepancy between the Azure Resource Manager reserved word documentation and the validation performed on configuration store name by the Azure App Configuration service. This will be fixed in an upcoming service release. Following this release, "login" will be allowed in configuration store names as long as it is not at the start of the resource name.

I will follow up here once the service release has completed.