Cannot delete and purge an app configuration via CLI

Describe the bug

Command Name az appconfig delete az appconfig list-deleted az appconfig purge

Describe the bug I cannot delete and purge an app configuration instance

Errors:

az appconfig create -g MyResourceGroup -n MyAppConfiguration -l eastus --sku Standard
(NameUnavailable) The specified name is already in use.
Code: NameUnavailable
Message: The specified name is already in use.

az appconfig purge --name MyAppConfiguration
This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Failed to find the deleted App Configuration store 'MyAppConfiguration'. If you think that the store name is correct, please validate all your input parameters again.

To Reproduce:

1. az appconfig create -g MyResourceGroup -n MyAppConfiguration -l eastus --sku Standard (successfully completes)
2. az appconfig delete -g MyResourceGroup -n MyAppConfiguration (successfully completes)
3. az appconfig list-deleted (completes, but doesn’t return any deleted instances) This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus []
4. az appconfig create -g MyResourceGroup -n MyAppConfiguration -l eastus --sku Standard (errors) (NameUnavailable) The specified name is already in use. Code: NameUnavailable Message: The specified name is already in use.
5. az appconfig purge --name MyAppConfiguration This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus Failed to find the deleted App Configuration store ‘MyAppConfiguration’. If you think that the store name is correct, please validate all your input parameters again.

Expected Behavior

I expected the deleted app configuration to be shown by the list-deleted and to be able to purge that with the purge. If it was indeed already hard deleted, I expect to be able to create a new app configuration with the same name.

Environment Summary

Windows-10-10.0.19043-SP0
Python 3.10.4
Installer: MSI

azure-cli 2.37.0

Additional Context

output from az appconfig create
{
  "createMode": null,
  "creationDate": "2022-05-01T15:42:24+00:00",
  "disableLocalAuth": false,
  "enablePurgeProtection": false,
  "encryption": {
    "keyVaultProperties": null
  },
  "endpoint": "https://myappconfiguration.azconfig.io",
  "id": "<id to my app config in my subscription and resource group>",
  "identity": null,
  "location": "eastus",
  "name": "MyAppConfiguration",
  "privateEndpointConnections": null,
  "provisioningState": "Succeeded",
  "publicNetworkAccess": null,
  "resourceGroup": "MyResourceGroup",
  "sku": {
    "name": "standard"
  },
  "softDeleteRetentionInDays": 7,
  "systemData": {
    "createdAt": "2022-05-01T15:42:24+00:00",
    "createdBy": "<my email>",
    "createdByType": "User",
    "lastModifiedAt": "2022-05-01T15:42:24+00:00",
    "lastModifiedBy": "<my email>",
    "lastModifiedByType": "User"
  },
  "tags": {},
  "type": "Microsoft.AppConfiguration/configurationStores"
}

I experience similar behavior through the portal UI also.

[derekjoos]

@RakeshMohanMSFT That was the problem! I thought I was good because I was an owner on the resource group. I had missed these lines in the documentation: “Permissions for reading and purging deleted App Configuration stores must be assigned at the subscription level. This is because deleted configuration stores exist outside of individual resource groups.” https://docs.microsoft.com/en-us/azure/azure-app-configuration/concept-soft-delete

Is there anyway to provide an error message or warning that might point someone to permissions as the cause of the problem?

Thank you for your help!

[msftbot[bot]]

Hi, we’re sending this friendly reminder because we haven’t heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don’t hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!