POC
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.
DEPLOYMENT FIT
Plan a deployment around the system you already operate.
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.
OFFICE SDK / DEPLOYMENT FIT
12345
ILLUSTRATIVE SAMPLE / OFFICE WORKFLOW
Keep the file
with the work.
A sample Office surface for products that keep a document beside the work around it.
Illustrative sample
Product context → Office surface → business result
A CLEAR BOUNDARY
Useful detail for the next technical question.
Use these pages to decide which workflow, format, and ownership boundary should be validated first.
Your system keeps file storage and permissions.
Preview, edit, review, import, and export are separate decisions.
Callbacks and SDK surfaces connect the document to your product.
WEB DELIVERY
Meet users in the browser.
Office SDK is evaluated as a web-based document surface inside the product your users already access on desktop and mobile browsers.
PRODUCTION BASELINE
Use the documented platform baseline.
The current deployment guidance provides an Ubuntu 22.04 or 24.04 x86 baseline. Confirm resource sizing, topology, and version requirements with engineering.
OWNERSHIP
Keep storage and permissions in your system.
Deployment planning should identify the service that stores files, issues access decisions, receives callbacks, and records business-level audit history.