Skip to main content
Question

OWA and New outlook sync issues

  • December 11, 2025
  • 4 replies
  • 139 views

ndupeire-d9125e04

Hello everyone!

 

We recently started having issues with Netskope where OWA and Outlook (new) will not sync emails without a manual sync. Outlook (classic) works just fine though.I have had Netskope on my device since May hand have had no issues until Dec 10th. Microsoft may have made some changes, but I'm looking for a fix on the Netskope side. This is affecting all of my users. I've tried temporarily adding steering exceptions for outlook domains, but it has not solved the issue.

 

Thank you all for your help!!!

4 replies

ndupeire-d9125e04

After further investigation it looks like it has something to do with Web applications a whole. Adding MSEdgeWebViewer2.exe to an exception solved the syncing issue. Dropbox is also having issues without that exception. 


joru
Netskope Partner
  • Netskope Partner
  • December 11, 2025

Mmm since yesterday we also detected a similar issue but funny enough was on the contrary in classic outlook could not sync new emails until it was closed and opened again, but in the new Outlook worked ok. As the  MSEdgeWebViewer2.exe process is also related to the Microsoft Edge browser not sure if adding that exception to the certificate pinned apps might bypass inspection by the Netskope agent in said web browser


ndupeire-d9125e04

Yeah, adding it to a pinned app and adding it to the steering exception unfortunately will bypass inspection. Right now this is a temporary fix just to get our users up and running. My goal is to find a more permanent solution but also hopefully figure out what caused this issue yesterday and today. I cant tell if its a MS change or a Netskope backend change.


joru
Netskope Partner
  • Netskope Partner
  • December 11, 2025

Checking a little deeper in the Microsoft documentation the process  MSEdgeWebViewer2.exe is used by several windows apps besides Edge browser (outlook, teams) as a way to handle HTML, CSS and Javascript content in those apps, it seems to be a common process in apps that have a web version and a desktop version in Windows probably to maintain the same look and feel in both environments so it might not bypass the actual traffic of those apps