Microsoft Teams went down this morning for nearly three hours after Microsoft forgot to renew a critical security certificate. Users of Microsoft’s Slack competitor were met with error messages attempting to sign into the service on Monday morning, with the app noting it had failed to establish an HTTPS connection to Microsoft’s servers.
Microsoft confirmed the Teams service was down just after 9AM ET today, and then later revealed the source of the issue. “We’ve determined that an authentication certificate has expired causing users to have issues using the service,” explains Microsoft’s outage notification. Microsoft then started rolling the fix out at 11:20AM ET, and by 12PM ET the service was restored for most affected users. Microsoft confirmed the fix was successfully deployed at 4:27PM ET.
This was an embarrassing mistake for Microsoft to make for its flagship “Office hub” software, especially as the company started its own TV commercials for Teams recently. It’s also surprising to see Microsoft forget to renew a key certificate for Teams, especially when the company develops software like System Center Operations Manager to monitor for things like certificate expiration.
Update, February 3rd 4:40PM ET: Added confirmation from Microsoft that the fix was successfully deployed.
BCProgramming on February 3rd, 2020 at 23:29 UTC »
My favourite is how Teams doesn't even add it's autorun entry correctly. It doesn't quote the file path, and since it get's installed into the Program Files folder, windows tries to start "C:\program.exe" and can't find it.
It's the kind of thing that is expected for software that was written in 1995 but is inexcusable now.
5of10 on February 3rd, 2020 at 22:28 UTC »
Guess they forgot to add it as a task on the new ToDo application they launched....
TemporaryBoyfriend on February 3rd, 2020 at 21:15 UTC »
So that’s what happened. And technically, it’s Office 365. They get to take a day off, since there will be 366 days this year.