Fix Word Cannot Open SharePoint On-Premises Files via Azure AD Proxy
Question details
The user is unable to open SharePoint 2013 on-premises documents using the Microsoft Word desktop application when routed through an Azure AD Application Proxy.

- Product
- Microsoft Word, SharePoint 2013
- Device & OS
- not provided
- Scenario
- Attempting to access and edit SharePoint on-premises files using the Word desktop client via an Azure AD Application Proxy.
- Observed behavior
- The Word desktop application returns an HTTP 403 Forbidden error, despite Office for the web successfully opening the files with the same user account.
Verify that your Azure AD Application Proxy is properly configured to pass authentication tokens to desktop client applications, and ensure you can still access the portal normally via your web browser.
Consult the Microsoft Q&A SharePoint Server Category
Because this issue involves SharePoint Server 2013 on-premises architecture and complex Azure AD Application Proxy routing, it requires specialized IT infrastructure support.
Most standard community forums focus heavily on SharePoint Online. For on-premises environments integrated with modern Azure AD proxies, specialized engineers are needed to investigate token passing, conditional access policies, and Office desktop integration.
Open your browser and visit the official Microsoft Q&A portal.
Use the search or filtering tools to navigate to the 'SharePoint Server' tag, ensuring you are not in the SharePoint Online section.
Submit a new question detailing your environment (SharePoint 2013 on-premises), the proxy being used (Azure AD Application Proxy), and the specific error (HTTP 403 Forbidden in Word desktop but working in Office web).

Clear Windows Credentials and Office Cache
Clear local authentication tokens to force the Word desktop app to request a fresh connection through the Azure AD Proxy.
Try WPS Office for Seamless Document Management
Dealing with complex SharePoint on-premises configurations, Azure AD proxies, and HTTP 403 errors in Microsoft Word can disrupt your workflow. WPS Office provides a lightweight, highly compatible alternative that makes editing and managing your documents straightforward and hassle-free without enterprise authentication barriers.
- 1. Download the installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
- 3. Open your documents: Launch WPS Writer and open your .docx files directly from your local drive or standard cloud storage.

Frequently Asked Questions
Why does Office for the web work but Word desktop returns a 403 error?
Office for the web relies on browser-based cookie authentication, which seamlessly passes through the Azure AD Application Proxy. The desktop Word app uses modern authentication protocols that may require specific proxy configurations or conditional access adjustments to route correctly.
Can I bypass the Azure AD Application Proxy to open these SharePoint files?
If you are connected directly to the corporate network or via a company VPN, you might be able to access the SharePoint 2013 on-premises URL directly. This bypasses the external Azure AD Application Proxy routing and often resolves desktop client authentication errors.
Is SharePoint 2013 still supported for modern Azure AD integration?
SharePoint 2013 reached its end of extended support in April 2023. Continuing to integrate it with modern authentication architectures like Azure AD Application Proxy may lead to compatibility issues, and upgrading to a newer server version or SharePoint Online is strongly advised.




