GovernorAIby SentinelLayer Request a briefing
Find and qualify
Discovery & Shadow AIInventory the AI activity nobody registered AssuranceEvaluate an agent snapshot before production
Decide and enforce
Policy & GovernanceKeep the policy engine you already run Runtime EnforcementDecide at the action boundary Inference & Model GovernanceGovern the model call itself Multi-cloudOne policy, each cloud's own controls
Prove and observe
Evidence & ComplianceTamper-evident record, mapped to controls Decision ObservabilitySee the decision behind the action
Risk and security
RiskScore the action, and act on the score ContainmentStop a runaway run before it lands Security architectureHow the control plane itself is built
By persona
SecurityPer-call authorization and stop controls GRCEvidence chains and control mapping Platform & AI EngineeringGovern without touching the agent
By risk
Shadow AIUnmanaged agents and connections Data leakageIn prompts, completions and tool calls Destructive actionsChanges to systems of record
By platform
AWS BedrockInbound path, guardrail attachment ServiceNowNow Assist discovery and scoped control SalesforceAgentforce and Einstein Bots, in-org MCPRegistry, proxy, argument-aware inspection
By cloud and runtime
AzureConnect, discover, govern at the gateway Google CloudValidated connect mode, bootstrap session DatabricksCluster-side egress, pinned at create Kubernetes & sidecarIn your cluster, on the agent host

USE CASES / AZURE

Connect without handing over a standing key.

Azure connection uses a short-lived bootstrap session rather than a long-lived credential. The session is orchestrated, persisted while it is needed, and swept when it is not — so the onboarding path does not leave a permanent key behind.

Short-lived bootstrap credentials Azure AI account discovery Explicit deprovision path
CONNECT WITHOUT HANDING OVER A STANDING KEY Bootstrap session opened short-lived, not a standing key 01 Read-only discovery AI and Cognitive Services accounts in scope 02 Mode recorded explicitly persisted, and validated against the credential 03 Session swept a sweeper reclaims it, so nothing accumulates 04 Deprovision a first-class path, not the absence of a record 05 Connection and discovery are not enforcement. No Azure-native inbound point equivalent to Bedrock is claimed.

A short-lived bootstrap session rather than a long-lived credential, so onboarding does not leave a permanent key behind — and a sweeper reclaims the session so the temporary path does not accumulate.

no standing keyread-only discoveryconnection is not enforcement

CONNECTION MODEL

How the subscription is attached.

01
A bootstrap session is openedA temporary connection session is created and persisted, orchestrated through a deployment against your subscription rather than a credential paste.
02
Discovery runs read-onlyAzure AI and Cognitive Services accounts in scope are enumerated through the Azure SDK, so the inventory comes from the platform's own API rather than from a survey.
03
The mode is recorded explicitlyThe connection mode is persisted alongside the credential shape, and a mismatch between the two is rejected rather than stored — so the console cannot label a connection production-safe when it is not.
04
The session is sweptA sweeper reclaims bootstrap sessions, so the temporary credential path does not accumulate.
05
Deprovision is a first-class pathDisconnecting is an explicit operation with its own handling, not the absence of a connection record.

ENFORCEMENT

Where the decision goes on Azure.

Enforcement point
Applies to
Azure APIM forward-auth
Agent traffic already crossing Azure API Management. Allow returns 200, deny returns 403. This pattern cannot rewrite a body.
LLM gateway
If a gateway such as Portkey or LiteLLM fronts the model call, GovernorAI registers as a guardrail on it and governs the call itself.
SDK
Where the workload is yours to instrument and no gateway sits in front of it.

Connection and discovery are not enforcement. Attaching a subscription tells you what is running; an enforcement point has to be chosen before anything is governed.

Honesty note

This page describes connection, discovery and the enforcement points available on Azure. Each enforcement point above is shipped code whose attachment is a configuration step you own. The APIM path is a standalone check service that ships as a binary with its own Kubernetes manifests; an API Management policy that you author calls it, and GovernorAI does not write that policy for you. The same division holds for the LLM gateway and the SDK — the adapter ships, and attaching it is not something connecting a subscription performs.

Azure's native attachment point is the Azure OpenAI RAI policy, not AI Foundry. A GovernorAI policy compiles to an Azure OpenAI RAI policy document — content filters and blocklists — which can be created or updated through the ARM management plane. That path is off unless you turn it on: the control plane installs a no-op Azure client unless AZURE_RAI_ENABLED is set to true and the target account is named through the AZURE_RAI_* environment variables, and it carries its own dry-run switch. Azure AI Foundry itself offers nothing equivalent to a Bedrock guardrail. A Foundry agent is governed on the request side through the gateway, which can allow, deny, or narrow the arguments of a tool call and re-checks the narrowed arguments against what is actually posted to Azure — a narrowing it cannot honour becomes a deny rather than an unconstrained request. It does not shape responses on that path.

The multi-cloud compiler also emits an Azure artifact, and that is where it stops. The shipped control plane wires a no-op cloud client for all six compile targets, so the artifact is something you can read and declare — not something the product applies to your subscription or checks back against afterwards.

Continue

IntegrationsEvery enforcement point in one table DiscoveryWhat the connection surfaces GCPThe same model, different cloud