
Argent with Microsoft Azure
Run Argent in your own Azure subscription, send Azure OpenAI and Foundry calls through it, and let Argent read your subscription to show whether Azure itself refuses AI calls that go around the gateway.
Argent across Microsoft Azure
Argent Strategic Intelligence is the gateway between your AI agents and the AI models they use. It meets Microsoft Azure in five places.
| Where | What Argent does |
|---|---|
| Runs in your subscription | One Helm chart on Azure AKS. The gateway's edge handles TLS itself, and the secrets store unlocks from Azure Key Vault through the cluster's workload identity. |
| Governs Azure OpenAI and Foundry | Agents send their calls to the gateway, which checks, records and forwards each one. See Azure OpenAI. |
| Agents with no keys | A workload can send a token from its managed identity. Argent checks the token and maps it to an agent with a human owner. People sign in with Microsoft Entra. |
| Evidence on Azure storage | The signed evidence archive can live in an Azure Blob container with version-level immutability, signed in with the pod's workload identity, so no storage key is kept anywhere. |
| Checks the cloud | A read-only coverage scan reads your subscription and reports, per Azure OpenAI or Foundry account, whether Azure itself blocks calls that skip Argent. The rest of this page is about that scan. |
Why the cloud matters. A gateway governs what goes through it. Azure can make it the only way. Microsoft notes that organizations "can disable local authentication methods and enforce Microsoft Entra authentication instead" (Microsoft Learn). Add a private endpoint in the network that holds the gateway and turn public network access off, and a workload that tries to go around the gateway gets a 403 from Azure itself. We proved this live on 2026-11-05.
What the scan checks in Azure
Every check is read-only. Each one ends in pass, fail or unknown, and the evidence says why.
| Check | Pass means |
|---|---|
| Public network access is off | The account's public network access is disabled. |
| A private endpoint is approved | At least one private endpoint connection to the account is approved. |
| Key sign-in is off | Local (key) authentication is disabled. Azure leaves the setting out while key sign-in is on, so a missing setting is a fail. |
| Only approved models can be deployed | An enforced Azure Policy assignment with a Deny effect, testing the deployment's model name, covers the account. The allowed models are listed in the evidence. |
| The built-in deny policies are assigned | Azure's built-in network-access and key-access policies are both assigned over the account with a Deny effect, and enforced. |
| Diagnostics are on | A diagnostic setting sends audit and request-response logs to a Log Analytics workspace or a storage account. Recorded for your auditors; it does not change the verdict. |
| API Management sits in front | An API Management backend points at the account. Recorded alongside; it does not change the verdict. |
A policy set reports unknown, not pass. Policy sets (initiatives) are not unpacked, so a set that might hold the lever makes the policy checks unknown. Microsoft also notes that turning key sign-in off can take "up to several hours" to reach the gateway that enforces it (Microsoft Learn), so scan again after a change.
How a scan runs, and what you see
Argent reads the account, judges it, and signs the result.
- Argent signs in read-only. It fetches the scan credential from the Credential Broker by its reference.
- Argent runs every check. On its schedule, every 24 hours by default, or when an admin presses Scan now.
- Argent gives a verdict. Bypass blocked when every check that closes a path passes. Bypass possible when one fails. Unknown when none fails but one could not be read. Logging and front-door checks are shown, but they do not change the verdict.
- Argent signs the result. Each scan writes a signed record, and every check whose result changed since the last scan writes another.
- Argent raises an alert on a drop. When an account falls from blocked to possible, an alert opens with the failing checks, and an admin acknowledges it. A return to blocked is signed too.
A check that cannot read is unknown, never pass. When Azure refuses a read, the check reports unknown with the HTTP status in its evidence, so a missing permission never looks like a green light.
What you enter in the Argent console
An admin adds the account under Integrations > Discovery > Cloud coverage, with Add account. The form asks for:
| Field | What it is |
|---|---|
| Cloud | Azure. |
| Name | Optional. Shown instead of the subscription id. |
| Subscription id | The subscription to scan. |
| Directory (tenant) id | Your Microsoft Entra tenant. |
| Application (client) id | The app registration the scanner signs in as. |
| Resource groups | Optional. Separated by commas; empty scans the subscription. |
| Credential reference | Where the app's client secret is kept in the Credential Broker, never the secret itself. |
| Scan every (hours) / Scan on schedule | How often the scan runs on its own. The default is every 24 hours. |
- See every account at a glance. The page counts accounts by verdict, shows each account's last scan, lists open alerts and explains what each check reads and what a pass proves.
- Who can do what. SuperAdmins and tenant admins add accounts and run scans. Auditors can read every result.
- One switch, with a lock. Scanning has one switch per tenant: on, off or locked. Off skips the schedule and refuses Scan now, and deletes nothing. A higher level can lock the switch, and only that level can change or unlock it. Every change is signed, and so is every refused one.
What you set up on the Azure side
One read-only identity, once. Nothing on this list lets Argent change your cloud.
- An app registration for the scanner in Microsoft Entra, with a client secret.
- The Reader role on the subscription, or only on the resource groups you list. Reader is enough: the scan only reads.
- Its client secret, saved as one reference in the Credential Broker. Give Argent the reference and delete the local copy.
- The levers themselves are yours. Your Azure admins set up the private endpoint, turn off public access and key sign-in, and assign the policies. See Microsoft's guide to disabling local authentication.
Where it fits, and how you start
The scan is how a security team proves the gateway is the only way to the models, not just the easiest one.
- Capabilities: shadow AI discovery, model control, keyless agents, watch before you enforce and one-click audit evidence. All capabilities.
- Goals: see all AI in your company, model control and routing, threat defense, compliance evidence and sovereign AI. All goals.
- Use cases: AI coding agents, customer-facing assistants, enterprise copilots, agent tool access and regulated and air-gapped AI.
- Related integrations: Azure OpenAI, Microsoft Entra, Kubernetes and Helm, and the scans for Amazon Web Services and Google Cloud.
- Where Argent runs: air-gapped on premises, private cloud or your public cloud VPC. Compare the options.
- Industries: financial services, insurance, healthcare, the public sector and retail. All industries.
- Install. Put the Helm chart in your AKS cluster with the Azure profile, and point Azure OpenAI callers at the gateway.
- Watch. In Watch mode, Argent records what it would have stopped and changes nothing.
- Scan. Add the account under Integrations > Discovery > Cloud coverage and press Scan now. Each failing check is named, with its evidence.
- Enforce and prove. Switch on Enforce, have your admins pull the levers, and scan again until the account reads Bypass blocked. The signed records show when it got there.
Want this running on your own use cases?
Book a demo