Signals split across tools
Regressions customers find first
Exceptions, dependency timeouts and failed deployments are scattered across tools. By the time they connect, a customer has already noticed.
Spend that drifts
A new service or a sustained increase in compute can add cost every day before finance flags it.
Service principals with production keys
Pipelines and automation run as service principals that often hold far more access than they need. A leaked credential inherits all of it.
AI features without guardrails
Azure OpenAI deployments go live with public access, API keys and no content filters because shipping comes first.
Detect resource drift
TENET learns what normal looks like for each connected resource and flags the ones moving away from it, with no thresholds to set.
- Baselines learned per resource
- Health events listed next to the drift
- No thresholds to set per resource
vm-api-prod
Memory utilisation above baseline
aks-cluster-eu
CPU utilisation above baseline
sql-db-prod
Resource Health event reported
storage-westeu
Within baseline
checkout-api
Exceptions rising · dependency timeouts
billing-service
Failed deployment detected
notification-worker
Slower than usual
web-frontend
Healthy
See application health
Instead of piecing together separate dashboards, you open one row per application and see what is wrong, why it is likely failing and which dependencies it leans on.
- Health status for each application
- Plain-language summary of the failure
- Dependencies mapped from Application Insights data
Flag new cost sources
Cost rises are rarely announced. TENET reads Azure Cost Management data you already have access to and highlights sustained increases and services that were not in the bill before.
- Sustained increases highlighted
- First-time services called out
- Nothing extra to connect
Compute in the production subscription
Sustained increase
New service in the test subscription
New source of spend
Storage
In line with recent spend
svc-deploy-pipeline
Owner role on production subscription
Path to customer database
Exposed VM · broad identity · database
SSH open to a wide range
nsg-build-agents
mi-reporting
Scoped access
Lock down production access
Pipelines and automation run as service principals and managed identities. TENET shows how far each one reaches, which ports are open to the internet and the attack paths they create to customer data.
- Reach of every service principal
- Internet-facing ports per network security group
- Attack paths to customer data
Ship AI features safely
Every Azure OpenAI, AI Search and Cognitive Services deployment shows its error rate, throttling and quota use, and posture findings flag public access, key-based authentication and missing content filters.
- Runtime health per deployment
- Posture gaps by severity
- AI agent identities scored for risk
openai-prod
Public network access · API keys enabled
gpt-chat
Throttled calls rising
search-docs
Content filter missing
openai-internal
Healthy
Customer exports folder
Anonymous link
Support escalations site
Guest links
dev-laptop-12
Out of compliance
Finance site
Internal only
Protect customer data in Microsoft 365
Customer contracts, data exports and support files live in SharePoint and OneDrive. TENET shows what is shared outside the company and which devices fall out of compliance, and maps your controls to NIST CSF 2.0 for customer security reviews.
- External sharing per site
- Device compliance and endpoint findings
- NIST CSF 2.0 readiness
FAQs
We run on Azure but may add AWS or GCP. Is TENET the right fit?
Does connecting TENET change our Azure resources?
No. Setup creates an Entra application and service principal with read-only access. TENET does not deploy agents or modify resources, so your resources and the workloads on them stay as they are.
See the Microsoft cloud integration guide for the exact roles and setup steps.
Do we have to set alert thresholds in TENET?
No. TENET builds baselines for connected resources automatically, so there are no alert rules or thresholds to tune. Workload anomalies, application events, cost anomalies and identity risk appear in one view.
Read more about anomaly detection.
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.