az afd endpoint purge does not show error message when invalid resource-group argument.

[okumura-pico]

Describe the bug

When --resource-group argument is not valid,
az afd endpoint purge
commend does not output any error message.

Related command

az afd endpoint purge --debug --resource-group not-exists-rg --profile-name my-afd  --endpoint-name my-ep --content-paths '/*' 

Errors

(No error message)

Issue script & Debug output

cli.azure.cli.core.sdk.policies: Request method: 'POST'
cli.azure.cli.core.sdk.policies: Request headers:
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json'
cli.azure.cli.core.sdk.policies:     'Content-Length': '24'
cli.azure.cli.core.sdk.policies:     'x-ms-client-request-id': '782f9992-1fe3-11f0-9ccb-8b06431baeaf'
cli.azure.cli.core.sdk.policies:     'CommandName': 'afd endpoint purge'
cli.azure.cli.core.sdk.policies:     'ParameterSetName': '--debug --resource-group --profile-name --endpoint-name --content-paths'
cli.azure.cli.core.sdk.policies:     'User-Agent': 'AZURECLI/2.71.0 (DEB) azsdk-python-core/1.31.0 Python/3.12.8 (Linux-6.8.0-47-generic-x86_64-with-glibc2.35)'
cli.azure.cli.core.sdk.policies:     'Authorization': '*****'
cli.azure.cli.core.sdk.policies: Request body:
cli.azure.cli.core.sdk.policies: {"contentPaths": ["/*"]}
urllib3.connectionpool: Starting new HTTPS connection (1): management.azure.com:443
urllib3.connectionpool: https://management.azure.com:443 "POST /subscriptions/00000000-0000-0000-0000-5c40393f3af4/resourceGroups/my-2025-rg/providers/Microsoft.Cdn/profiles/-----------afd/afdEn
dpoints/-----------pw-ep/purge?api-version=2024-09-01 HTTP/1.1" 404 107
cli.azure.cli.core.sdk.policies: Response status: 404
cli.azure.cli.core.sdk.policies: Response headers: 
cli.azure.cli.core.sdk.policies:     'Cache-Control': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Pragma': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Content-Length': '107'
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json; charset=utf-8'
cli.azure.cli.core.sdk.policies:     'Expires': '-1'
cli.azure.cli.core.sdk.policies:     'x-ms-failure-cause': 'gateway'
cli.azure.cli.core.sdk.policies:     'x-ms-request-id': '5cca1545-1112-4d98-8ea7-a71013d3d47b'
cli.azure.cli.core.sdk.policies:     'x-ms-correlation-request-id': '5cca1545-1112-4d98-8ea7-a71013d3d47b'
cli.azure.cli.core.sdk.policies:     'x-ms-routing-request-id': 'JAPANEAST:20250423T013710Z:5cca1545-1112-4d98-8ea7-a71013d3d47b'
cli.azure.cli.core.sdk.policies:     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.sdk.policies:     'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.sdk.policies:     'X-Cache': 'CONFIG_NOCACHE'
cli.azure.cli.core.sdk.policies:     'X-MSEdge-Ref': 'Ref A: 92C12108E04E4CEB9AF1E4201FA4D0B6 Ref B: OSA221030113023 Ref C: 2025-04-23T01:37:08Z'
cli.azure.cli.core.sdk.policies:     'Date': 'Wed, 23 Apr 2025 01:37:09 GMT'
cli.azure.cli.core.sdk.policies: Response content: 
cli.azure.cli.core.sdk.policies: {"error":{"code":"ResourceGroupNotFound","message":"Resource group 'my-2025-rg' could not be found."}}
cli.azure.cli.core.commands: Service returned 404 on the long-running delete or purge operation. CLI treats it as delete or purge successfully but service should fix this behavior.
cli.knack.cli: Event: CommandInvoker.OnTransformResult [<function _resource_group_transform at 0x7afeb22c44a0>, <function _x509_from_base64_to_hex_transform at 0x7afeb22c4540>]
cli.knack.cli: Event: CommandInvoker.OnFilterResult []
cli.knack.cli: Event: Cli.SuccessfulExecute []
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x7afeb226c4a0>]

Expected behavior

Show me some error message.
Just like a 'No such frontdoor exists.'

Environment Summary

azure-cli 2.71.0

core 2.71.0
telemetry 1.1.0

Extensions:
application-insights 1.2.1

Dependencies:
msal 1.31.2b1
azure-mgmt-resource 23.1.1

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• az afd endpoint purge silently ignores non-existent resource group #30621

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

I found what is wrong in my case. Do this: az resource list --resource-group NAME. If you see the ID of the ENDPOINT, it is generated in the wrong way. The PROFILE_NAME is set for both profiles and afdendpoints. So, you can do two things:

az afd endpoint purge --id IDVALUE --domains DOMAINVALUE --content-paths '/*'

or

az afd endpoint purge -g RESOURCEGROUP --profile-name PROFILE --endpoint-name PROFILE --domains www.contoso.com --content-paths '/*'

(Note that PROFILE value is twice)

Good Luck

Reference:

• az afd endpoint purge silently ignores non-existent resource group #30621 (comment)

Powered by issue-sentinel

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cdnfdsuppgithub, @t-bzhan, @gxue, @TracyYaoYao.

[okumura-pico]

Duplicate #30621

[okumura-pico]

Please consider not ignoring following Azure Management API response.

{"error":{"code":"ResourceGroupNotFound","message":"Resource group 'my-2025-rg' could not be found."}}

[Ptnan7]

Change the behavior of this logic of command is a little difficult for our service now, we suggest customers manually check the existence of your rg before you purge them, sorry for that.