Office for the web environments
Office for the web provides two environments that cloud storage partners can use. The WOPI discovery URLs for each environment are provided below.
Initially you're given access to the test environment (also called Dogfood), that you use when building and testing your integration.
Once you are ready to release your integration, you can start the Launch process. As part of that process, your application is given access to the production environment.
The test environment is updated frequently - usually at least once per day - and all initial testing should be done against it. Initially, this is the only environment you can access.
The test environment runs the most recent Office for the web code available. This means that you might see features there that aren't yet available in production. However, the WOPI interactions between Office for the web and your WOPI host should not differ dramatically between test and production.
Because builds are deployed frequently to this environment, you might see regressions in behavior. However, the deployment cadence supports pushing changes quickly, so contact Microsoft if you experience any strange or unexpected behavior when using the test environment.
End users shouldn't access the test environment. If you're making Office for the web integration available to your end-users, you must be in the production environment.
The production environment is updated weekly.
Primary requirements for production environment
This is not an exhaustive list.
- Hosts must use HTTPS in the production Office for the web environment. HTTP isn't supported.
- Domains on the WOPI domain allow list must be a WOPI-dedicated subdomain in production.
- Domains must be owned by the partner.
- Production changes can take 3-4 weeks to fully roll out; this includes domain changes.
WOPI discovery URLs