Forum Discussion
WebDAV protocol difference from 2016 to 365
Hey Don't know if this is the right forum but hope you can help. I have a client who uses a custom WebDAV on-premise server together with Saperion as document handler, they do NOT use SharePoi...
Another day, another Office unoptimization of interoperability.
Recently people using our webdav solution get blocked by the Office privacy settings for "optional connected experiences". No matter even if the site is under trusted sites or not. And no matter that if you are in an org where you can set these settings yourself when you visit the setting, the optional experiences are already set.
this is not at all mentioned in the Microsoft documents at https://learn.microsoft.com/en-us/deployoffice/privacy/optional-connected-experiences.
Nor probably does this happen when you access a Sharepoint site.
The sort of solution is to add the domain of the site in the inetcpl privacy settings.
However it seems that this panel reduces the domain to almost TLD level, so this can be unworkable for everyone.
Recently people using our webdav solution get blocked by the Office privacy settings for "optional connected experiences". No matter even if the site is under trusted sites or not. And no matter that if you are in an org where you can set these settings yourself when you visit the setting, the optional experiences are already set.
this is not at all mentioned in the Microsoft documents at https://learn.microsoft.com/en-us/deployoffice/privacy/optional-connected-experiences.
Nor probably does this happen when you access a Sharepoint site.
The sort of solution is to add the domain of the site in the inetcpl privacy settings.
However it seems that this panel reduces the domain to almost TLD level, so this can be unworkable for everyone.