Risks that build up quietly
Drift nobody set an alert for
Alert rules only catch what someone thought to configure. A resource slowly moving away from normal goes unnoticed until it fails.
Spend that creeps up
A sustained increase or a new service in the bill adds cost every day until finance asks about it.
Exposure from quick fixes
A port opened to test something and a broad role given to a pipeline stay in place long after the task is done.
Find drift before it breaks
TENET learns the normal behaviour of each Azure resource and flags the ones moving away from it, with no rules to write. Application errors, slow requests and dependency failures come from Application Insights, and Microsoft health events sit alongside.
- Baselines learned per resource
- Application failures grouped by app
- Health events next to the drift they explain
aks-prod-weu
CPU far above baseline
orders-api
Dependency timeouts rising
func-ingest
Slower than usual
sql-prod
Within baseline
Compute · production subscription
Sustained increase
New AI Search service
New source of spend
Storage
In line with recent spend
Control cloud spend
TENET reads settled Azure cost data and flags sustained increases that are unusual for that day of the week, plus new sources of spend once they have persisted. An AI summary frames the likely cause and the next check.
- Spend by service or subscription
- Sustained increases and new spend sources
- Newest three unsettled days left out
Close exposed paths
TENET lists network security group rules that open ports to the internet and maps how an exposed resource, an identity with broad permissions and sensitive data connect into an attack path. You close the link that breaks the most paths first.
- Internet-facing ports per network security group
- Attack paths from entry point to target
- Service principals and managed identities with broad reach
RDP 3389 open to 0.0.0.0/0
nsg-legacy-vm
Pipeline identity with Owner role
Reaches every subscription
SSH 22 open to a wide range
nsg-build-agents
HTTPS 443 open
Public web app · expected
openai-support-bot
Public network access · API keys enabled
gpt-deployment-prod
Throttled calls rising · quota at 90%
search-docs
Content filter missing
openai-internal
Healthy
Run Azure AI safely
See every Azure OpenAI, AI Search and Cognitive Services deployment with its error rate, throttling, latency and quota use. Posture findings flag public network access, API key authentication, open network rules and missing content filters.
- Runtime health for each deployment
- Security posture gaps by severity
- AI agent identities scored for risk
FAQs
Why does the cost view skip the last three days?
Which Azure AI services does TENET monitor?
Azure OpenAI, Azure AI Search and Cognitive Services deployments, with runtime health and security posture for each. AI agent identities in Microsoft 365 are covered too.
Read more about AI security posture.
Can our scripts and AI agents read TENET findings?
Yes. The TENET MCP server gives any MCP-compatible agent read access to anomalies, compliance, risk graphs and activity logs, and lets it create remediation tasks. See the TENET MCP server.
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.
14-day free trial · 2 min setup · No credit card required