FIDEVO FINANCEVATIS-9 · M365 governance & MCP for AI
Your M365 tenant is growing faster than anyone can govern it.
VATIS-9 provisions, identifies and governs every SharePoint site, library and document — automatically, from the moment it is created. And any MCP-compatible AI can call the same governed operations without ever touching tenant credentials.
THE PROBLEM
Every M365 tenant accumulates the same three problems.
Sites created by anyone, named by no one, owned by nobody. Six months later, IT cannot tell which ones are still active.
Documents move. Libraries grow. Nobody knows what changed, who approved it, or whether it is still required.
A compliance request arrives. The team spends three days reconstructing what should have been recorded automatically.
THE ANSWER
One engine. Three motions. Zero manual governance.
A user describes what they need in plain language. VATIS-9 creates the site, sets permissions, stamps a UDIS identifier — under a minute.
Every artefact receives a UDIS identifier bound to the ADO Feature that authorised it. Nothing is anonymous.
Retention, classification and approval workflows execute in the background. No checklist to remember.
HOW IT WORKS
From a sentence to a governed site — in under a minute.
The admin types what they want.
VATIS-9 interprets the natural-language request, matches an approved template and reserves a deterministic UDIS bound to its owning ADO Feature.
$ Provision ACE finance workspace for COR wave 3 » GENERATING UDIS... MWP-SITE-00042-F3391
SharePoint builds itself.
Site, libraries, permissions and retention are applied through Microsoft Graph in seconds — with a service identity. The AI never touches tenant credentials.
POST https://graph.microsoft.com/v1.0/sites
{
"displayName": "Hornsea 4 — EIA",
"template": "MWP-TEAM-V3"
}Policies run in the background.
Every document flows through Policy Hub — draft, review, approval, retention — with a complete audit trail ready for e-discovery.
applyPolicy({
naming: "mwp-baseline",
classification:"internal",
retention: "7y-project"
})UDIS · ANATOMY
Identifiers your auditors can read out loud.
Every UDIS is four segments: what programme it serves, what kind of artefact it is, its position in that sequence, and the ADO work item that authorised its birth.
MCP FOR AI
One MCP server. Every AI that matters.
VATIS-9 speaks the Model Context Protocol end-to-end. Any compliant client — Claude, ChatGPT, Gemini, Cursor, Copilot — can discover the same governed operations, propose artefacts and mint identifiers. Your tenant credentials stay in the service identity.
Native MCP client. Add VATIS-9 in Claude Desktop settings.
Connect VATIS-9 as a custom connector in ChatGPT.
Reach VATIS-9 tools over the MCP HTTP transport.
Drop the VATIS-9 server into ~/.cursor/mcp.json.
Expose UDIS lookups inside VS Code agent mode.
Streamable HTTP · JSON-RPC 2.0 · OAuth 2.1.
- › vatis.propose_artefact — Match a plain-language brief to an approved artefact template.
- › vatis.issue_udis — Reserve a UDIS bound to an ADO work item.
- › vatis.resolve_udis — Return provenance, policy and location for an existing UDIS.
- › vatis.apply_policy — Apply naming, classification and retention at creation time.
- › vatis.audit_query — Query the audit trail for any actor, artefact or window.
BOOK A DEMO
30 minutes with an M365 specialist.
We will show you VATIS-9 on a real tenant and answer your questions about Graph permissions, data residency and retention.