Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft 365 Outage

status.office365.com

Post reply on HN
Print view View original

111–120 of 166 posts

Re: Microsoft 365 Outage

#111

Post by OkGoDoIt »

taf2 wrote: post #94
OkGoDoIt wrote: post #23

I'm assuming this is related: I can't do any development using Visual Studio 2019 at the moment because it calls home to verify the license and it is currently unable to log me in to to verify my license. So VS is basically bricked for me until this gets fixed :-( Screenshot: https://rog.gy/ss/3b14f7a2ac.png

Question does the compiler at the cli also phone home or is it just the IDE?

The compiler and the .net platform in general are all accessible without a paid license or internet connection, and actually there’s a free edition of visual studio you can use without a paid license as well. But downloading and installing a fresh copy of Visual Studio Community Edition would take a while and I don’t feel like dealing with that hassle right now. I assume this will be fixed by tomorrow.

Re: Microsoft 365 Outage

#113

Post by dragonwriter »

koyote wrote: post #84
neolog wrote: post #80

Earlier quoted context omitted.

> That is awful and why I have always been very sceptical of software moving to the cloud. Because you're less likely to brick your IDE than Microsoft is?

I don't think I've ever 'bricked' my IDE. How does one go about bricking an IDE?

> I don't think I've ever 'bricked' my IDE. How does one go about bricking an IDE?

Visual Studio major version updates (uninstall old plus install new) used to be a good way to do that and often wreak havoc on the overall stability of your system as well. At least, on a system where you didn't want to strip it to fresh OS install as an intermediate step.

Re: Microsoft 365 Outage

#114

Post by dismalpedigree »

Nextgrid wrote: post #78

Azure DevOps' Git is also down (a git pull hangs forever) which is a bit surprising. I wouldn't have expected SSH key authentication to depend on Azure Active Directory. Microsoft Teams also appears to be down so it's not just authentication that's affected as I was already logged in and it still doesn't work, just hangs trying to load forever. Edit: appears to be resolved at 1:07 am London time.

Difficult to tell if this is desired functionality for teams or a bug. It’s inline with its normal performance level.

Re: Microsoft 365 Outage

#115

Post by sixdimensional »

acwan93 wrote: post #64

I just finished convincing old-school management to move to Office365/Azure/Teams after we've been doing everything on-premise, saying we can reduce our maintenance and increase in reliability since we're a small operation. Needless to say this isn't a good look for me.

If it makes you feel any better, I've been that guy on both sides of the coin - both on the cloud and on-prem. Things go down.. even the cloud.

I worked for a company, where I really did have nearly 100% uptime at my local data center in our office. I wasn't a luddite, and the cloud wasn't something I was afraid of or didn't understand. I just, at the time, had an infrastructure in place before the cloud existed, and it worked well enough at a great price point. We were on the same electrical grid as a hospital, our infrastructure handled our scale, and just really didn't have problems for a long span of time.

Still, someone came in and said.. what, you are still doing stuff on-prem and not the cloud!? How legacy! How dated! And so the push to the cloud came next.

We migrated to the cloud (and some colo facilities for some equipment we chose to keep), and on the 3rd day of being freshly migrated, the cloud provider had a major outage and went down for longer than we'd ever had on prem. The next month, the colo went down and their diesel generators failed, and it was down for an entire afternoon.

Oh sure, there was some SLA money returned in that event from the colo...

I'm just saying, I've been on both sides. Tell them the truth - even the cloud has outages, but it is certainly more "convenient" to have hundreds of engineers work on fixing an outage at global scale, and all you have to do is wait for it to start working again - then it is to have to fix it all yourself.

Re: Microsoft 365 Outage

#116

Post by smcleod »

O365 (aka Microsoft 365 now) has easily been the most unreliable SaaS product I've been forced to use over the past 8 1/2 years, it's been a real disaster story for several of the clients I used to have and for several of them has resulted in loss of profits and general distrust in Cloud/SaaS software.

A few times during outages I managed to get hold of someone that worked at Microsoft who stated something along the lines that they only state that a service is degraded or has an outage if enough customers complain - or if the websites they have to sell / demonstrate products to potential customers are unavailable.

Re: Microsoft 365 Outage

#117

Post by spondyl »

Ahh, this explains why I was unable to log into my personal email account on my work laptop.

I thought it was just the network here being overly keen to block requests since I'm relatively new and am still finding out all the quirks

This also explains why clicking "Sign in" would randomly download an HTML page (ie logout.html) instead of redirecting to the proper auth endpoint!

Re: Microsoft 365 Outage

#118

Post by danbmil99 »

thanatos519 wrote: post #4

Is this /really/ the status page? It looks like it was pasted straight out of an email to Jason Zander from whoever is trying to fix the problem. https://status.office365.com/ Title: Can't access Microsoft 365 services User Impact: Users may be unable to access multiple Microsoft 365 services. More info: Any Microsoft 365 service that leverages Azure Active Directory (AAD) authentication may be impacted by this issue…

It looks like an actual status page written by a developer, instead of some Market speak gobbledygook attempt to not say anything for fear of liability or whatever

Re: Microsoft 365 Outage

#119

Post by tyingq »

tyingq wrote: post #85
tyingq wrote: post #62

Earlier quoted context omitted.

Yep, I can imagine the feeling of doom when the rollback didn't work. Push back from the desk, head droops down, hand on forehead. Then I whisper, "Fuck".

We’re rerouting traffic to alternate infrastructure to improve the user experience while we continue to investigate the issue. Imagine there's some foxhole prayers happening.

We’re seeing improvement for multiple services after applying mitigation steps and we’ll continue monitoring the services to ensure full recovery.

Big exhale.

Post reply on HN