Validate one workflow first.
Use a single-server evaluation environment to confirm the file path, browser experience, callback exchange, and result handling before broad rollout.
Start with a focused proof of concept, verify the target workflow, then align the production environment with the current deployment guidance. The application that owns users, files, permissions, and business data remains the integration boundary.
A sample Office surface for products that keep a document beside the work around it.
Use these pages to decide which workflow, format, and ownership boundary should be validated first.
Use a single-server evaluation environment to confirm the file path, browser experience, callback exchange, and result handling before broad rollout.
Office SDK is evaluated as a web-based document surface inside the product your users already access on desktop and mobile browsers.
The current deployment guidance provides an Ubuntu 22.04 or 24.04 x86 baseline. Confirm resource sizing, topology, and version requirements with engineering.
Deployment planning should identify the service that stores files, issues access decisions, receives callbacks, and records business-level audit history.
An Office SDK deployment is the operating arrangement that delivers the document surface in the browser while your services retain file storage, identity, permission, and business-record responsibility.
Start with one workflow and one representative file path before broad rollout.
The current guidance names Ubuntu 22.04 and 24.04 on x86 for planning.
Desktop and mobile browser access belong in the acceptance plan.
| Stage | Environment question | Evidence to keep |
|---|---|---|
| Proof of concept | Can the target workflow open, edit, and return a result? | Test file, browser trace, callback log, and owner sign-off |
| Web delivery | Can intended users reach the surface from supported browsers? | Desktop and mobile acceptance notes |
| Production | Can the operating team recover and observe the service? | Sizing, deployment record, monitoring, and rollback plan |