Excellent deep dive on the real costs of Azure Front Door for static sites. The $35/month minimum for what amounts to a blog CDN is absurd, and the multi-day cache propagation delays you describe would drive anyone insane. Your point about zombie resources continuing to charge after deletion is particularly important,I've seen people get burned by orphaned managed identities and log analytics workspaces that Azure leaves behind. The forensics angle at the end about unexpected charges being potential incident indicators is spot on. Those lingering services that shouldnt exist make great canaries for detecting unauthorized activity.
And I just looked and its still revving up cost. I have to wait now till azure billing decide they want to answer their ticket. Using the graph query does not show any things lingering and so I can't even do anything about deleting or documenting any erroneous things I see
The CNAME flattening issue with Cloudflare is a real gotcha. I've seen that trip people up because the proxy layer sits between DNS resolution and Azure's validation check. The cache purge delays on AFD sound brutal too, especially when you're trying to iterate quickly. Static Web Apps having instant propagation is a game changer for dev workflow.
Yea it is I decided to move everything into one spot for easier management, originally I think the biggest issue was that for hour you could not tell what was going on. So your site could be working but you would not for hours. Additionally the amount of resources I had to manage was difficult because they sit at different levels and permission management becomes muddy to. I did not talk about having to create an enterprise app and give it permissions to handle the github deployments and the CDN
Excellent deep dive on the real costs of Azure Front Door for static sites. The $35/month minimum for what amounts to a blog CDN is absurd, and the multi-day cache propagation delays you describe would drive anyone insane. Your point about zombie resources continuing to charge after deletion is particularly important,I've seen people get burned by orphaned managed identities and log analytics workspaces that Azure leaves behind. The forensics angle at the end about unexpected charges being potential incident indicators is spot on. Those lingering services that shouldnt exist make great canaries for detecting unauthorized activity.
And I just looked and its still revving up cost. I have to wait now till azure billing decide they want to answer their ticket. Using the graph query does not show any things lingering and so I can't even do anything about deleting or documenting any erroneous things I see
The CNAME flattening issue with Cloudflare is a real gotcha. I've seen that trip people up because the proxy layer sits between DNS resolution and Azure's validation check. The cache purge delays on AFD sound brutal too, especially when you're trying to iterate quickly. Static Web Apps having instant propagation is a game changer for dev workflow.
Yea it is I decided to move everything into one spot for easier management, originally I think the biggest issue was that for hour you could not tell what was going on. So your site could be working but you would not for hours. Additionally the amount of resources I had to manage was difficult because they sit at different levels and permission management becomes muddy to. I did not talk about having to create an enterprise app and give it permissions to handle the github deployments and the CDN