Outlook is down, and so is Microsoft's status page

Re:Outlook is down, and so is Microsoft's status page by atraac on Friday November 13, 2026 @05:02AM (#50481035)

I read opinions like those but then I worked with Azure at previous jobs a lot and never had any really big issues. On the other side, I just tried using AWS for a small Saas of mine and after setting up SES, I got a shady email, from non-defult support amazon domain that I need to send them scans of my personal documents. Link in that email was blocked by uBlock Origin, domain was not the same as other emails, not a single notification in AWS Support Console anywhere so I ignored it as phishing. Got suspended two weeks later, not a single human in sight within 48 hours of me making a ticket, I just gave up and moved emails to Cloudflare. If I had actual real clients at that phase I'd be pretty pissed. I genuinely don't know how people blindly trust AWS with everything these days, it's 2026 and there's still not even a hard billing limit built into AWS.

[ Parent | on HN ]

Re:Outlook is down, and so is Microsoft's status page by gunsle on Friday November 13, 2026 @11:48AM (#50486150)

I will never understand people crying about MS and Azure when AWS and GCP support are 10x worse. At least Microsoft usually has decent docs and support.

[ Parent | on HN ]

Re:Outlook is down, and so is Microsoft's status page by llama052 on Friday November 13, 2026 @05:50PM (#50491248)

Hardly, Microsofts docs will actively lie to you on functionality and features. Even pointing claude at them will run opus around in circles realizing it's not concrete at all.

If the docs are correct I'm sure they'll depreciate the offering and rename it to something else and leave you on an island either way.

[ Parent | on HN ]

Re:Outlook is down, and so is Microsoft's status page by sov on Friday November 13, 2026 @12:33PM (#50486802)

> I worked with Azure at previous jobs a lot and never had any really big issues

to what extent, though? over the course of my working with azure, ive been disappointed constantly, by just about every service i've used. things that should work a particular way don't, and when you try to investigate you end up in a maze of out-of-date and/or totally wrong documentation. i've started a project before, followed their precise "quick start!" guide to the letter, and find it totally non-functional and wrong.

things that DO work end getting updated (often due to financial incentives) and break, or shuddered entirely. some values that you might want to change for certain services are hard-coded (which, to their credit, you can verify from their public github repos) for ostensibly no reason. a lot of their documentation is internal only, and the public facing stuff feels perennially out-of-season.

(opinion) i feel like fundamentally microsoft has embraced ai development so wholly because they've not been able to describe their services in documentation very well, and thus rely heavily on the ai's ability to digest what scraps of truth remain and the various source code to be effective at delivering output

[ Parent | on HN ]