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
Sample Word document.docxDOCX · preview surface
Preview
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.
01
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.

02
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.

03
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.

04
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.

IN ONE SENTENCE

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.

1 workflow:

focused proof of concept

Start with one workflow and one representative file path before broad rollout.

2 baselines:

Ubuntu baselines

The current guidance names Ubuntu 22.04 and 24.04 on x86 for planning.

2 contexts:

browser contexts

Desktop and mobile browser access belong in the acceptance plan.

COMPARE THE BOUNDARY

Separate evaluation from production planning

StageEnvironment questionEvidence to keep
Proof of conceptCan the target workflow open, edit, and return a result?Test file, browser trace, callback log, and owner sign-off
Web deliveryCan intended users reach the surface from supported browsers?Desktop and mobile acceptance notes
ProductionCan the operating team recover and observe the service?Sizing, deployment record, monitoring, and rollback plan
APPLY THE GUIDANCE

Four checks before the next decision.

  1. Choose one workflow and document its file, identity, permission, and result boundaries.
  2. Validate the single-server proof of concept from the same network path users will use.
  3. Plan the production baseline, observability, recovery owner, and version policy.
  4. Repeat the acceptance workflow after deployment and retain the evidence with the release record.
RELATED STANDARDS AND CONTEXT

Review the supporting material.