4 ms·

While it is true that Teams does often use inexplicably high amounts of CPU and network bandwidth (at least on my machine) - I'm not sure that Electron is at fa

by hooby 5y ago

While it is true that Teams does often use inexplicably high amounts of CPU and network bandwidth (at least on my machine) - I'm not sure that Electron is at fault - at least not in my case. I only figured it out by accident - through the Microsoft Authenticator App I got to a login/authentication history somewhere, and there I saw that Teams was automatically re-authenticating itself in the background. Probably some sort of token renewal or something. But it was doing that LOTS. Like 2 or 3 times per SECOND. And once it starts doing that, it seems to be doing that indefinitely (until you restart the app) - with absolutely no hint of what's happening inside the app.

politician 5y ago
Microsoft just has no idea how to do auth well. Many of their online web properties follow these tortured redirect chains for authentication. I just cannot even count the number of times I've ended up in some horked state while trying to view something on O365 like email quarantine. I'm not surprised to hear that their apps are generating auth storms.
- Spooky23 5y ago
  My theory is that they are torturing you to give up and use Azure AD. The other big issue is that they saddled with the technical debt of legacy auth, and many failure scenarios lead to that path, which really sucks.
filoleg 5y ago
Oh god, this confirms what I've observed visually. A few times I got into a weird auth bug scenario, where if a window popped up to auth, and I didn't get it right the first time, it would send me into an endless loop of popping out auth windows (while Teams shows me offline). Whether I succeed with auth in the subsequent windows or not, or even whether i just dismiss the window, it doesn't matter. They kept popping up almost instantly again, dragging away window focus from whatever other application window was in focus. Even closing Teams wouldn't help, only reboot would reliably resolve it (though given how few times I've observed it, I didn't bother looking deeper than that into it). And that was on macOS.
- Galanwe 5y ago
  I have the same issue with the android client. Sometimes it just keeps refreshing forever. Nothing less than a reboot of the phone works.
Saig6 5y ago
It could be refreshing tokens before every API request in an attempt to avoid 1. API request, 2. 401. 3. refresh token 4. redo request? Not that that makes any sense, msal.js will refresh cached tokens before they time out.
- hooby 5y ago
  Seems unlikely. It usually works fine for an hour or two after restarting the app - and then it suddenly starts refreshing endlessly as fast as it can. There's no visible reason why it would suddenly be doing so many API requests, and wasn't doing them before. (And then stops doing them again, after being restarted.)
cookiengineer 5y ago
If you work in an enterprise environment where the microsoft domains are whitelisted, but cdn.office.net is not...you'll end up with a couple hundred requests per second because it keeps trying to refresh all emojis, folder icons and others in an endless loop. I'm not kidding you. They DDoS themselves because the app apparently doesn't cache anything. Oh, and don't try what happens when skype.com doesn't work. The whole app goes maniac then.
- dzhiurgis 5y ago
  > domains are whitelisted Why people still do that?
  - deleted 5y ago
    [deleted]
  - Spooky23 5y ago
    Microsoft doesn’t publish an accurate list of IP ranges, and pushes many things to Akamai, so you need to whitelist a few dozen domains. When I ran a very large O365 environment, it was even harder as we had a dedicated 10Gb circuit to Microsofts network, and and depending on various bugs, conditions, etc, you could easily send traffic to the wrong place and impact performance. (For example, if you inspect TLS traffic, that latency will kill Outlook application performance)
- hooby 5y ago
  cdn.office.net is fully, unrestrictedly accessible. Also, I believe those re-authentications are actually ALL the app is doing in those moments. It's not actually loading anything, not emojis, not notifications or anything else (all of the app still works normally) - it's just re-authenticating, re-authenticating, re-authenticating, re-authenticating... in the background (eating quite a bit of CPU and bandwidth in the process).

by hooby 5y ago

politician 5y ago

Microsoft just has no idea how to do auth well. Many of their online web properties follow these tortured redirect chains for authentication. I just cannot even count the number of times I've ended up in some horked state while trying to view something on O365 like email quarantine. I'm not surprised to hear that their apps are generating auth storms.

Spooky23 5y ago
My theory is that they are torturing you to give up and use Azure AD. The other big issue is that they saddled with the technical debt of legacy auth, and many failure scenarios lead to that path, which really sucks.

filoleg 5y ago

Oh god, this confirms what I've observed visually. A few times I got into a weird auth bug scenario, where if a window popped up to auth, and I didn't get it right the first time, it would send me into an endless loop of popping out auth windows (while Teams shows me offline). Whether I succeed with auth in the subsequent windows or not, or even whether i just dismiss the window, it doesn't matter. They kept popping up almost instantly again, dragging away window focus from whatever other application window was in focus. Even closing Teams wouldn't help, only reboot would reliably resolve it (though given how few times I've observed it, I didn't bother looking deeper than that into it). And that was on macOS.

Galanwe 5y ago
I have the same issue with the android client. Sometimes it just keeps refreshing forever. Nothing less than a reboot of the phone works.

Saig6 5y ago

It could be refreshing tokens before every API request in an attempt to avoid 1. API request, 2. 401. 3. refresh token 4. redo request? Not that that makes any sense, msal.js will refresh cached tokens before they time out.

hooby 5y ago
Seems unlikely. It usually works fine for an hour or two after restarting the app - and then it suddenly starts refreshing endlessly as fast as it can. There's no visible reason why it would suddenly be doing so many API requests, and wasn't doing them before. (And then stops doing them again, after being restarted.)

cookiengineer 5y ago

If you work in an enterprise environment where the microsoft domains are whitelisted, but cdn.office.net is not...you'll end up with a couple hundred requests per second because it keeps trying to refresh all emojis, folder icons and others in an endless loop. I'm not kidding you. They DDoS themselves because the app apparently doesn't cache anything. Oh, and don't try what happens when skype.com doesn't work. The whole app goes maniac then.

dzhiurgis 5y ago
> domains are whitelisted Why people still do that?
- deleted 5y ago
  [deleted]
- Spooky23 5y ago
  Microsoft doesn’t publish an accurate list of IP ranges, and pushes many things to Akamai, so you need to whitelist a few dozen domains. When I ran a very large O365 environment, it was even harder as we had a dedicated 10Gb circuit to Microsofts network, and and depending on various bugs, conditions, etc, you could easily send traffic to the wrong place and impact performance. (For example, if you inspect TLS traffic, that latency will kill Outlook application performance)
hooby 5y ago
cdn.office.net is fully, unrestrictedly accessible. Also, I believe those re-authentications are actually ALL the app is doing in those moments. It's not actually loading anything, not emojis, not notifications or anything else (all of the app still works normally) - it's just re-authenticating, re-authenticating, re-authenticating, re-authenticating... in the background (eating quite a bit of CPU and bandwidth in the process).