Yeah, they fixed their truthfulness real fast. There is an earnings call today after all.
1 Like
This tells me they aren’t very confident in their fix.
Although we are seeing signs of recovery and have an estimated timeline, customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure. - Azure status
4 Likes
4 Likes
Might as well call it day at this point.
1 Like
What a day! I am thankful we only got hit by CBS outage - knock on wood.
One takeaway for us is that we will keep workaround versions of CBS menus handy with the base extensions ripped out so we can at least process transactions except for running the cards themselves (the outage completely prevented these screens from launching).
3 Likes
I’ll see your pitcher and raise you
2 Likes
Tom, can you break down CBS acronym?
It’s the company that makes ebizcharge About Us | EBizCharge
2 Likes
thanks.
Never cared to look but found it: Century Business Solutions we just call them “ebiz” here so 
1 Like
We’re able to open the client with out issues now. I hope I don’t jinx myself.
2 Likes
A customer caused the Azure outage yesterday.
2 Likes
That’s what I told @chaddb but he didn’t believe me. 
1 Like
I take it to mean the ‘tenant’ in question was Microsoft’s own tenant not a customer’s.
AI (sorry, not sorry):
The phrase “tenant configuration change within Azure Front Door” can sound confusing because it suggests something customer-specific, but in this incident, it referred to Microsoft’s internal tenant configuration, not a customer’s.
Here’s the distinction:
- Customer configuration change: A change made by you (or any Azure customer) to your own AFD profile—like adding a custom domain, updating routing rules, or modifying WAF policies. These changes only affect your subscription.
- Microsoft internal tenant configuration change: Microsoft operates its own Azure tenants for managing global services like AFD. The October 29 outage was caused by a change in Microsoft’s internal AFD tenant, which controls core infrastructure and DNS routing for the entire AFD platform. This change propagated globally and impacted all customers because it altered how AFD resolved and routed traffic at the platform level.
So, while the term “tenant configuration change” was accurate, the tenant in question was Microsoft’s, not yours. That’s why customers didn’t trigger the outage, but they were affected by it.
1 Like
So the “customer” was calling from inside the house…
5 Likes
I saw this yesterday as well.
Anyone in US Central seeing issues?
1 Like