"No one was ever fired for buying Microsoft" just ended.
"No one gets fired for renting Microsoft" ftfy
Microsoft 365 Outage
81–90 of 166 posts
Re: Microsoft 365 Outage
#82Re: Microsoft 365 Outage
#83Re: Microsoft 365 Outage
#84Earlier quoted context omitted.
That is awful and why I have always been very sceptical of software moving to the cloud. Just yesterday I had a similar issue with Resharper, where our local licence server was down for the day. Luckily I was able to enable a 30-day trial. (and I guess Resharper isn't that mandatory to get work done)
> 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?
Re: Microsoft 365 Outage
#85Earlier quoted context omitted.
> We're not observing an increase in successful connections after rolling back a recent change. We're working to evaluate additional mitigation solutions while we investigate the root cause. Oooh that's panic stations.
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.
Re: Microsoft 365 Outage
#86Earlier quoted context omitted.
That is awful and why I have always been very sceptical of software moving to the cloud. Just yesterday I had a similar issue with Resharper, where our local licence server was down for the day. Luckily I was able to enable a 30-day trial. (and I guess Resharper isn't that mandatory to get work done)
> 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?
Yes? I have never heard the concept of "bricking your IDE" before. How badly could you mess up and not be able to reset it? If your IDE can break dramatically without an obvious method to revert to a good state, consider a different IDE.
Re: Microsoft 365 Outage
#87I 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.
Their reliability only looks bad in comparison with other cloud providers.
Microsoft can still probably do a much better job compared to a small team.
Re: Microsoft 365 Outage
#88I 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.
"Nobody ever got fired for buying IBM" -> Microsoft
Re: Microsoft 365 Outage
#89My phone keeps asking me to retype in my Microsoft word password every 30 seconds. Agh!
Re: Microsoft 365 Outage
#90Earlier 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?
Welcome to Visual Studio, the home of updates that take hours to install and sometimes end up bricking your IDE.
To be fair, that hasn't happened in a pretty long time for me - but in the earlier days it was commonplace. It used to be bleeding edge features that would do it, other times it was just because they took so long, that interrupting the process of upgrading or installing caused a mess. Or installing the newest version alongside the older version, etc.
Visual Studio is a massive and complex creature (much like other "big IDEs", such as Eclipse) - although it has become much more streamlined in more recent releases - considering how complex it is.
EDIT: To be clear, problems often involved corruption of registry values, library/DLL hell, small database or configuration files and caches, etc. that happened with Visual Studio in the scenarios above.