Orbit documentation
The evidence behind the product story.
Clear enough for a manager to make a decision. Specific enough for an architect, developer or assurance team to challenge the design.
Evaluation guides
Start with your role, then follow the linked source evidence when a statement needs deeper verification.
Architecture and technical viability
The reference architecture, identity and data flows, integration boundary, deployment shape and questions a technical evaluator should resolve before committing.
Developers & architectsDeployment and readiness
The customer-owned prerequisites, delivery sequence, configuration boundary, assurance gates and handover artefacts for a controlled Orbit deployment.
Platform & delivery teamsSecurity and assurance boundary
What Orbit controls, what the Microsoft tenant controls, where client-side enforcement stops and which evidence should be collected for an assured deployment.
Security & complianceMicrosoft licensing and prerequisites
A practical guide to the Microsoft services and use rights that may be needed, with the baseline separated from optional workflow, app and reporting choices.
Managers & licensing adminsStandards alignment and governance
How Orbit can support service-management and information-security evidence, the limits of that alignment, and the deployment records management should expect.
Compliance & managementOperations and ownership
The customer, platform and product responsibilities needed to keep an Orbit deployment supported, controlled and useful after go-live.
Service owners & managersOrbit commercial model
A non-binding commercial overview for Orbit itself, clearly separated from Microsoft licensing and implementation services. The executed agreement alone defines customer rights.
Commercial & procurement