This morning, I tried to make some updates to our non-production Azure Front Door configuration, but I ran into a frustrating error message: "BadRequest: All Changes to Azure Frontdoor Configuration are blocked currently." It seems like this is a result of the incident from last week, but it's been three days now since that issue. Can anyone explain why the changes are still blocked and when we might expect this to be resolved?
2 Answers
I'm feeling your pain. The communication from Microsoft on this has been pretty terrible. Honestly, I'm thinking about jumping ship to Cloudflare as soon as I can! Not trying to sell you on it, just my plan.
But hey, Cloudflare isn't perfect either—there was an outage for them in March due to a key rotation issue, so keep that in mind.
While I totally get your frustration, it’s possible Microsoft knows the issue and is just being cautious. They might be blocking changes until they can roll out a fix to prevent any further problems. If they extend this lockout, then I’d be more worried.
Looks like we're in a lockout period that should last for another couple of days. According to the info I've seen, the restrictions should be lifted by the 5th. It's definitely a big mess, though!
True, Cloudflare isn't immune to outages. I've had some decent experiences with cloudflared in my homelab, though. Just got it running on several Kubernetes clusters, and it’s been a lot of fun.