[HN Gopher] Microsoft 365 Widespread Outage
___________________________________________________________________
Microsoft 365 Widespread Outage
Author : psim1
Score : 72 points
Date : 2020-09-28 22:08 UTC (51 minutes ago)
(HTM) web link (status.office365.com)
(TXT) w3m dump (status.office365.com)
| OkGoDoIt wrote:
| 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
| thanatos519 wrote:
| 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.
|
| Current status: We've identified and are reverting a recent
| change to the service which may be causing or contributing to
| impact.
|
| Scope of impact: Any user may experience access problems for
| Microsoft 365 services.
| bluedino wrote:
| >> More info: Users would be unable to access Outlook.com,
| Microsoft Teams including Teams Live Events, and Office.com.
|
| Not even English.
| stefan_ wrote:
| The (c)2019 Microsoft Corporation is a nice touch. There isn't
| a date on this entire page!
| thanatos519 wrote:
| Seriously!!! How about the "Add this page to your favorites"
| link? I guess the 365 target audience still hasn't learned
| how to bookmark.
|
| Anyways the Azure status page is a bit more grown up:
|
| https://status.azure.com/en-us/status
| lucasmullens wrote:
| That button doesn't work in Chrome, which almost certainly
| means it doesn't even work in Microsoft's own browser
| (since Edge is Chromium-based now)
| tyingq wrote:
| Yes, that's pretty nice. A clear, concise, and accurate
| description of the problem, noting that the change is bring
| reverted.
| thanatos519 wrote:
| Absolutely! It's more about the presentation.
|
| "Title:" makes it look like a grade school book report.
| mikequinlan wrote:
| https://portal.office.com/servicestatus
|
| Title: We're investigating a potential issue affecting
| Outlook.com
|
| User Impact: Affected users may be unable to access Outlook.com
| services or features.
|
| Current status: We've identified a recent change that appears
| to be the source of the issue. We're rolling back the change to
| mitigate impact.
|
| Next update by: Monday, September 28, 2020, at 11:00 PM UTC
| Animats wrote:
| "No one was ever fired for buying Microsoft" just ended.
| jimnotgym wrote:
| If uptime was your only metric...
| riffic wrote:
| Oh please! This sort of outage is regular for O365.
| thanatos519 wrote:
| Maybe they should have called it O364.
| rachelbythebay wrote:
| O365 makes sense if it's down all day, since this _is_ a
| leap year, after all.
| pgn674 wrote:
| The exact-ish length of a year is 365.2422 days. 365 days
| a year is three nines of uptime (99.93369%).
| [deleted]
| ponker wrote:
| You must not have heard the old joke "Office 361."
| bluedino wrote:
| The best part: "Add this page to your favorites"
|
| The link is _javascript:window.external.AddFavorite(location.href
| ,%20document.title);_
| imperialdrive wrote:
| I'm using this to test for return of service: $loop = "loop" do
| {$response = $null; Start-Sleep -Seconds 5 try {$response =
| Invoke-WebRequest
| "https://login.microsoftonline.com/common/oauth2/" -ErrorAction
| SilentlyContinue | select status*} catch {Write-Host "Down $(get-
| date)"} finally {} if ($response) {Write-Host "OK"
| ($response).StatusCode (Get-Date)} } while ($loop -eq "loop")
| AmateurAlert wrote:
| https://twitter.com/msft365status?lang=en
| annoyingnoob wrote:
| You could play status page roulette...
|
| https://status.azure.com/en-us/status
|
| https://status.office365.com
|
| https://portal.office.com/servicestatus
| filmgirlcw wrote:
| #HugOps to the SRE's rolling back changes. I can't reliably
| access anything right now so I'll just use this as an excuse to
| take a brief walk.
| x86_64Ubuntu wrote:
| You hope that the walk only need to be brief...
| filmgirlcw wrote:
| I mean, indeed. But it's good to get some air (wearing a
| mask, of course) anyway.
| joemaller1 wrote:
| Seems to be Azure-related, all sorts of stuff is not accessible
| right now.
| mastry wrote:
| Yep. I can't get into the azure portal.
| DrPhish wrote:
| Specifically Azure Active Directory
|
| We (like many other orgs, I expect) have gone all-in on AAD, so
| this has pretty much taken down everything company wide with
| the exception of the factories. Good thing the plant floor
| isn't tied in.
___________________________________________________________________
(page generated 2020-09-28 23:00 UTC)