Live data from Hacker News

Microsoft 365 Outage

status.office365.com

31–40 of 166 posts

Re: Microsoft 365 Outage

#31

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")

Doesn't work for me, I get:

At line:1 char:16 + $loop = "loop" do {$response = $null; Start-Sleep -Seconds 5 try {$re ...

+ ~~

Unexpected token 'do' in expression or statement.

+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException

    + FullyQualifiedErrorId : UnexpectedToken

Re: Microsoft 365 Outage

#32
post #30

https://twitter.com/msft365status?lang=en

> 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.

Category 503 hurricane centered over Redmond, WA

Re: Microsoft 365 Outage

#33

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…

Most of the elements you'd want on a status page are there, but the tone and structure are really off. I think you nailed it that this reads like an internal communication to a manager, not to a customer.

Re: Microsoft 365 Outage

#35

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’s the “oh crap, there is an unsurmountable obstacle in between the end users and the admin portal. We have to say something now” page. Most of the time, service alerts are supposed to be reported through the Azure or MS365 admin portals.

Re: Microsoft 365 Outage

#36

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")

Doesn't work for me, I get: At line:1 char:16 + $loop = "loop" do {$response = $null; Start-Sleep -Seconds 5 try {$re ... + ~~ Unexpected token 'do' in expression or statement. + CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException + FullyQualifiedErrorId : UnexpectedToken

Sorry about that - I have no idea how to format comments. I placed a copy here: https://www.codepile.net/pile/gz77EXzd

Re: Microsoft 365 Outage

#38

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")

Doesn't work for me, I get: At line:1 char:16 + $loop = "loop" do {$response = $null; Start-Sleep -Seconds 5 try {$re ... + ~~ Unexpected token 'do' in expression or statement. + CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException + FullyQualifiedErrorId : UnexpectedToken

Cleaned-up version

while ($true) { $response = $null; try { $response = Invoke-WebRequest "https://login.microsoftonline.com/common/oauth2/" -ErrorAction SilentlyContinue | select status*; if ($response) { "OK $($response.StatusCode) $(Get-Date)" | Write-Host; } } catch { "Down $(Get-Date)" | Write-Host; }; Start-Sleep -Seconds 5; }

Re: Microsoft 365 Outage

#39

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…

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

> 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.

Current status: We've identified that reverting the recent change did not alleviate impact to Microsoft services as expected. We're working to explore additional options for mitigation.

[I actually enjoy these updates but they indeed read more like our internal incidents channel]

Re: Microsoft 365 Outage

#40

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

Funnily enough the community/free version works without issues. That really sucks if you're a paying customer.
Post reply on HN