All users impacted have the Forcepoint proxy client. It was forcepoint direct connect client i was installing to rectify the issue though, whether it was changing to the direct connect client or the different version that fixed it is unclear.
I would say all the user impacted were exchange on-prem, we are currently migrating the entire company so we have a large mix.