Requests and incidents
Guided intake, ownership, priority, comments, status and history.
Microsoft 365-native service management
Service management that stays in your Microsoft tenant.
Orbit brings requests, incidents, approvals, assets, lifecycle work and knowledge into one calm, configurable portal—without asking your organisation to adopt another system of record.
Read the technical documentationDesigned and maintained by RME Solutions TechnologyMicrosoft Partner
IdentityMicrosoft Entra ID
Tenant dataSharePoint Online
Optional workflowsPower Automate
White-label by designSource access by agreementTenant-specific deploymentCloudflare edge deployment availableDocumented deployment boundary
A useful front door for IT
One experience. The service records you already own.
Orbit is a focused service-management layer for Microsoft 365. It gives employees an approachable place to ask for help and gives the service team structured, auditable work behind the scenes.
Search services, knowledge and requests⌘ K
01Get helpReport an issue or ask a question
02Request a serviceStart with the right form and approvals
03Track my workClear status, comments and history
Access requestAwaiting manager approval
In reviewCatalogue and approvals
Configurable services and forms with documented approval states.
Assets and lifecycle work
Link service work to assets, onboarding, offboarding and fulfilment.
Knowledge and operations
Reusable guidance, service oversight and evidence-ready records.
Illustrative product view. Features and presentation are configured per deployment.
See the live experienceA legible technical boundary
Built around Microsoft 365—not beside it.
The standard Orbit deployment is a static React application. People sign in with Microsoft Entra ID; the browser works with Microsoft Graph and SharePoint Online under the signed-in user’s delegated access.
- SharePoint Lists remain the primary service-data store.
- Tenant identity, branding and catalogue are deployment configuration.
- Power Automate is used only where selected workflows require it.
- Strict writes can add an authenticated server-side control where required.
People
EmployeesBrowser + Microsoft identity
Service teamRole-aware operating views
ExperienceOrbit ITSMStatic web applicationNo customer data stored in the static hostCloudflare edge-ready
Orbit ITSMStatic web applicationYour tenant
Entra ID + GraphIdentity and delegated access
SharePoint OnlineLists, permissions and records
Power AutomateOptional tenant workflows
Governance without theatre
Useful evidence. Honest boundaries.
Orbit can support controlled service management and information-security evidence. It does not claim to certify a deployment—or replace the controls, ownership and assurance your organisation must operate.
ITIL-aligned operating patterns
Structured intake, ownership, approvals, knowledge, change and service records support disciplined ways of working.
ISO/IEC evidence hooks
Documentation maps product capabilities to relevant ISO/IEC 20000-1, 27001 and 27002 practices without making conformity claims.
Traceable source documentation
Public guides are backed by an allowlisted source register that synchronizes metadata and hashes while excluding internal document bodies.
ArchitectureSecurity boundaryAssurance checklistStandards applicabilityOperational ownership
Suitability at a glance
A strong fit when Microsoft 365 is already home.
A good product decision includes the awkward questions. These are the starting conditions we would examine before recommending a deployment.
Orbit is worth a close look if you…
- run your organisation on Microsoft 365 and SharePoint Online;
- want a branded service portal without a separate SaaS data silo;
- value source access and tenant-specific configuration; and
- can assign service, platform and security ownership.
Plan the control model carefully if you need…
- strict server-side authorization for sensitive write paths;
- premium/custom connectors or high-volume automation;
- guest, cross-tenant or complex Conditional Access scenarios; or
- formal retention, DLP, backup or data-residency controls.
The standard model is not designed as…
- a multi-customer shared SaaS platform;
- a replacement for SharePoint Online;
- a certification or compliance guarantee; or
- a zero-ownership turnkey managed service.
Licensing, plainly stated
Two licensing conversations—not one surprise.
Orbit has its own commercial licence. Your organisation also supplies the Microsoft entitlements required by the solution design.
Review the licensing guideLayerWhat to allow forWhen
OrbitCommercial licensing by quotation; the executed agreement defines scope, source access, term and tenant coverage.Required
Microsoft 365User licensing that includes SharePoint Online, plus Entra app registration and approved permissions.Required
Power AutomateAppropriate use rights for selected flows, ownership context and connector types.By design
Power Apps, Dataverse, Power BIOnly where optional apps, premium data services or reporting are adopted.Optional
Microsoft licensing, connector classification and tenant policy can change. The intended design and user population must be checked with your Microsoft licensing administrator before production deployment.
For the people who need to know
The product story is short. The evidence is not.
Explore the architecture, deployment path, security boundary, standards position, Microsoft prerequisites and public source-document register.