Anyone else remember the bad Windows Defender virus signature they put out on Friday the 13th a couple weeks ago? Microsoft is not having a good start to their year.
Microsoft Azure Outage
191–200 of 247 posts
Re: Microsoft Azure Outage
#192Earlier quoted context omitted.
And the companies are forced to due to huge contracts with Microsoft
Nothing is forcing companies to sign an Azure contract with Microsoft, and go with AWS or GCP instead. Perhaps they are just doing something right. But I didn't use Azure myself. I'd be curious to know what's good or bad about it compared to GCP and AWS.
> I'd be curious to know what's good or bad about it compared to GCP and AWS.
Documentation lies, support lies, metrics lie, bugs everywhere, and when something breaks the status page is always all green and support tries to convince you it's your fault anyway. They're only here to prevent you from enforcing the SLA. The distrust is pervasive. I stopped suspecting my code, if something breaks outside of a planned maintenance it is _always_ Azure.
My latest support ticket: Azure App Service internal DNS server broke and there is no way to bypass it short of hardcoding IPs in /etc/hosts. Support told me that if I wanted App Service to work reliably I had to implement their DNS server myself. To rephrase, my PaaS provider told me to spend time and money to implement the very platform I was paying them for, and it just so happened to be absolutely impossible because of an unannounced BC break a few months prior (which is another lengthy and frustrating story).
This morning I had a VM cut out of the network and 10% of my App Service traffic just disappeared. No explanation, no incident report, nothing.
These days I'm working with AWS, and it just works. If something isn't working you know it's your fault and that the answer is in the documentation. I'm not spending days on workarounds, I'm actually implementing as planned. I have no words to describe the relief I'm feeling.
Re: Microsoft Azure Outage
#193Earlier quoted context omitted.
> it seems far worse to have status pages fail to reflect actual outages than to have them accidentally report an outage when there isn't one Thats not the goal. > It's hard to see how the goal here could be anything other than trying to add plausible deniability for what would otherwise be obvious deception Thats the goal. The "status page" is considered the source of truth for most of the big contracts. If status-p…
Utter rubbish. Major contracts have account managers and it all gets hashed out 1-1.
Don't know why this was downvoted. We've definitely been able to provide proof of an outage when the status page showed otherwise and get a refund in the form of server credits by contacting them directly. For all 3 big vendors, AWS, Azure, GCP
Re: Microsoft Azure Outage
#194Earlier quoted context omitted.
We're migrating on Teams because of that kind of reasoning. It's utter shit of a service. Even worse if you need to write integrations for it
What will you use instead? What don't you like about teams (or wiring integrations)
Our work switched from Slack to Teams after an acquisition, and I can confidently say that Teams is just complete garbage compared to Slack.
- The interface is laggy
- Scrolling back in long messages is buggy, it often skips around and loses its place
- No built in "whiteboarding" tools in screen sharing
- Teams will often keep ringing on my phone for up to a minute after I picked up a call on my laptop
- Sometimes I can't click reactions on messages. I click the emoji and nothing happens
Overall, it's just poorly made software. It feels like something that was made by a couple of interns in their spare time, not a keystone product from a multi-billion dollar company
Re: Microsoft Azure Outage
#195Earlier quoted context omitted.
Application insights is amazing - I didn't realise how amazing until I had to try and achieve the same thing in the JavaScript/Node ecosystem.
Yeah, I'm currently missing it very much running .NET on AWS. It's insane how much it gives you for "free". CloudWatch feels like weak tea in comparison.
We moved from AWS to Azure for other reasons, but in doing so we moved from X-Ray to AppInsights, and the difference was amazing. We're big App Insights fans.
Re: Microsoft Azure Outage
#196Azure is the most developer hostile cloud environment. I have zero sympathy for people being affected by this because if you voluntarily use Azure then this is what you deserve. Sorry for being so miserable, but Azure has given me soooo much grief over the last 10 years that I'm just completely done with this shitshow of a platform.
[deleted]
Re: Microsoft Azure Outage
#197Does this mean they need to rebrand, because it's not up 365 days of the year? Maybe rebrand it to Microsoft 364.5?
There’s 365.2425 days per year, so a six hour outage is just about 0.2425 hours, which suggests that they remain able to declare 365 when considering this specific outage only.
Re: Microsoft Azure Outage
#198Earlier quoted context omitted.
What will you use instead? What don't you like about teams (or wiring integrations)
Our work switched from Slack to Teams after an acquisition, and I can confidently say that Teams is just complete garbage compared to Slack. - The interface is laggy - Scrolling back in long messages is buggy, it often skips around and loses its place - No built in "whiteboarding" tools in screen sharing - Teams will often keep ringing on my phone for up to a minute after I picked up a call on my laptop - Sometimes I…
Also for several weeks recently my phone was getting messages several minutes before they showed up on my laptop, and 3 or 4 of my coworkers (all remote and in various parts of the US) confirmed they were having the same issue.
Re: Microsoft Azure Outage
#199It's good that Microsoft saved money via layoffs so that it balances out when customers leave Azure. Very forward thinking company.
[deleted]
Re: Microsoft Azure Outage
#200Hope the Leopard tanks aren’t running azure…