Unable to Delete Failed Purchase of Domain Name

Question

Unable to Delete Failed Purchase of Domain Name

GLV 0

I tried to purchase a Custom Domain - It Failed and had the email to say it had failed.

Still shows in resources and cant delete it

Tried all the ways online - Seems its stuck in a billing / deployment loop-

isSoftDeleted": false,

"nameServers": [],

"privacy": false,

"provisioningState": "InProgress",

"readyForDnsRecordManagement": false,

"registrationStatus": 0,

"subStatus": "FAILED_SETUP"

I have since purchased it elsewhere and cant use it as Azure is still showing it

Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-06-29T16:44:29.0466667+00:00
Hello @GLV ,

It sounds like you attempted to purchase an Azure App Service domain (custom domain). The purchase failed, but the domain resource is still showing in Azure with provisioningState: "InProgress" and subStatus: "FAILED_SETUP", so you can’t delete it and it’s blocking you from using the domain elsewhere.

There are few Azure “can’t delete domain” scenarios and cleanup steps to consider:

1) If the domain purchase created a delete lock, remove it

For Azure App Service domains, Azure may create a lock that prevents deletion.

Steps:

In the Azure portal, go to App Service Domains

Select the domain you’re trying to remove

Open Locks

If a delete lock exists, remove it:

Select Delete on the lock

Then go back to the domain’s Overview and use Delete (or cancel the purchase if you’re still within the cancellation window)

2) If deletion fails due to dependencies, remove dependent resources first

A “failed setup / stuck provisioning” domain can also be blocked by dependencies. Microsoft guidance for domain deletion indicates you should ensure you’ve removed all users, groups, and applications dependent on the custom domain name—because deletion won’t succeed while dependencies exist.

3) Make sure you’re using the correct admin context (Global Admin nuance)

If this is a Microsoft Entra / tenant domain delete scenario (rather than just an App Service domain), deletion may fail if the signed-in admin account has dependencies on the domain being deleted.

Guidance says to:

Sign in with a Global Admin account that doesn’t have a dependency on the domain you’re deleting

Often the safest approach is using the initial default domain account context (example given in the doc: ******@...onmicrosoft.com) or another Global Admin with a different verified domain

4) If validation/authoritative DNS isn’t aligned, Azure domain state can stay stuck

In some domain-customization workflows, domain ownership validation can remain stuck if the required TXT validation record isn’t created in the authoritative DNS zone Azure is querying.

So, if your domain is stuck in a “validating / processing” style state, ensure the TXT record is added where Azure expects it.

Can you please update us if the action plan provided was helpful?

Should there be any follow-up questions or concerns, please let us know and we shall try to address them.

If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-07-01T18:00:53.3833333+00:00

Hello @GLV , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-07-03T17:19:40.3833333+00:00

Hello @GLV , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-07-22T17:46:48.7966667+00:00

Hello @GLV , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.

1 answer

Your answer

Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-07-01T18:00:53.3833333+00:00

Hello @GLV , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-07-03T17:19:40.3833333+00:00

Hello @GLV , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-07-22T17:46:48.7966667+00:00

Hello @GLV , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.

Answer 1

The object you are seeing is a failed App Service Domain resource under Microsoft.Web/domains. It is not the registrar ownership of the domain, so deleting it will not affect the copy you purchased elsewhere or its external DNS.

First open the failed App Service Domain resource, check Locks, and remove any Delete lock. Then use Cancel purchase or Delete from Overview.

If deletion still fails while provisioningState remains InProgress and subStatus is FAILED_SETUP, try deleting the exact resource ID from Azure CLI:

az resource delete --ids <full-resource-id>

If that returns Conflict, OperationInProgress, or the resource immediately reappears, stop retrying. The Microsoft.Web resource provider has a stuck purchase/provisioning record that only Azure support can clear. Open a subscription-management or App Service support request and include the full resource ID, failed deployment name, operation/correlation ID, UTC timestamp, and the JSON state you posted. Ask specifically for backend cleanup of the failed Microsoft.Web/domains resource and confirmation that no charge completed.

You do not need to remove Entra users, applications, or DNS records; those steps apply to a different type of custom domain. You can use the externally registered domain by configuring its DNS and adding it as a custom hostname to your App Service.