I've noticed that Microsoft has switched M365 app updates from relying on Delivery Optimization (DoSvc) to using the WebView2 runtime, and I'm curious about the implications of this change. Normally, DoSvc allows us to manage updates more strictly—setting policies for caching, bandwidth usage, and timing. But with this switch to WebView2, we seem to lack those controls. This change could lead to M365 apps like Teams consuming a lot of bandwidth unexpectedly, especially for users on limited connections. I've confirmed this with engineering contacts at Microsoft, and it's concerning because it seems there's no way to control this new update behavior. Has anyone found effective ways to manage or mitigate this issue?
3 Answers
Also, the recent WebView2 update seems to mess with SAML SSO when using WatchGuard VPNs, which is another headache to deal with. Has anyone else experienced this?
When did this become a thing? We had to disable Delivery Optimization recently for other reasons, and now I see Teams is just stuck without updates. I didn’t think it would come to this.
Honestly, this change feels like typical Microsoft. They often make decisions that complicate management for admins like us. It's a real head-scratcher why they’d move to WebView2 without providing enterprise controls. Now, with no options to manage this traffic, we're just waiting for our networks to buckle during updates. It’s frustrating to see.
Right? And with the way DoSvc was designed to give us control, making this sudden switch seems reckless. We can’t afford for our connections to drop every time there's an update. It's like they just threw the controls out the window.
It hit us hard this week! There were widespread outages caused by this update. We didn’t even know what was going on at first.