O365 Down. Is it just us?

[AB_IT]

Hi All,

 

This morning been battling with some staff as O365 seems to be down for us. Just wanted to double check and make sure it's not only us, can't seem to find any thread on any forum saying there is issues.

 

Has anyone found out a way around this as of yet? On the admin 'Service Health' page it says they're having problems with eDiscovery however they're only expecting a new update at 4pm today so this would essentially mean we have no email services all working day!

 

Thanks Everyone

 

 

[network41]

No issues here , at the moment anyway 

[AB_IT]

2 minutes ago, network41 said:

No issues here , at the moment anyway 

 

Thanks! So it's not effecting everyone then. So strange. A colleague of mine has also found the following Reddit thread 

 

 

I'm getting the following error message when trying to browse to outlook.office.com/mail

 

UTC Date: 2025-03-28T09:59:27.339Z
Client Id: 45C3DC7AD12B48E2A9CD6A93BCFF949E
Session Id: cfc05766-12ec-4d7d-a95f-8e27bc25cba4
Client Version: 20250307002.17
BootResult: configuration
Back Filled Errors: Unhandled Rejection: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data:undefined|Unhandled Rejection: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data:undefined|Unhandled Rejection: Error: 500:undefined|Unhandled Rejection: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined
err: Microsoft.Exchange.Data.Storage.TenantAccessBlockedException
esrc: StartupData
et: ServerError
estack: s@https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.8b53afd4.js:1:142760
y/</<@https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.8b53afd4.js:1:155397

st: 500
ehk: X-OWA-Error
efe: LO4P265CA0289
emsg: TenantAccessBlockedError

 

 

[Rob_D]

Sorry, email, sharepoint, teams, and admin center are all working fine here.

Edited March 28, 2025 by Rob_D

[3s-gtech]

The eDiscovery issue shouldn't affect email etc.

[PotNoodleTech]

Seems ok here on two different tennancys, touch wood.

[psydii]

We had a bit of oddness yesterday with search (particularly outlook), I figured it was related to the Purview issue - as it seemed (I didn't bother to cross check) from memory that those having issues were those who were also involved in purview cases, and the issues were transient/inconsistent.

 

However specifically relating to your error message that you posted:

 

TenantAccessBlockedError - Microsoft Community

 

Might be worth going through that checklist.

 

Though perhaps the rest of the error you see seems to me more like a problem starting Exchange services after a back-end patch so ::shrug:: 

 

If it is still happening after 10 minutes definitely raise a support ticket  via the admin portal. If you can't get to the admin portal call your CSP and they can take it forward on your behalf.

Edited March 28, 2025 by psydii

[rossibIT]

48 minutes ago, AB_IT said:

 

Thanks! So it's not effecting everyone then. So strange. A colleague of mine has also found the following Reddit thread 

 

 

I'm getting the following error message when trying to browse to outlook.office.com/mail

 

UTC Date: 2025-03-28T09:59:27.339Z
Client Id: 45C3DC7AD12B48E2A9CD6A93BCFF949E
Session Id: cfc05766-12ec-4d7d-a95f-8e27bc25cba4
Client Version: 20250307002.17
BootResult: configuration
Back Filled Errors: Unhandled Rejection: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data:undefined|Unhandled Rejection: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data:undefined|Unhandled Rejection: Error: 500:undefined|Unhandled Rejection: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined
err: Microsoft.Exchange.Data.Storage.TenantAccessBlockedException
esrc: StartupData
et: ServerError
estack: s@https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.8b53afd4.js:1:142760
y/</<@https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.8b53afd4.js:1:155397

st: 500
ehk: X-OWA-Error
efe: LO4P265CA0289
emsg: TenantAccessBlockedError

 

 

Thanks for this. Had a SAR that I was planning on doing today and getting some weird messages. 

Regards

Ross

[AB_IT]

Thanks all for your help and input. We've discovered that for some reason our reseller have removed all our licenses from our Tenant. Working with them to try and get something sorted.

[pete]

eDiscovery and Content Search export (classic and new version) are both broken and have been since 25th March.  Most likely due to the idiots pushing breaking changes to production.  You'll get a JSON error message and if you press F12 it's a 500 error (even if you have appropriate permissions in 365 and roles in Purview).

 

*is also processing a SAR*