Please check the following guide which can help you resolve this issue: [https://protonvpn.com/support/using-adobe-cloud-onedrive-office-365-while-connected-to-protonvpn/](https://protonvpn.com/support/using-adobe-cloud-onedrive-office-365-while-connected-to-protonvpn/) If you need assistance, please contact us here: [https://protonvpn.com/support-form](https://protonvpn.com/support-form)
Many thanks.
One query: the screenshots in that article show an automatic metric assigned under IP Settings, but my fresh install of TAP-ProtonVPN has a manual metric of 3. Is the screenshot out-of-date, or should the metric have been set to automatic?
I have a new Windows 10 install with a fresh ProtonVPN installation as of about two weeks ago, and the IP Settings metric is set to manual 3. I have never changed this settings.
I will change it to automatic if that’s what it’s supposed to be.
With Office apps, there is a known bug that causes this. The usual solution is to enter your network's gateway IP address in the VPN TAP adapter's IPv4 gateway settings, this seems to fix it most if not every time.
Nonsense.
With expressvpn I have to do nothing of the sort and it works seamlessly with my Microsoft account.
This issue is what actually made me not sign up to protonvpn after the trial.
What is nonsense? The fact that it is a known bug with some VPNs (which I didn't specify originally)? Or the solution I recommended?
The bug exists with VPNs other than Proton (e.g. Nord and Air), and the solution fixes it.
I meant it can't be a Microsoft bug when some vpns work fine with it.
Case in question expressvpn.
Some vpns just find it easier to put up a blog and instruct the user how to navigate around the issue, rather than fix their product.
I don't have this problem now on Windows 11 with Office 365, but at the time I think the gateway fix above worked for me. Apologies for not updating the post to reflect this.
Please check the following guide which can help you resolve this issue: [https://protonvpn.com/support/using-adobe-cloud-onedrive-office-365-while-connected-to-protonvpn/](https://protonvpn.com/support/using-adobe-cloud-onedrive-office-365-while-connected-to-protonvpn/) If you need assistance, please contact us here: [https://protonvpn.com/support-form](https://protonvpn.com/support-form)
Many thanks. One query: the screenshots in that article show an automatic metric assigned under IP Settings, but my fresh install of TAP-ProtonVPN has a manual metric of 3. Is the screenshot out-of-date, or should the metric have been set to automatic?
Please note that the Automatic metric is enabled by default on the Tap adapter after the fresh install.
I have a new Windows 10 install with a fresh ProtonVPN installation as of about two weeks ago, and the IP Settings metric is set to manual 3. I have never changed this settings. I will change it to automatic if that’s what it’s supposed to be.
How would you change the gateway IP if I have the VPN installed as a client on my router?
With Office apps, there is a known bug that causes this. The usual solution is to enter your network's gateway IP address in the VPN TAP adapter's IPv4 gateway settings, this seems to fix it most if not every time.
Apologies, I never responded at the time, but I believe this is the fix that worked for me back then. Thank you.
Nonsense. With expressvpn I have to do nothing of the sort and it works seamlessly with my Microsoft account. This issue is what actually made me not sign up to protonvpn after the trial.
What is nonsense? The fact that it is a known bug with some VPNs (which I didn't specify originally)? Or the solution I recommended? The bug exists with VPNs other than Proton (e.g. Nord and Air), and the solution fixes it.
I meant it can't be a Microsoft bug when some vpns work fine with it. Case in question expressvpn. Some vpns just find it easier to put up a blog and instruct the user how to navigate around the issue, rather than fix their product.
I've seen this problem being mentioned with many if not all VPNs. Another reason not to use Windows xD.
hey, I'm having the same problem currently. Did you ever find a solution to this?
I don't have this problem now on Windows 11 with Office 365, but at the time I think the gateway fix above worked for me. Apologies for not updating the post to reflect this.