Microsoft Teams communication platform suffered a temporary outage due to an expired SSL...

Polycount

Posts: 3,017   +590
Staff
Oops! Microsoft's enterprise-oriented Teams communication software has gotten better and better as of late. A couple of months ago, the software even made the jump to Linux, opening up its feature set to an entirely new userbase. However, as great as Teams is, it was inaccessible to many users for several hours this morning for reasons unknown (until later).

The service went down without warning, and many users were forced to find alternative ways to communicate with their peers. The timing was especially unfortunate as for most workers this morning marked the start of a new work week, when there are important meetings to hold and files to share.

Eventually we learned thanks to an announcement from Microsoft on Twitter why Teams went down: the company forgot to renew the service's SSL certificate.

That's a pretty low-tech problem for such a high-tech company to miss, but it's certainly not unprecedented. A few years back, Instagram made a similar mistake, as did Apple the year before.

Of course, simple mistake or not, the internet is certainly having a good laugh about the situation at Microsoft's expense.

"Hey Cortana, set a reminder for a year from now: "Renew the really important certificate," Twitter user Dinidu joked. Others took a more helpful approach, with user DTZach suggesting the following: "Can you let us know when the new certificate will expire? We will set a reminder and can inform you before it expires."

As much fun as it is to poke fun at Microsoft for their latest gaffe, the important takeaway here is that the certificate has been renewed, and Teams is functioning properly once again. Hopefully, Microsoft will take the advice of some of its users so this problem doesn't resurface again.

Masthead credit: Shutterstock

Permalink to story.

 
MS repeatedly jacks our company up by their outages. We especially love it when they change things and don't even tell us. So much for "cloud" internet services. Laughing stock of the world, as is all storm "clouds". I still SMH why people continue to host their data on someone else's servers. No control whatsoever. lol
 
Imagine using anything made my Microsoft except Windows, lmao!

FYI, Visual Studio Code is the most popular IDE in the World.

https://insights.stackoverflow.com/survey/2019#technology-_-most-popular-development-environments

The second one is Visual Studio, by the way. Teams usage has already surpassed Slack's. I could go on with examples, but I think you get the idea. Typing this from the Chromium-based Edge browser, which is simply the most responsive browser on my comps.
 
The timing was especially unfortunate as for most workers this morning marked the start of a new work week, when there are important meetings to hold and files to share.
Would that not be the case regardless of timing? There is always something of importance going on.
 
This affected me at work, at the moment we are running Skype for Business and Teams in parallel, but my team have been trying to champion Teams, so this was rather disruptive.

A good number of guys in our Citrix division are championing Teams over Skype for Business and Slack at our corporate offices as well.. they weren't the happiest this morning.. very colorful vocabularies to start off this week.
 
As a small scaled business I don't recall this affecting us. We can always use phones and whatsapp in dire cases..
 
FYI, Visual Studio Code is the most popular IDE in the World.

https://insights.stackoverflow.com/survey/2019#technology-_-most-popular-development-environments

The second one is Visual Studio, by the way. Teams usage has already surpassed Slack's. I could go on with examples, but I think you get the idea. Typing this from the Chromium-based Edge browser, which is simply the most responsive browser on my comps.
Imagine using anything made my Microsoft except Windows and Visual Studio, lmao!
 
Worked on Teams for a second. Horrible mishmash of different languages including python, C++, typescript, others. It was explained to me that was necessary to maintain compatibility across all the different platforms they wanted to cover. I was told I was hired due to my extensive C++ experience, but when I sat down to code I was required to do Typescript, which I had no experience with. Bizarre situation. Left after a month of doing nothing.
 
Worked on Teams for a second. Horrible mishmash of different languages including python, C++, typescript, others. It was explained to me that was necessary to maintain compatibility across all the different platforms they wanted to cover. I was told I was hired due to my extensive C++ experience, but when I sat down to code I was required to do Typescript, which I had no experience with. Bizarre situation. Left after a month of doing nothing.
Your experience was so extensive they thought it's time for you to start with something new for your own good :)
 
Worked on Teams for a second. Horrible mishmash of different languages including python, C++, typescript, others. It was explained to me that was necessary to maintain compatibility across all the different platforms they wanted to cover. I was told I was hired due to my extensive C++ experience, but when I sat down to code I was required to do Typescript, which I had no experience with. Bizarre situation. Left after a month of doing nothing.
My very first project I did for Microsoft was similar. At the time (about 15 years ago now) I was a VB.NET developer and they said, "We only support C# for this project, so you'll have to learn it (and still had a 2 month deadline to make)" and that's how I started. lol In retrospect, I'm glad I was forced to learn C# but a heads up would have been nice. lol
 
Back