No script broke Hotmail / outlook today

[ppb]

Win 7
Firefox latest
NoScript with outlook whitelisted

Changed in the last 24 hours
Hotmail / Outlook gets lost trying to log in or on page refresh and puts up error starting

app: Mail
st: undefined
reqid: undefined
wsver: undefined
efe: undefined
ebe: undefined
et: ClientError
esrc: Script
err: Error: Failed to load LazyModule
Estack estack: 14/j</e.prototype.onLoadFailed/</<@https://outlook.live.com/mail/inbox?bO=1&sessionId=ce . . . . . .

it goes on with several more urls, but I am unsure what to redact that I might keep safe when posting

[Giorgio Maone]

NoScript 11.0.23rc1 (but tested also with 11.0.22).
Firefox 74

I manage to login as long as live.com and office.net are both TRUSTED.

[Hermooz]

Hi all. Just got bitten by this same issue.
For the moment I avoided the issue by disabling NoScript entirely on the tab where I keep Outlook365 page open, but I would like to use a custom-tailored rule instead.
The thing is, that even if I check with debug console enabled I don't see any request that's going in some domain other than Office365.com (which was obviously already trusted). In the previous message there's the suggestion to trust live.com and office.com, but since I don't see request going towards those site, why would I do it?
Is there any other way to troubleshoot what's going on when noscript step in?

thanks for any hint, and best regards!
Fabrizio

[Giorgio Maone]

In the previous message there's the suggestion to trust live.com and office.com, but since I don't see request going towards those site, why would I do it?

Because NoScript tells you it has blocked something on that domain (the new one for me was office.net, the page requesting it for me is https://outlook.live.com/mail/0/inbox), which might have been blocked before anything has a chance to reach the debug console.

[Hermooz]

Hi Giorgio and thanks for the quick reply. Didn't know that NoScript could actually act before the request even reach the debug console!
Actually In the meantime I spotted that the culprit was Office.net, but I got there thru a simple trial and error method.

Ciao!
Fabrizio