Reference architecture for an owned workplace
Plan an owned workplace across identity, files, office editing and communication, with clear service boundaries, user lifecycle checks and recovery ownership.
Last updated
In short
- Identity continuity and file ownership must be designed together.
- Browser office editing adds its own network and licensing boundary.
- Mail, calendars and endpoint management need an explicit scope decision.
On this page (6)
Architectures · Part of Sovereign workplace
Define the workplace service before choosing applications
An owned workplace is a set of coordinated services: identity, files, document editing, communication, recovery and employee support. Installing several applications does not by itself produce a coherent workplace. The hardest decisions often concern who owns a departing employee’s documents, how guests are restricted and what continues working during an identity outage.
This reference architecture describes a pilot boundary. It is not a claim of a tested deployment or complete Microsoft 365 feature parity. The sovereign workplace overview explains the broader service direction; this page provides the component and acceptance model needed to make an implementation reviewable.
Give each component a specific job
| Service | Reference component | Boundary to establish |
|---|---|---|
| Organizational identity | Existing directory with Keycloak where needed | Immutable user IDs, authentication policy and account lifecycle |
| Files and sharing | Nextcloud | Ownership, internal groups, guest sharing and storage quotas |
| Browser document editing | Collabora Online connected to Nextcloud | WOPI trust, supported formats and production licensing |
| Team communication | Selected messaging service such as Mattermost | Edition, guests, history, retention and mobile access |
| Mail and calendars | Retained or separately selected service | Mailbox migration, domains, scheduling and mobile clients |
| Operations | Backup, monitoring and support processes | Access, response responsibilities and restore evidence |
Keep mail and calendar decisions explicit. A file platform and browser editor do not automatically replace Exchange mailboxes, Outlook behavior, meeting-room booking or device management. Retaining a subscription for those workloads is a valid transitional design and belongs in the cost comparison.
The connection between Nextcloud and the editor is also a separate service dependency. Nextcloud’s Office configuration defines the editor endpoint and WOPI-related controls. Collabora’s FAQ distinguishes its development offering from a supported production deployment. Select the actual edition and record its licence before treating browser editing as a production commitment.
Map the request and failure paths
A user first authenticates, then receives application-specific access. Opening a file requires the file service and its storage. Editing additionally requires the editor service and browser connectivity to that service. Sending a message has its own database and attachment dependencies. These paths can fail independently.
| Failure | Intended user experience | Operational evidence |
|---|---|---|
| Identity provider unavailable | Existing sessions behave according to documented lifetimes; new logins show a clear failure | Session and outage drill |
| Editor unavailable | Files remain available for approved download or later editing | File access and unsaved-change checks |
| File storage unavailable | Writes fail visibly; clients do not report false success | Storage failure exercise |
| Messaging unavailable | Staff use an agreed alternative contact route | Incident communication record |
| Backup destination unavailable | Production can continue while recovery exposure is alerted | Backup-age alert and escalation |
Do not promise that every application honors upstream logout immediately. The Keycloak administration guide covers identity sessions and brokering, but each downstream application still has its own session behavior. Measure the end-to-end result for the selected versions.
Rehearse one employee lifecycle
Use synthetic accounts for a new employee, their manager, an external collaborator and a service administrator. The employee joins an engineering group and receives only the intended file and communication spaces. They create a document, share it internally and invite the collaborator to one approved location. The collaborator must not gain access to other engineering content through search, previews or inherited permissions.
Next, move the employee to another department. Check group changes, cached sessions and existing shares. Finally, disable the account and transfer the necessary files to the manager under the organization’s policy. Verify desktop synchronization, application passwords, mobile sessions and previously shared links separately. An upstream account disablement is only one step in that offboarding sequence.
Record the user identifier used in every component. Changing an email address should not create an unintended second account or orphan documents. Existing account linking deserves a rehearsal before enabling automatic account creation for the whole workforce.
Measure document fidelity with real working patterns
A representative document set should include tracked changes, comments, tables, fonts, formulas, charts, protected sheets and templates. The team responsible for each workflow should compare rendered appearance and actual behavior. A file opening successfully is not enough when a spreadsheet drives a business decision.
Include simultaneous editing, a browser reconnect, a desktop sync conflict and a large attachment. Record the source and target formats, editor release and fonts installed. Where a required macro or integration does not work, retain the original workflow or redesign it explicitly; do not hide that dependency in a general adoption percentage.
Agree on versions, recovery and ownership
Maintain a compatibility inventory for the directory connector, Nextcloud server and apps, editor, messaging edition, database and desktop clients. Separate freely available features from paid SSO, support or retention capabilities. Pilae service scope and current pricing must be agreed against that inventory.
Backups should capture application databases, files, configuration and the secrets needed to decrypt them. Restore a pilot into isolation and check identity mappings, file ownership and editor access before allowing users onto it. A rollback after a live cutover also needs a plan for documents and messages created in the new system; restoring an old snapshot without reconciliation loses that work.
The pilot is ready for expansion when the lifecycle checks pass, representative documents are accepted, recovery is demonstrated and every service has an accountable owner. Those outcomes provide a stronger basis for migration than a list of installed applications.
Sources and further reading
Use the linked documentation to confirm the version, edition and contract that apply to your project.
