Others

How to Configure CSPP WOPI Homepage URL Redirection Requirements

Algirdas Jasaitis Sep 29, 2026 870 views

Question details

The user needs to understand how to correctly configure the fallback homepage URL redirection for the Cloud Storage Partner Program (CSPP) when dealing with hash-based routing and permission-controlled WOPI access.

CSPP WOPI Homepage URL Redirection Requirements

Product: Microsoft Cloud Storage Partner Program (CSPP)
Device & OS: not provided
Scenario: Configuring the fallback homepage URL for WOPI integration in an application utilizing role-based access control.
Observed behavior: Application administrators need to ensure unauthorized users do not reach a dead end while properly enforcing backend authorization for WOPI document editing components.

Before you start

Ensure you have administrative access to your application's routing configuration and a clear understanding of your current role-based access control (RBAC) implementation before adjusting the WOPI environment settings.

Solution 1Recommended

Configure a Valid Fallback Homepage URL

Set up a meaningful fallback destination for your WOPI integration to ensure a seamless user experience when users cannot continue editing through Office for the web.

The CSPP homepage URL acts as a fallback destination. Even if your application lacks a traditional public-facing homepage, you must provide a valid, accessible URL that leads to a meaningful location, such as a post-login dashboard.

Identify a landing page

Locate an existing landing page or post-login dashboard within your application (for example, https://xyz.com/admin#home).

Verify URL accessibility

Ensure the selected URL is fully accessible and provides a meaningful interface to users, even if the application relies on hash-based routing.

Update CSPP environment settings

Enter this URL as the designated homepage in your Microsoft Cloud Storage Partner Program (CSPP) WOPI environment settings.

Fallback Destination Purpose: This configuration ensures that if an unauthorized user reaches an Office for the web link, they are gracefully redirected to your application's dashboard rather than encountering a broken page or error.

Solution 2

Implement Role-Based Access Control (RBAC) Safely

Ensure that your role-based access configuration effectively secures documents without creating dead ends for unauthorized users.

Free Microsoft Office alternative

Looking for a Flexible Office Suite? Try WPS Office

If you are exploring robust alternatives to Microsoft Office for your document management and editing needs, WPS Office offers a free, lightweight, and highly compatible solution. It provides a familiar user interface and seamless file compatibility without the overhead of complex enterprise integrations.

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 installer and follow the simple on-screen instructions to set up the lightweight application.
3. Open and manage documents: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office files with perfect formatting preservation.

100% compatible with Microsoft Office formats including DOCX, XLSX, and PPTXLightweight installation with minimal system requirements for faster performanceFamiliar, easy-to-use interface that requires no steep learning curvePowerful built-in tools for document editing, PDF conversion, and secure file sharing

microsoft office alternative - wps office

Frequently Asked Questions

Can I use a URL with hash-based routing as the CSPP homepage?

Yes, you can use a hash-based URL (such as https://xyz.com/admin#home) as long as it successfully resolves to a meaningful landing page or post-login dashboard for the user.

What happens if an unauthorized user clicks an Office for the web link?

If the user is unauthorized, they should not reach a dead end or blank screen. They must be redirected to your configured fallback homepage URL, while your backend simultaneously prevents access to the protected document resource.

Is a traditional public homepage mandatory for the CSPP WOPI requirement?

No, a traditional public-facing homepage is not strictly required. A functional and accessible dashboard or internal landing page is perfectly acceptable as long as it provides a meaningful fallback destination for your users.

Office Quick Solutions