Error: 'Word cannot open the document: user does not have access privileges' on Mac OS Sierra with Office 2016

Question

When I click on a link to open / edit a Word-document from an online filesharing source (e.g. a Kentico or eXo Platform intranet), Word for Mac is started correctly, but then the message ‘‘Word cannot open the document: user does not have access privileges’ pops up and the document cannot be opened:

The peculiar thing is that opening / editing Excel or Powerpoint files from the same online sources goes without problems. The same applies to opening these Word documents from a browser on a Windows PC. Besides, when I download the Word documents to my MacBook and open them from my local drive, there are no problems at all. Also, when I open the same files via OneDrive in my browser and click on ‘Edit in Word’, this goes without problems.

Does anybody have a clue what might cause this? I have tried all potential fixes that I could find in the Microsoft Forums and elsewhere to resolve this issue:

1. Tested with different machines (MacBook Pro, MacBook and iMac)
2. Tested with different browsers on my Mac
3. Tested with different online filesharing platforms that have Office integration
4. Checked permissions on the files
5. Repaired disk permissions on my Mac
6. Reset home folder permissions on my Mac
7. Tested with a new user profile
8. Logged out of Word 2016
9. Removed remnants of Office 2011
10. Removed Office plist files
11. Removed containers for Office apps
12. Removed old font files stored by Office 2011
13. Removed font collections
14. Deleted all fonts
15. Cleaned font cache with FontNuke
16. Removed normal.dot and backup
17. Removed all Microsoft entries in keychain
18. Booted in safe mode

etc.

Nothing helped.

For more details, see this document: https://1drv.ms/w/s!An9V\_kOPpd0Mhqp60gP9r5C0CgZeBQ

Answer 1

Update:  I just heard from Tier 2.  Once they finally confirmed that they understood my issue, they proceeded to try to tell me that they thought it was a software incompatibility between Word 2016 and my client's SharePoint.

I pointed out that my client uses Office 365 and is using their own person SharePoint directory.

Nonetheless, the Tier 2 agent was only grasping at straws and did not have any technical replies or steps for me.  I thought for sure that this was logged in their system, as earlier posts here state that this issue is a "Microsoft Office for Mac, that has been reported as early as December 2013.

Anyhow, with some urging, the agent is escalating to the Engineering department.  Thanks, I guess, but now have to wait for any updates, I suppose.