title: How to delete a Front Door resource locked by a domain I don't own
body: <p>Azure Front Door does not allow frontend endpoint deletion if the endpoint's domain still points to the Front Door using a CNAME record. The same holds even when there is just the verification domain (afdverify).</p>
  <blockquote>
  <p>409 Conflict<br>
  Cannot delete frontend endpoint &quot;www.example.com&quot; because it is still directly or indirectly (using &quot;afdverify&quot; prefix) CNAMEd to front door &quot;example.azurefd.net&quot;. Please remove the DNS CNAME records and try again.</p>
  </blockquote>
  <p>While I hate that there is no way to delete such a frontend, there is a way to deal with that even if the DNS zone cannot be changed by the Front Door owner -- just don't assign the frontend endpoint to any routing rule and don't mind it; it consumes just a bit of developer's attention, which makes it somewhat bearable.</p>
  <p>The problem comes with the fact that such a frontend prevents even the deletion of the whole Front Door, which in turn prevents deletion of the whole resource group.</p>
  <p>Why is that a problem? Consider that a single subscription is shared by the whole dev team and someone creates a Front Door instance for experiments, uses his own domain and later leaves the team. Now the resource consumes money as there has to be at least one routing rule for the default frontend endpoint and routing rules are paid per time unit, and there is no obvious way to get rid of it.</p>
  <p>Is there a way to delete such a Front Door instance besides contacting Microsoft support or asking the owner of the domain to pretty please delete the records pointing to the Front Door?</p>