Gaps between client reviews
Client tenants nobody watches
Between quarterly reviews, a client tenant can collect new admin roles, shared links and open ports. The first sign is often an incident.
Findings that never become tickets
A finding that lives in one more console waits for someone to notice it. Risk that is not in the service desk is risk nobody owns.
Evidence built by hand
Compliance and posture reports assembled per client eat the hours that should go to fixing the gaps they describe.
Rank clients by risk
Partner Hub lists every client tenant you manage with its risk posture score and connection status, and calls out the clients scoring below 50. Open any client to see its summary, generate its reports or ask Brite about it.
- Risk posture score for every client
- Clients below 50 counted at the top
- Reports and Brite one click from each client
Client A
Risk posture 38 · open attack path
Client B
Risk posture 54 · NIS2 control gaps
Client C
Risk posture 67 · new guest access
Client D
Risk posture 88 · no new findings
Client A · application health review
Repeated failures in a customer-facing app
Client B · capacity review
Production VMs running above baseline
Client C · cost review
New source of Azure spend
Client D · application monitoring
Won
Turn findings into opportunities
Partner Hub reads the AI summaries of each client’s anomalies and application health and proposes the product, service or scoped engagement they point to, with the evidence, why it matters and the smallest next step. Approve or dismiss each one, then track it to a decision.
- Opportunities backed by client evidence
- Approve or dismiss before it reaches sales
- Tracked from New to Won or Not now
Put incidents in context
TENET reads each client’s Microsoft Sentinel and Microsoft 365 Defender incidents and places them next to the identities, resources and attack paths already tracked for that tenant. Your analysts see what an alert can reach, not just that it fired.
- Sentinel and Defender incidents in one list
- Incidents linked to attack paths and root cause
- Any incident sent to Brite for investigation
Sentinel: suspicious sign-in burst
Account holds a privileged role
Defender: malware on device
Device out of compliance
Sentinel: mailbox rule created
Under investigation
Defender: blocked phishing link
Closed · no further reach
Toxic combination
Exposed VM owned by an admin · ticket opened
Overdue remediation task
SLA breached · ticket escalated
NIST CSF 2.0 control failing
Ticket opened in client project
Port closed by technician
Ticket closed · task completed
Route findings to your desk
TENET opens tickets in HaloPSA or Jira when anomalies, compliance findings, incidents or remediation tasks reach the severity you set, routed to the right client company or project. Remediation tickets close when the task is completed, and status changes your technicians make on them flow back into TENET.
- Severity threshold set once for every client
- Duplicate tickets skipped automatically
- Microsoft Teams alerts and a daily brief per tenant
Assess clients under your brand
Connect a new or prospective client’s tenant with read-only consent and TENET scans its Azure and Microsoft 365 estate. Set your logo, company name, accent colour and presenter once. Cloud security, NIS2, NIST CSF 2.0 and Copilot readiness reports then carry only your brand, in English, German, French, Spanish, Italian, Dutch or Polish.
- Your brand only, never mixed with ours
- Four report types for every client
- Seven report languages
NIS2 gap report
Client B · German
Cloud security report
Client A · English
Copilot readiness report
Client C · French
NIST CSF 2.0 report
Client D · Dutch
Article 21(2)(j) · multifactor authentication
Failing · 2 engineer accounts
RMM tool supplier
Supplier review overdue
Incident response policy
Review due next month
Access control policy
Active
Cover your own NIS2 duties
NIS2 names managed service providers and managed security service providers in Annex I, so your own controls are in scope too. Connect your own tenant and use the same compliance hub you run for clients: NIS2 and NIST CSF 2.0 readiness, policies, a risk register and supplier reviews.
- Readiness for your own tenant
- Policies and risk register with review dates
- Supplier reviews and questionnaires
FAQs
Does TENET deploy agents into client tenants?
No. Each client tenant connects with read-only permissions through an Entra application and service principal. TENET does not deploy agents or modify client workloads.
See the Microsoft cloud integration guide for the exact roles and setup steps.
Does TENET work with Microsoft Sentinel?
Which ticketing tools does TENET integrate with?
Can client reports carry our brand?
Yes. Add your logo, company name, accent colour and presenter details in Partner Hub. Reports then show only your brand.
Read the partner program FAQ for how white-labelling works.
How do we resell TENET to our clients?
Find your Microsoft cloud risk
Connect your Azure and Microsoft 365 tenant with read-only access and see which identities, exposures and anomalies matter most.