Make cloud value visible
Review Azure cost, M365 licences, Entra governance, DevOps findings and Microsoft posture with owners and source evidence.
The finance perspective ↗ORCA / MICROSOFT CLOUD OPERATIONS
Your cloud.
In its element.
A clearer view of your Microsoft cloud. An accountable path from evidence to action.
Orca brings cloud optimisation, security operations, service management and desired-state governance into one scoped workspace. Powered by our own locally deployed Orca AI, or configured to run with Azure AI.
Explore the launch offering. Confirm accepted release scope in your proposal.
01 / A connected operating modelBuilt around your people
25 product enginesAzure + M365 governed scopeReport / Revert desired-state policyHuman approval consequential actions
THE PLATFORM
Different responsibilities.
A shared operating picture.
Spend, risk and service decisions depend on the same context. Orca connects the work while keeping each team’s authority clear.
Keep operations connected
Bring supported Microsoft incidents, asset context, evidence and service work into linked workflows with accountable handovers.
The operations perspective ↗Govern what happens next
Use scoped permissions, independent approval and verified execution. Monitor supported configuration against an approved desired state.
The drift workflow ↗YOUR PERSPECTIVE
What does Orca
change for you?
Choose a role to explore a working day, the capabilities behind it and the evidence that makes progress visible.
DESIRED STATE & CONFIGURATION DRIFT
Know what changed.
Decide what should stay.
Version the approved configuration for supported Azure and M365 properties. Detect differences, register the work and govern the next step.
Your baseline. Your policy.
Report records the difference in a ticket and notifies the owner. Revert registers the ticket before a supported, authorised restore and independently checks the result.
Intentional changes can become the next baseline through a scoped change window, fresh capture and independent approval.
- Default scan cadence
- Every 15 minutes
- Coverage
- Explicit per resource and property
- Failed or partial reads
- Unknown, never silently compliant
Polling cadence does not guarantee detection or restoration within 15 minutes. Provider scope, permission and reversibility must be validated.
INTERACTIVE EXAMPLE
Azure storage / public network access
Illustrative values only. No live systems or actions.
Approved baselineDisabledVersion 1
Observed configurationEnabledFresh sample observation
Ready to compare the observed value with baseline version 1.
“Simulate approved change” demonstrates a scoped pause, fresh candidate, separate approval and activation. It does not grant approval in Orca.
A KEY ORCA CAPABILITY
Your AI.
Your deployment choice.
Our own locally deployed AI
Run Orca AI through your approved private deployment. Bring AI assistance to authorised knowledge and operational workflows with control over the inference environment.
Configured for Azure AI
Configure Orca to run with Azure AI using approved endpoints, identities and model policy that fit your cloud operating model.
The same authority boundaries
Both routes preserve tenant scope, authorised retrieval and user, group and tenant budgets. AI assists people without approving consequential actions.
Local AI describes the inference deployment. Microsoft cloud integrations still require their approved API connectivity.
TRUST IN THE WORKFLOW
Authority stays explicit.
People see their permitted work
Tenant membership, role ceilings and the permission matrix govern access. Inaccessible menus disappear and server-side checks enforce the boundary.
Customer records retain their ownership
Committed business records belong with the customer, with offboarding export. Private operator notes and trusted execution authority stay separate.
AI assists within policy
Our own locally deployed Orca AI or configurable Azure AI, authorised retrieval and user, group and tenant budgets govern AI use. AI output does not approve consequential actions.
Accepted is followed by verified
A provider receipt starts the verification journey. Unknown outcomes remain visible until reconciled and fresh evidence supports the result.
THE ENGINE ROOM
Twenty-five engines.
One deliberate design.
Select any module to explore its purpose, key features and a practical example. The v8 launch scope includes M24 desired-state monitoring and M25 incident and request templates. Optional engines have tenant-specific settings; Platform and UAM remain foundational.
Capabilities depend on accepted release scope, provider consent and tested adapters. Engine numbers identify responsibility and do not imply separate deployments.
GO DEEPER
The detail behind the story.
MASTER SPECIFICATION / V8 / WORD
The complete Orca reference
All 25 engines, tenant controls, permissions, workflows and acceptance criteria. Includes desired state and guided incident and request templates.
Download v8 specification ↗INTERACTIVE MODULE CATALOGUEUnderstand every engine
Select a module for its features, practical example, integrations and controls. Browse all 25 in either theme.
Explore the modules ↗YOUR NEXT STEP
A better conversation
starts with your cloud.
Download your Orca discovery questionnaire in Excel. Your organisation, selected priorities and pilot outcome will be included. Complete the answer fields, save the workbook and email it to presales-orca@tib.org.uk.
Your information is kept private. Protecting your data and keeping it secure is our top priority.