Athentra for partners
Govern fifty tenants without fifty consoles.
Athentra is built to be run by somebody who does not work for the client. Your engineers administer every client from your own tenant, you configure once and roll it out, and each client keeps its own data, its own residency and its own bill. And what it finds is not a report — it is a book of work with your name on it.
The part nobody quotes for
Multi-tenant governance usually means doing it all again, per client.
Most governance tooling is built for the organisation that owns the tenant. Run it for thirty clients and the cost is not thirty licences — it is thirty sets of configuration, thirty logins, thirty places a policy has to be updated, and a guest account for every engineer in every client directory.
That is the work that quietly eats a managed service. It does not show up in the pitch, it shows up in the second year, when a policy changes and somebody has to apply it thirty times.
And the tools that do solve it tend to solve it by making your engagement smaller.
The other side of the ledger
A governance product that creates billable work rather than absorbing it.
Athentra is not a tool that quietly does your job and shrinks the engagement. It finds work, evidences it, ranks it and queues it — and most of that work is yours.
-
01
A paid governance assessment
Point Athentra at a prospect’s tenant for a week and walk them through what it found. It is the shortest route from a conversation to signed work — and the findings are the scope of everything that follows.
-
02
Implementation
Consent, connection, naming conventions, provisioning templates, review cadences, baselines. Every client needs it. You design it once and reuse it across your base.
-
03
Remediation
Every finding arrives with the evidence behind it and a severity against it. The backlog is generated, ranked and quantified for you, so you quote from a list the client can see rather than from an assertion.
-
04
Managed governance
The monthly line: reviews chased, findings triaged, drift watched, new Teams provisioned to standard, and somebody accountable for the score going up. This is the recurring revenue, and it is the part Athentra makes defensible.
-
05
Maturity assessment and roadmap
A structured assessment against the Essential Eight or the Microsoft 365 maturity model, re-run on a cadence so improvement is visible. A schedulable consulting engagement rather than a one-off.
-
06
Automation you own
Controls you write once and share across every client. Your scripts stop being tribal knowledge on an engineer’s laptop and become versioned, permission-checked, auditable work you can charge for.
-
07
The disposal integrator
Athentra never deletes or archives anything in a client’s tenant. It marks what is due, publishes the request and waits for a system outside it to act and report back. Building and running that system is work only a partner can do.
-
08
Copilot readiness
The reason clients are asking right now, and the programme that bundles the first four with a deadline attached. A cleanup that has to be finished before Copilot rolls out is an easier sale than governance in the abstract — and the assessment tells you exactly how much there is to do.
Why the renewal conversation gets easier
You stop asserting that things improved.
A managed service lives or dies on whether the client can see what they are paying for. Athentra scores each area, tracks it over time, and records every decision with who made it and when. At the quarterly review you are not claiming the tenant got better — you are showing the line, and the evidence underneath it.
The operating model underneath it
Built for the company in the middle.
-
Your staff, your tenant
An engineer in your tenant holds a role that reaches the clients beneath you. No guest accounts in client directories, no second identity to manage, nothing to clean up when somebody leaves — you revoke it once, with everything else.
-
Configure once, roll it out
Build a provisioning template, a maturity model, an access review definition or a configuration baseline once, and share it to the clients that should have it. Athentra checks for conflicts before it lands, and re-syncs when you change the original.
-
Buy for a client without becoming them
Subscribe on a client’s behalf by naming them. No switching in, no borrowed credentials. Clients cannot subscribe themselves unless you allow it, so purchasing stays where the commercial relationship is.
-
Clients stay separate, and stay theirs
Each client keeps its own residency, its own data and its own administrators. One client cannot see another, and a client you do not manage is invisible to you — Athentra behaves as though it does not exist, rather than telling you it is off-limits.
A worked example
Onboarding a client, and the month that follows.
One new client. The same shape holds for the thirtieth.
-
Day 0
They join, and they own their own tenancy.
You invite the client’s organisation. Their administrator accepts in their own tenant and becomes its administrator — you did not create an account for them, and they did not hand you a credential.
- invite
- organisation
- accepted by
- client administrator
- residency
- set by the client
-
Day 1
Your standards arrive with you.
You push the provisioning templates, review definitions and baselines you use for every client of this size. Conflicts are reported before anything lands, so an existing template is never quietly overwritten.
- shared
- 4 templates, 2 definitions
- conflicts
- checked first
- source
- your tenant
-
Month 3
You change it once.
The naming convention changes. You edit the original and re-sync — and every client that took it moves with you. A client that has diverged is reported rather than flattened.
- edited
- once
- re-synced
- every client that took it
- record
- who shared, when
The client’s people answer their own reviews and approvals — that is the point of the product. What you carry is the configuration, not the decisions.
Being straight with you
What we are building next.
Athentra gives you one hierarchy, one set of credentials and one place to configure. What it does not yet give you is a single operational dashboard across every client at once — today you move between clients to work in them. That view is what we are building, and it is the thing to ask us about if it decides your answer.
The commercial side
Terms are a conversation, not a table.
Athentra is priced per licensed user per month, per module, and every figure is published — so you can model a client before you call us. What that becomes for a partner, and how the contract and billing sit, depends on how you want to sell it. That is worth twenty minutes rather than a form.
Bring us a client you already worry about.
The most useful first conversation is not a demo. Pick a tenant you inherited and do not fully trust, and we will run a free Health Check against it — you keep the report whatever happens next.