An identity for every agent
Contents
About Microsoft
Microsoft, founded in 1975 by Bill Gates and Paul Allen, headquartered in Redmond, Washington, and led by chairman and chief executive Satya Nadella since 2014: is one of the world's most valuable companies (NASDAQ: MSFT). The Microsoft Cloud spans Azure, Microsoft 365, Dynamics 365, Microsoft Security, Microsoft Fabric and GitHub. Volge delivers across that estate through six alliance offerings.
What Volge delivers on Microsoft: six offerings
The offering this book covers: marked ◆: is Zero Trust Security, delivered on Microsoft Entra.
| Volge offering | What it covers | Anchored on |
|---|---|---|
| Modern Workspace & E7 | Secure modern work on the E7 bundle; human-agent collaboration | Microsoft 365 · Copilot |
| Applied AI | Building, governing and running enterprise AI agents and apps | Azure AI Foundry |
| Zero Trust Security ◆ | Identity, threat protection and data governance | Microsoft Entra · Defender · Purview |
| Business Applications | ERP, CRM and low-code, with in-process agents | Dynamics 365 · Power Platform |
| Digital Product Engineering | Autonomous software engineering and CI/CD | GitHub · GitHub Copilot |
| Cloud Infrastructure & Operations | Cloud build, run and cost governance (FinOps) | Microsoft Azure |
Sources: Microsoft corporate and product documentation, 2025–26.
This book: Zero Trust Security on Microsoft Entra
Microsoft Entra is Microsoft's unified identity and network-access family, built around Entra ID (formerly Azure Active Directory). It delivers Zero Trust access across human, workload and, as of 2026, AI-agent identities.
In the field in 2026
- Entra ID for workforce and external identities, SSO, passwordless/MFA and risk-based Conditional Access
- Entra Agent ID (GA April 2026), first-class identities for AI agents, consolidated into Microsoft Agent 365 (GA 1 May 2026)
- Entra ID Governance, entitlement management, access reviews and lifecycle workflows, extended to agents
- Entra Suite for Zero Trust network access: Private Access (ZTNA) and Internet Access (SSE)
Executive summary
A second workforce now reaches into corporate data, and almost none of it appears on a payroll, in a joiner-mover-leaver process, or in an identity team's inventory. Every autonomous agent shipped during 2025 and 2026 holds a credential, calls tools, queries data stores, and writes against live systems. Each is a non-human identity (NHI). Most are unscoped, unlogged, and impossible to revoke cleanly, because they were stood up without a first-class identity in the first place.
The title of this paper is an operational question, not a rhetorical one. In a large enterprise the population touching corporate data is already predominantly non-human, and the human security team can attribute almost none of it. Non-human identities outnumber human users by more than 80 to one across enterprises surveyed, and by as much as 100 to one in agent-heavy estates (CyberArk, 2026; industry estimates, 2026). Agent deployment is widening that ratio, not narrowing it.
The risk does not sit in the agents. It sits in the asymmetry between how fast they were deployed and how slowly the controls followed. Sixty-eight per cent of identity-related security incidents now involve machine identities, and 50 per cent of enterprises report a breach already traced to an unmanaged non-human identity (industry research, 2026). Eighty per cent of organisations report that their agents have already acted beyond their intended scope (industry survey data, 2026). The agent that causes the loss is rarely compromised and never malicious. It is over-permissioned, untracked, and trusted by default, which is the same failure mode as a standing service account, scaled and made autonomous.
The central claim of this paper is the following. An agent without a first-class, cryptographic identity cannot be inventoried, scoped, audited, or revoked. It is therefore not a productivity asset but an unmetered path into corporate data wearing the badge of one. Securing the agent estate is an identity programme before it is anything else. In the Microsoft estate, the identity is supplied by Microsoft Entra Agent ID and operated through Microsoft Agent 365.
The board-level case in the reference flagship of this series, From copilot to autopilot, settled that identity is the frontline of agent control. This paper is written for the people who now have to build that frontline: the identity administrator, the security engineer, and the chief information security officer's team. It is about the mechanics, the agent identity object, the registry, conditional access for agents, tool-level least privilege, the credential lifecycle, the audit trail, and the kill-switch, and how each is configured.
The argument runs in five moves, developed across the chapters that follow.
A single rogue agent is a chain of five identity omissions, and any one of them breaks the chain. The breach does not begin with a clever adversary. It begins with broad access granted because scoping is harder than granting, a credential that never expires, an agent absent from any inventory, actions logged in no reviewable form, and access that is never withdrawn when the task ends. Each omission is an identity control that was skipped. The agent-security problem is the sum of those skipped controls.
The fix is to make every agent countable, because what cannot be enumerated cannot be governed. An agent with a first-class identity can be placed in a registry, scoped to least privilege, evaluated by policy at each request, logged, and revoked. An agent without one can be none of these things. Microsoft Entra Agent ID reached general availability in April 2026 and assigns each agent a governed identity with specialised OAuth flows, lifecycle management, and a full audit trail (Microsoft, 2026).
Zero Trust reaches agents as four configured settings, not as a slogan. Conditional Access for agents evaluates every token an agent identity acquires, scopes policy by object identifier, custom security attribute, or blueprint, and blocks agents that Identity Protection rates high-risk (Microsoft Learn, 2026). Least privilege binds to the tool call, not to the agent. The credential is short-lived and purpose-bound, not a standing secret. These are knobs an identity team turns, and this paper specifies them.
The audit trail and the kill-switch are the floor, and most estates are below it. Every authentication, token acquisition, tool invocation, and policy decision has to be logged in a form that answers four questions: what was done, on whose behalf, under what policy, and why. Eighty-four per cent of organisations report that they could not currently pass a compliance audit focused on agent behaviour or access (Cloud Security Alliance, 2026). The ability to cut an agent's authority instantly and estate-wide is the operational twin of that audit trail, and it is worthless until it has been tested against a live agent.
The standards landed within eight weeks of each other and they agree. The OWASP Top 10 for Agentic Applications, published on 9 December 2025, and the Cloud Security Alliance Agentic Trust Framework, published on 2 February 2026, both put identity first and both codify the same posture: no agent trusted by default, autonomy earned through demonstrated behaviour, trust continuously verified (OWASP, 2025; Cloud Security Alliance, 2026). The Microsoft control set maps onto both, control for control.
The Microsoft ecosystem is this paper's primary lens because it is the default identity estate of the large enterprise, not because the problem is Microsoft-specific. Entra Agent ID brings third-party agents built on platforms such as Amazon Web Services Bedrock and n8n under the same identity, so the control plane is not confined to Microsoft-built agents (Microsoft Learn, 2026). Volge's position is plain: the identity decision is the precondition for every other agent-security control, and it is the decision most enterprises have made by default rather than by design. This paper sets out how to make it deliberately.
Chapter one: Anatomy of a rogue agent: how a single identity gap becomes a data breach
The takeaway
A rogue agent is not an exotic event. It is the predictable output of a five-step pipeline in which every step is an identity control that was skipped, and the rate at which it produces breaches is already rising with adoption. Trace the pipeline and the remedy is obvious: break it at any step and the breach does not occur. The first task of agent security is to make this pipeline visible in the estate, which is an identity task before it is a network or data task.
2.1 The pipeline, step by step
The mechanism by which agents produce rogue data exposure is well evidenced and structural rather than accidental. It runs the same way each time.
An agent is shipped quickly to capture value. To make it useful, it is handed broad access, because scoping access narrowly costs more engineering than granting it widely. The agent is registered in no central inventory, because no inventory for non-human identities exists. Its credential is a standing secret with no expiry. Its actions land in no log a security analyst would ever read. When the task that justified the agent ends, neither the credential nor the access is withdrawn.
The output is an over-permissioned, untracked, immortal identity with a clear path to corporate data. Eighty per cent of organisations report that their agents have already acted beyond their intended scope, which is the expected result when task scope, tool access, and credential lifetime are never aligned (industry survey data, 2026). Sixty-seven per cent of executives believe their organisation has already lost data or suffered a breach through unapproved AI tools (industry survey data, 2026).
Read the pipeline as a list of controls and the diagnosis writes itself. The agent was not registered, not scoped, not credential-managed, not logged, and not revoked. Each of those five is an identity control. The chapters that follow restore each in turn, and chapter three treats the four that an identity team configures directly.
2.2 Why this pipeline is worse for agents than for prior machine identities
Identity teams already manage non-human identities: service accounts get rotated, certificates get managed, keys get vaulted. Those techniques are necessary for agents and insufficient, and the reasons are specific. Four properties of agents widen each step of the pipeline above.
An agent is non-deterministic, so static scoping under-counts its reach. A service account runs the same code path every time. An agent's behaviour is a function of a model's output, which moves with the input. The same agent, given the same nominal task, may pick a different tool or follow a different path on a second run. What an agent can do is therefore harder to bound by inspection than conventional software, and the broad grant in step two of the pipeline is rarely understood as broad at the time it is made.
An agent's authority is composite, so the effective permission set is easy to misjudge. An agent often acts on behalf of a user, inheriting part of that user's access, while also holding its own identity and its own permissions. The reach is the union of the two, and the union is routinely underestimated. Microsoft's model separates the cases explicitly, distinguishing delegated-access agents that act on behalf of a user from own-access agents that operate with their own identity not tied to a user session (Microsoft Learn, 2026).
An agent delegates, so a narrow grant becomes broad reach through inheritance. An agent calls other agents, and those call further agents. Permission inheritance down a delegation chain is how a tightly scoped task acquires a wide blast radius. Excessive agency, which the OWASP Top 10 for Agentic Applications (December 2025) names as a primary risk, is most often the product of an under-controlled delegation chain rather than a single over-permissioned agent (OWASP, 2025).
An agent persists, so step five of the pipeline is the default rather than the exception. Once deployed, an agent and its credential typically outlive the task that justified them. Only 22 per cent of organisations treat their agents as independent identities with their own lifecycle; the rest rely on shared keys, human credentials, or generic service accounts, leaving credential and entitlement sprawl that persists indefinitely (industry research, 2026).
2.3 The population behind the pipeline, quantified
The pipeline scales with the size of the non-human population, and that population has crossed a threshold that changes what identity management is for. Identity is no longer principally about people.
The reported ratios vary by estate type, and the variation is itself the finding. Machine identities outnumber human employees by more than 80 to one across the enterprises in CyberArk's 2026 study (CyberArk, 2026). Other research places the modern-enterprise ratio between 25 and 50 to one, rising to 82 to one in some populations, to 144 to one in cloud-native and DevOps environments, and to as much as 500 to one in hyper-automated organisations (industry research, 2026). Agent-heavy estates reach 100 to one and beyond (industry estimates, 2026).
| Estate type | Non-human to human identity ratio | Source basis |
|---|---|---|
| Enterprise average | More than 80: 1 | CyberArk, 2026 |
| Modern enterprise (range) | 25–50: 1 | Industry research, 2026 |
| Agent-heavy enterprise | 100: 1 and beyond | Industry estimates, 2026 |
| Cloud-native / DevOps | 144: 1 | Industry research, 2026 |
| Hyper-automated | Up to 500: 1 | Industry research, 2026 |
Ratios are drawn from differing survey bases and are not strictly comparable. The consistent signal is that non-human identities outnumber human users by at least one, and frequently two, orders of magnitude.
By the numbers: the identity inversion. Across large enterprises, machine identities outnumber human users by more than 80 to 1 (CyberArk, 2026). In agent-heavy estates the ratio reaches 100 to 1 and beyond. The human security team can usually account for the human identities. It can account for almost none of the machine identities, and least of all the agents, which are the fastest-growing slice and the one whose reach is hardest to bound.
2.4 The proof the pipeline is running: the audit gap
The single clearest measure that this pipeline is live in most estates is that organisations cannot demonstrate control of their agents to an auditor. Eighty-four per cent report that they could not currently pass a compliance audit focused on agent behaviour or access controls (Cloud Security Alliance, 2026). Only 23 per cent have a formal agent identity strategy, and only 18 per cent are confident that their existing identity and access management can manage agent identities at all (Cloud Security Alliance, 2026, survey of 285 IT and security professionals).
| Capability | Share of organisations | Source |
|---|---|---|
| Could pass an audit of agent behaviour or access | 16% | Cloud Security Alliance, 2026 |
| Have a formal agent identity strategy | 23% | Cloud Security Alliance, 2026 |
| Confident existing IAM can manage agent identities | 18% | Cloud Security Alliance, 2026 |
| Treat agents as independent identities with a lifecycle | 22% | Industry research, 2026 |
The first row is the inverse of the 84 per cent who report they doubt they could pass such an audit; both figures are retained as the source presents them.
These four numbers describe the same gap from four angles. The enterprise stood up a non-human workforce faster than it built the controls to govern it, and the pipeline of section 2.1 has been running in the interval. Closing it is the subject of the rest of this paper.
2.5 The implication for the security agenda
The agent-security problem reduces to a non-human-identity problem, and the proof is that every step of the breach pipeline is an identity control that was skipped: no identity, no registration, no scoping, no logging, no revocation. None of these is a network control and none is a data-loss control in the first instance. The first move is therefore to give every agent a first-class identity and put it in a registry, which makes the population countable and the pipeline breakable. That is the subject of chapter two.
Chapter two: Making the invisible workforce countable: identity as the control plane
The takeaway
What cannot be enumerated cannot be governed, so identity is the control plane and not one control among several. An agent with a first-class, cryptographic identity becomes governable in every other dimension; an agent without one is governable in none. Microsoft Entra Agent ID supplies that identity in the Microsoft estate through a specific object model, blueprint, blueprint principal, agent identity, and agent user, that an identity team must understand before it configures anything downstream. The agent registry, consolidated into Microsoft Agent 365, is the inventory that turns the invisible workforce into a counted one.
3.1 What "first-class" buys, and what its absence costs
A first-class identity is one the identity platform recognises natively, as it recognises a user or a workload, rather than a secret bolted onto a human account. The distinction is the whole of the matter, because every downstream control depends on it.
A first-class agent identity has four properties. It is cryptographic, authenticating through managed credentials and standard protocols rather than a shared key. It is enumerable, appearing in a directory where it can be found, attributed, and counted. It is policy-addressable, so access policy can target it specifically. It is lifecycle-managed, so it can be created, governed, and decommissioned as a managed object.
Read those four properties against the breach pipeline of chapter one and each maps to a step the pipeline skipped: cryptographic credentials replace the standing secret, enumeration ends the missing inventory, policy-addressability enables scoping, lifecycle management forces withdrawal at task end. An agent that authenticates with a human user's credentials, or with a generic service account shared across many agents, has none of the four. It cannot be told apart from the human or from its siblings, cannot be policy-addressed on its own, and cannot be revoked without breaking everything that shares the credential. This is the configuration 78 per cent of organisations still run, by the inverse of the 22 per cent who treat agents as managed identities (industry research, 2026).
3.2 The Entra Agent ID object model
Microsoft Entra Agent ID reached general availability in April 2026 and extends Microsoft Entra identity and access management to AI agents (Microsoft, 2026). The object model has to be understood before anything else is configured, because conditional access, governance, and auditing all reference these objects by name. The model below is drawn from Microsoft's own definitions (Microsoft Learn, 2026).
| Object | What it is | Function |
|---|---|---|
| Agent blueprint | A logical definition of an agent type | A template carrying consistent security policy for many agents |
| Agent identity blueprint principal | A service principal representing the blueprint in the tenant | Executes only the creation of agent identities and agent users; cannot itself access resources |
| Agent identity | An instantiated agent identity | Acquires tokens to access resources; the actor in agentic tasks |
| Agent user | A non-human user identity for agent experiences requiring a user account | Acquires tokens to access resources where a user context is required |
| Agent resource | A blueprint or agent identity acting as the resource | The target in agent-to-agent flows |
The blueprint-to-identity relationship is what lets the model scale. A blueprint is authored once, carrying its security policy, and individual agent identities are instantiated from it in a parent-child relationship (Microsoft Learn, 2026). Policy set on the blueprint covers every agent identity parented by it, which is how an identity team governs thousands of agents without touching each one. This is the answer to the non-determinism problem of chapter one: scope is fixed at the template rather than chased per instance.
The platform authenticates and communicates over standard protocols, OAuth 2.0 for authorisation, the Model Context Protocol (MCP) for tool connection, and the Agent-to-Agent (A2A) protocol for inter-agent communication (Microsoft Learn, 2026). Standard protocols are what let the same identity be recognised across Microsoft and non-Microsoft platforms.
One governance-design point is worth fixing in mind. The blueprint principal can create agent identities but cannot itself access resources, and its creation calls are deliberately excluded from conditional-access evaluation (Microsoft Learn, 2026). The control surface is therefore the agent identity and the agent user: the objects that acquire tokens and reach data. Scope policy to those, not to the blueprint principal.
3.3 Delegated access versus own access: the most consequential choice
The most consequential single choice in agent identity is whether an agent acts on behalf of a user or in its own right. The two carry different permission semantics, different blast radii, and different control maturity.
A delegated-access agent acts on behalf of a signed-in user and acquires access in that user's context. Conditional Access for delegated-access agents reached general availability and extends the organisation's existing user policies to the agent acting on the user's behalf (industry reporting, 2026). The agent inherits the user's policy posture, a convenience and a liability at once, because the agent then carries the user's reach into every tool it touches.
An own-access agent runs with its own identity, tied to no user session, and operates autonomously. Conditional Access for own-access agents was in public preview as of mid-2026 (industry reporting, 2026). This is the harder case: the agent's authority is entirely its own and must be scoped from first principles rather than inherited, which is precisely where the broad grant of the breach pipeline takes hold.
The design rule follows directly. Prefer delegated access wherever a clear human principal exists and the agent should not exceed that person's reach. Reserve own-access identities for genuinely autonomous, event-triggered agents, and then scope them to least privilege explicitly. An own-access agent handed broad standing authority is the chapter-one pipeline reconstituted in a single object.
3.4 The registry: turning the population into an inventory
An identity that is not inventoried is not governed, because it cannot be found. The agent registry is the inventory of every agent in the tenant, and it is the literal answer to the question that titles this paper.
The registry shipped first as a standalone Entra blade and was consolidated into Microsoft Agent 365 on 1 May 2026, making Agent 365 the single control plane for agent visibility, governance, and security across the tenant (Microsoft, 2026). Through it a security team can ask which agents exist, what identities they use, what data they touch, where they run, which models they depend on, and how their actions are audited (Microsoft, 2026). Those six questions are the inverse of the six things the breach pipeline left unknown.
The registry is only useful if it records both in-house and third-party agents, because shadow agents are the largest exposure. Entra Agent ID brings third-party agents built on platforms such as Amazon Web Services Bedrock and n8n under a governed identity through the Microsoft Entra Auth software development kit or workload identity federation, regardless of where the agent was built (Microsoft Learn, 2026). An estate that registers only Microsoft-built agents leaves its biggest gap unmeasured and the pipeline running underneath it.
By the numbers: the visibility precondition. Microsoft Entra Agent ID reached general availability in April 2026; Microsoft Agent 365 reached general availability on 1 May 2026; the agent registry consolidated into Agent 365 on the same date (Microsoft, 2026). The control plane is a shipped product, not a roadmap item. What is missing in most estates is adoption, not availability.
3.5 The implication for the security agenda
Identity is the control plane and the registry is its first instrument. An agent given a first-class Entra Agent ID identity, recorded in the Agent 365 registry, and correctly classified as delegated-access or own-access is an agent that can now be scoped, evaluated, logged, and revoked. The agent that lacks these cannot be governed at all, and stays on the breach pipeline. Scoping, evaluation, logging, and revocation, the four mechanics an identity team operates against a counted estate, are the subject of chapter three.
Chapter three: Closing the four gaps: scope, conditional access, audit, and revocation
The takeaway
A counted estate is not yet a governed one. Four configured mechanics close the four gaps the breach pipeline opened. Least privilege binds to the tool call and the credential, not to the agent. Conditional Access evaluates every token an agent acquires, scopes policy by attribute or blueprint, and blocks high-risk agents. Auditing captures every authentication, invocation, and policy decision in a reviewable form. Revocation withdraws an agent's authority instantly and estate-wide. An identity team configures all four, and this chapter specifies how.
4.1 The posture, and why principle alone changes nothing
The posture now codified across the industry is that no agent is trusted by default, regardless of purpose or claimed capability, and that trust is earned through demonstrated behaviour and continuously verified through monitoring (Cloud Security Alliance, 2026). The principle is correct and inert until it is turned into settings. The four mechanics below are those settings, configurations, not aspirations, and each one closes a named step of the chapter-one pipeline.
The translation follows the Cloud Security Alliance Agentic Trust Framework, published on 2 February 2026, which names five core elements, identity, behaviour monitoring, data governance, segmentation, and incident response, required at every maturity level, with controls scaling as the agent earns autonomy (Cloud Security Alliance, 2026). Identity, established in chapter two, is the precondition; the other four assume it. The framework's maturity model runs from Intern to Principal across four levels, with agents starting read-only and earning autonomy through demonstrated trustworthiness across five gates (Cloud Security Alliance, 2026).
4.2 Gap one: least privilege at the tool call and the credential
Least privilege for agents does not live at the agent. It lives at each tool the agent calls and at the credential the agent holds. This is the correction to the most common agent-security error: scoping the agent once at deployment and calling the task done. That single grant is step two of the breach pipeline.
Scope the tool, not the agent. An agent's effective authority is the union of the tools it can invoke. Excessive agency arises when an agent holds more tool permissions than its task requires (OWASP, 2025). The control is to grant each agent only the specific tool permissions its task needs, and to constrain permission inheritance down delegation chains so a sub-agent cannot exceed its parent's scope. The Cloud Security Alliance framework requires least privilege at every step of recursive delegation, not only at the top, which directly counters the delegation-chain reach described in chapter one (Cloud Security Alliance, 2026).
Make the credential short-lived and purpose-bound. The standing secret is the durable exposure and step four of the pipeline. The control is just-in-time, purpose-bound access: a temporary, scoped credential that expires automatically when the task completes (industry research, 2026). The Cloud Security Alliance framework requires just-in-time provisioning and automatic credential expiration, yet most organisations still provision agent credentials at deployment and never revisit them (Cloud Security Alliance, 2026). Auto-expiry also closes step five, withdrawing access at task end without relying on anyone to remember.
The contrast between prevailing and required practice is set out below.
| Dimension | Prevailing practice | Least-privilege practice |
|---|---|---|
| Credential | Standing secret, no expiry | Just-in-time, auto-expiring, purpose-bound |
| Scope unit | The agent, set once at deployment | Each tool call, evaluated per task |
| Delegation | Inherited broadly down the chain | Constrained at every step; sub-agent ≤ parent |
| Permission review | Never revisited | Continuous; access withdrawn on task completion |
| Identity basis | Shared key or human credential | First-class agent identity |
Sources: OWASP Top 10 for Agentic Applications, 2025; Cloud Security Alliance Agentic Trust Framework, 2026; industry research, 2026.
4.3 Gap two: Conditional Access on every token
Conditional Access is the policy engine that evaluates each access request in real time against context and risk. For agents it treats the agent as a first-class identity and evaluates its requests as it evaluates a user's, with agent-specific logic (Microsoft Learn, 2026). The mechanics are precise and configurable, and an identity team should know them exactly.
What is evaluated. Conditional Access fires whenever an agent identity requests a token for any resource, and whenever an agent user requests a token for any resource (Microsoft Learn, 2026). It deliberately does not fire when a blueprint principal acquires a token only to create an agent identity, nor on intermediate token-exchange calls that reach no resource. The control surface is the token acquisition that touches data: the exact point the breach pipeline left ungoverned.
How policy is scoped. Policy can target all agent identities in the tenant, specific agent identities by object identifier, agent identities grouped by custom security attribute, agent identities grouped by their blueprint, or all agent users (Microsoft Learn, 2026). The custom-security-attribute method is the recommended approach for an approval workflow: an attribute such as AgentApprovalStatus carries values such as In_Review, HR_Approved, or IT_Approved, and policy blocks every agent except those carrying an approved value (Microsoft Learn, 2026). This is the inventory of chapter two turned into an enforcement gate.
What conditions are assessed. The principal condition is agent risk, scored high, medium, or low from Microsoft Entra ID Protection signals (Microsoft Learn, 2026). The available access control is to block. Policies can run report-only first to simulate impact before enforcement, then be toggled on (Microsoft Learn, 2026).
Two canonical policies belong first in any configuration (Microsoft Learn, 2026). The first blocks every agent except those carrying an approved custom security attribute, putting an approval gate across the estate. The second blocks any agent that Identity Protection rates high-risk, pulling a compromised or anomalous agent off resource access automatically. Deploy both in report-only mode, review impact, then promote to enforcement.
4.4 Gap three: audit that survives an auditor
An action logged in no reviewable form did not, for governance purposes, happen in a governable system. The audit trail is the evidentiary base of the entire posture and the precise gap that 84 per cent of organisations doubt they could close (Cloud Security Alliance, 2026). It is also step five of the breach pipeline: the action no analyst would ever review.
What must be logged. Every agent authentication, token acquisition, tool invocation, and policy decision has to be captured, recording what happened and on whose behalf, under what policy, and why (industry guidance, 2026). All agent authentication and activity is logged in Entra for compliance and audit (Microsoft Learn, 2026).
Where it lands. Agent activity surfaces across the Entra sign-in and audit logs with agent-specific filtering. Agent identities acting as the actor appear in service principal sign-in logs; agent users appear in non-interactive user sign-ins; users invoking agents appear in interactive user sign-ins (Microsoft Learn, 2026). Every agent action is logged with a unique Agent identifier, which is what attributes an action to a specific agent rather than to a shared account: the attribution the breach pipeline destroyed at step three (Microsoft, 2026).
How it joins the wider estate. Agent activity is captured automatically for audit and classification, and the organisation's existing data-loss-prevention policies, sensitivity labels, and compliance controls in Microsoft Purview apply to agents (Microsoft Learn, 2026). When a suspicious action leaves the tenant via a delegated agent, the relevant Purview audit records, the agent's service-principal sign-in logs, and the Defender inspection verdict assemble into a single investigation package, cutting investigation time from hours to minutes (Microsoft, 2026).
| Audit question | Where answered | Mechanism |
|---|---|---|
| Which agent acted? | Sign-in / audit logs | Unique Agent ID per action |
| On whose behalf? | Sign-in logs | Delegated vs own-access flow record |
| Under what policy? | Conditional Access logs | Policy evaluation result, including report-only |
| What data was touched? | Purview audit / DSPM for AI | DLP, sensitivity labels, classification |
| Was it anomalous? | Identity Protection | Agent risk score; Defender verdict |
4.5 Gap four: revocation that has actually been tested
The last mechanic is the power to cut an agent's authority instantly, and it is the one most often assumed and least often exercised. Revocation is the offboarding of a digital employee, and it has to be as reliable as the offboarding of a human one: closing step five of the breach pipeline on demand rather than at task end.
Because an Entra Agent ID identity is a first-class, managed object, it can be disabled, its access revoked, and its tokens invalidated through the same identity-governance machinery that offboards a user. Conditional Access supplies the rapid-response layer: a policy blocking a named agent identity, or every agent except an approved set, takes effect at the next token acquisition. A high-risk signal from Identity Protection blocks an agent automatically through the conditional-access policy of section 4.3 (Microsoft Learn, 2026).
What separates a credible programme from a paper one is that revocation is tested, not assumed. Exercise the kill-switch against a live agent in a controlled window and confirm three things: the agent loses resource access, its tokens stop working, and the action is logged. An untested kill-switch is a hope, and a breach is the one test no one wants to run first.
4.6 The implication for the security agenda
Zero Trust for agents is four configured mechanics that close the four gaps the breach pipeline opened: least privilege at the tool and credential, conditional access on every token, audit of every action, and tested revocation. Each is available in the Entra and Agent 365 estate today, and each maps onto the Cloud Security Alliance and OWASP frameworks. What remains is to sequence their deployment so the foundation precedes the autonomy, which is chapter four.
Chapter four: Sequencing the controls: reference architecture, rollout, and maturity
The takeaway
The identity controls for agents stack into a layered architecture, and the layers have a forced order: identity, then registry, then policy, then audit, then revocation, because each depends on the one beneath it. The rollout runs over roughly twelve months, and a maturity model lets a team place itself and define the next increment. The single discipline that separates success from rogue exposure is that the identity foundation precedes the first autonomous agent rather than chasing it. Build the layers out of order and the breach pipeline reappears between them.
5.1 The reference architecture
The architecture below is anchored to the Microsoft estate, consistent with this paper's lens, but the layering is portable. Its value is that each layer is a distinct control that can be configured, audited, and operated on its own while depending on the layer under it, which is also why skipping a lower layer leaves a gap the breach pipeline runs straight through.
The identity layer. Microsoft Entra Agent ID, assigning each agent a first-class identity through the blueprint and agent-identity object model. The foundation; nothing above it functions without it.
The registry layer. The agent registry in Microsoft Agent 365, inventorying every agent, Microsoft-built, third-party, and autonomous, so the estate is visible and attributable.
The policy layer. Conditional Access for agents, evaluating every token acquisition against scope, approval attribute, and agent risk, with Identity Protection supplying the risk signal.
The audit layer. The Entra sign-in and audit logs, integrated with Microsoft Purview for data classification and data-loss prevention and with Microsoft Defender for threat detection, capturing every action with a unique Agent identifier.
The response layer. Revocation and the kill-switch, through identity-governance lifecycle controls and rapid-response conditional-access policies, tested rather than assumed.
The architectural principle is that identity governance is a layer spanning the estate, not a feature embedded in each agent. That is what lets one control plane govern agents built in-house, by third parties, and on competing platforms: the multi-vendor reality the reference flagship established.
5.2 The licensing prerequisites
The controls carry specific licensing prerequisites, and a team should confirm them before committing to a sequence. Microsoft sets them out as follows (Microsoft Learn, 2026).
| Capability | Licence required |
|---|---|
| Agent identity platform (create and manage agent identities) | Available to all Microsoft Entra customers |
| Operate agents across Microsoft 365 and enterprise workflows | Microsoft Agent 365 licence per user |
| Conditional Access for agents | Microsoft Entra ID P1 |
| Identity Protection for agents | Microsoft Entra ID P2 |
| Identity Governance for agents | Microsoft Entra ID P1 |
| Network controls for agents | Microsoft Entra Internet Access (Entra Suite or separate) |
New Entra service plans for Conditional Access for agents and ID Protection for agents began their general-availability rollout in early July 2026 and were expected to complete by early August 2026, added to Microsoft Agent 365 and Microsoft 365 E7 (industry reporting, 2026). The practical reading is that an enterprise on E5, or holding P1 and P2 already, owns most of the entitlement. The gap is configuration, not procurement.
5.3 The rollout roadmap
The roadmap sequences the five layers over roughly twelve months. It is deliberately conservative on agent autonomy and deliberately aggressive on identity foundation: the inverse of the failure pattern in which agents proliferate before the controls exist.
Stage one, the first 60 days: establish identity and inventory. Configure Microsoft Entra Agent ID. Author agent blueprints carrying baseline security policy. Stand up the agent registry in Agent 365 and onboard every existing agent into it, including the third-party and shadow agents surfaced in the process. The objective is a complete, attributable inventory and a first-class identity for every agent. Past this stage, no autonomous agent operates outside the registry.
Stage two, months two to five: enforce policy and least privilege. Deploy the two canonical conditional-access policies in report-only mode: the approval-attribute block and the high-risk block. Review impact, then promote to enforcement. Convert standing agent credentials to just-in-time, purpose-bound credentials. Scope tool permissions per agent and constrain delegation inheritance. The objective is least privilege at the tool and the credential, with policy evaluating every token.
Stage three, months five to nine: instrument audit and integrate. Confirm that every authentication, token acquisition, tool invocation, and policy decision is logged with a unique Agent identifier. Integrate Entra logs with Microsoft Purview for data classification and data-loss prevention and with Microsoft Defender for threat detection. Validate that an agent action assembles into a single investigation package. The objective is an audit trail that would pass the agent-behaviour audit 84 per cent of organisations doubt they could pass.
Stage four, months nine to twelve: test revocation and operationalise. Exercise the kill-switch against a live agent in a controlled window, confirming loss of access, token invalidation, and logging. Fold agent offboarding into the identity-governance lifecycle so decommissioning is routine rather than exceptional. The objective is a tested revocation capability and a steady-state operating rhythm for the estate.
5.4 The identity maturity model
The model lets a team place the enterprise and define the next increment. It is the diagnostic counterpart to the roadmap and aligns with the Intern-to-Principal progression of the Cloud Security Alliance framework, in which agents earn autonomy through demonstrated trustworthiness (Cloud Security Alliance, 2026). Read the levels against chapter one: Level 0 is the breach pipeline running unbroken; each higher level breaks one more step.
| Level | Identity state | Access control | Audit and revocation | Typical exposure |
|---|---|---|---|---|
| 0: Invisible | Agents use shared keys or human credentials; no inventory | None scoped to agents | No agent-specific logging; no kill-switch | Rogue exposure; cannot pass audit |
| 1: Identified | Every agent has a first-class Entra Agent ID identity; registered in Agent 365 | Inherited or broad | Agent actions logged with unique ID | Visible but over-permissioned |
| 2: Scoped | First-class identity; delegated vs own-access classified | Conditional Access enforced; least privilege at tool and credential | Full sign-in and audit logging; revocation defined | Controlled; audit-ready |
| 3: Verified | Identity plus continuous risk evaluation | Risk-adaptive Conditional Access; JIT credentials estate-wide | Purview and Defender integrated; kill-switch tested | Low; continuously verified |
| 4: Governed estate | Estate-wide identity spanning Microsoft and third-party agents | Policy spans vendors; delegation constrained end-to-end | Unified investigation; routine offboarding | Minimal; demonstrable to auditor |
Most enterprises sit between Level 0 and Level 1 as of mid-2026, consistent with the finding that only 22 to 23 per cent treat agents as managed identities (Cloud Security Alliance, 2026; industry research, 2026). The audit-ready threshold is Level 2.
5.5 The implication for the security agenda
The controls are a sequence, not a menu, and the sequence is identity, registry, policy, audit, revocation. The enterprise that deploys them in that order, with the identity foundation ahead of the first autonomous agent, reaches the audit-ready Level 2 within months. The enterprise that deploys agents first and controls later rebuilds the rogue exposure of chapter one between its half-built layers. The order is the discipline.
Chapter five: The identity leadership agenda
The question that titles this paper, who is accessing your data, has a determinate answer in any well-governed enterprise and a frightening one in every other. The evidence assembled here resolves into a few clear conclusions for the chief information security officer and the identity leadership.
The population reaching corporate data is predominantly non-human, outnumbering human users by more than 80 to one and climbing (CyberArk, 2026). Agents are its fastest-growing and least-governed part, and they differ from prior machine identities in that they reason, delegate, and persist. The exposure they create is structural, a five-step pipeline in which every step is a skipped identity control, and it is already producing breaches. Break the pipeline at any step and the breach does not occur.
The controls to break it exist and are generally available. Microsoft Entra Agent ID reached general availability in April 2026 and Microsoft Agent 365 on 1 May 2026 (Microsoft, 2026). The constraint is not availability but configuration and sequence. Eighty-four per cent of organisations cannot currently pass an audit of agent behaviour, and the path to closing that gap is the staged rollout of chapter four (Cloud Security Alliance, 2026).
Five questions belong on the identity leadership agenda. First, can the enterprise produce a complete inventory of its agents, including third-party and shadow agents, and does every agent hold a first-class identity. Second, is each agent correctly classified as delegated-access or own-access, and is own-access reserved for genuinely autonomous agents scoped from first principles. Third, is least privilege enforced at the tool call and the credential, with just-in-time expiry, or is the agent scoped once at deployment and forgotten. Fourth, does Conditional Access evaluate every token an agent acquires, and is the audit trail enough to pass an agent-behaviour audit. Fifth, has the kill-switch been fired against a live agent, or is revocation still an assumption.
Volge's role is in the execution. The platform decision is, for most enterprises, already made by their existing Microsoft and Entra commitments. The disciplines that convert that commitment into a governed agent estate, the identity object model, the registry, the conditional-access policy design, the least-privilege credential lifecycle, the audit integration, and the tested kill-switch: are where security programmes either succeed or expose the enterprise. Volge looks forward to applying this framework to specific identity estates in detail.
Appendices
Appendix A: Agent identity controls and capability matrix
The following maps each identity control to its Microsoft capability and its framework reference, as of June 2026.
| Control | Microsoft capability | Framework reference | Availability |
|---|---|---|---|
| First-class agent identity | Entra Agent ID (blueprint, agent identity, agent user) | CSA ATF element 1 (Identity); OWASP excessive agency | GA April 2026 |
| Agent inventory / registry | Agent registry in Microsoft Agent 365 | CSA ATF element 1 (Identity) | GA 1 May 2026 |
| Third-party agent onboarding | Entra Auth SDK (sidecar) / workload identity federation | CSA ATF element 1 (Identity) | GA 2026 |
| Conditional access (delegated) | Conditional Access for agents | CSA ATF element 4 (Segmentation) | GA 2026 |
| Conditional access (own-access) | Conditional Access for agents | CSA ATF element 4 (Segmentation) | Public preview, mid-2026 |
| Risk-based blocking | Identity Protection for agents (agent risk) | CSA ATF element 2 (Behaviour monitoring) | GA rollout Jul–Aug 2026 |
| Least privilege at tool call | Tool-scoped permissions; delegation constraint | OWASP excessive agency; CSA recursive least privilege | Configuration |
| Just-in-time credentials | Purpose-bound, auto-expiring credentials | CSA ATF (JIT provisioning, auto-expiry) | Configuration |
| Audit logging | Entra sign-in and audit logs; unique Agent ID | CSA ATF element 2; OWASP | GA 2026 |
| Data governance | Microsoft Purview (DLP, sensitivity labels, DSPM for AI) | CSA ATF element 3 (Data governance) | GA 2026 |
| Threat detection / response | Microsoft Defender; investigation package | CSA ATF element 5 (Incident response) | GA 2026 |
| Revocation / kill-switch | Identity governance lifecycle; rapid-response CA policy | CSA ATF element 5 (Incident response) | GA 2026 |
Sources: Microsoft Learn and Microsoft announcements, 2026; Cloud Security Alliance Agentic Trust Framework, February 2026; OWASP Top 10 for Agentic Applications, December 2025.
Appendix B: Identity-governance checklist for agents
The following is a minimum identity control set, drawn from Microsoft Entra Agent ID and Agent 365 guidance (2026), the OWASP Top 10 for Agentic Applications (December 2025), and the Cloud Security Alliance Agentic Trust Framework (February 2026). Each block closes one step of the breach pipeline in chapter one.
Identity and inventory
- Every agent holds a first-class, cryptographic Entra Agent ID identity; none authenticates with a shared key or a human credential.
- Every agent is recorded in the Agent 365 registry, including third-party and previously shadow agents.
- Each agent is classified as delegated-access or own-access; own-access is reserved for genuinely autonomous agents.
- Agent blueprints carry baseline security policy so scope is consistent across instantiated identities.
Least privilege
- Tool permissions are scoped per agent to the specific task; no agent holds broad tool access by default.
- Delegation inheritance is constrained so a sub-agent cannot exceed its parent's scope.
- Credentials are just-in-time, purpose-bound, and auto-expiring; no standing secrets persist past the task.
- Access is withdrawn on task completion, not at indefinite future review.
Conditional access and risk
- A conditional-access policy blocks every agent except those carrying an approved custom security attribute.
- A conditional-access policy blocks any agent rated high-risk by Identity Protection.
- Both policies were validated in report-only mode before enforcement.
Audit and revocation
- Every authentication, token acquisition, tool invocation, and policy decision is logged with a unique Agent identifier.
- Entra logs are integrated with Purview (data) and Defender (threat) for unified investigation.
- The kill-switch has been tested against a live agent, confirming loss of access, token invalidation, and logging.
- Agent offboarding is part of the identity-governance lifecycle, not an exceptional manual act.
Appendix C: Glossary
- Agent blueprint. A logical definition of an agent type in Entra Agent ID, serving as a template that carries security policy for many instantiated agent identities.
- Agent identity. An instantiated, first-class identity in Entra Agent ID that acquires tokens and acts against resources.
- Agent user. A non-human user identity in Entra Agent ID used where an agent experience requires a user account.
- Agent registry. The inventory of every agent in the tenant, consolidated into Microsoft Agent 365 on 1 May 2026.
- Agent 365. Microsoft's unified control plane for agent visibility, governance, and security; generally available 1 May 2026.
- Conditional Access for agents. The Entra policy engine extended to evaluate every token an agent acquires against scope, approval attribute, and agent risk.
- Delegated-access agent. An agent that acts on behalf of a signed-in user and acquires access in that user's context.
- Entra Agent ID. Microsoft's identity and security framework assigning a first-class identity to each agent; generally available April 2026.
- Excessive agency. The OWASP-named risk in which an agent holds more permissions, functionality, or autonomy than its task requires.
- Just-in-time credential. A temporary, scoped, purpose-bound credential that expires automatically when the task completes.
- Non-human identity (NHI). A machine, service, or agent credential; NHIs outnumber human users by more than 80:1 in large enterprises.
- Own-access agent. An agent that operates with its own identity, not tied to any user session, typically autonomous and event-triggered.
- Zero Trust. A security posture in which no actor, human or agent, is trusted by default and trust is continuously verified.
Appendix D: Sources
This paper draws on the following, accessed June 2026. Figures are attributed in-text to their primary source. Where a statistic appears across multiple secondary outlets, the most authoritative primary attribution is given.
- Microsoft: Entra Agent ID (general availability April 2026), Agent 365 (general availability 1 May 2026), agent registry convergence, Conditional Access for agents, Identity Protection for agents, and Purview and Defender for agent governance; Microsoft Learn documentation, 2026.
- CyberArk: 2026 report on machine identities outnumbering human identities by more than 80 to one.
- Cloud Security Alliance: Agentic Trust Framework (2 February 2026), authored by Josh Woodruff, Michelle Savage, and John Kindervag; five core elements, four-level maturity model, and companion survey of 285 IT and security professionals.
- OWASP Gen AI Security Project: Top 10 for Agentic Applications (9 December 2025), with input from over 100 contributors; excessive agency, insecure tool execution, and related risks.
- Industry research on non-human identity ratios, machine-identity incident share, agent credential lifecycle practice, and agents acting beyond intended scope, 2025–2026 (including CyberArk, Obsidian Security, and Non-Human Identity Management Group analyses).
- Industry reporting on Entra service-plan rollout for Conditional Access and Identity Protection for agents (July–August 2026) and on delegated versus own-access conditional-access availability.
- Volge flagship: From copilot to autopilot: operationalising autonomous AI agents in the enterprise (June 2026), Voice of Volge series, for the board-level identity and governance position this paper extends.
Addendum: How Volge's forward-deployed engineers shall help: Zero Trust Security
The Volge engagement team
Volge delivers through one accountable team that runs from the boardroom to the production branch. Four roles carry the engagement, and they hold their remit from the first workshop to operational handover rather than handing off between phases.
| Role | What they own |
|---|---|
| Principal | The client relationship and the account. Sets the engagement's business outcomes, the governance cadence, and the value tracking, and stays the single point of accountability throughout. |
| Architect | The target architecture and the transformation roadmap. Sequences the work, sets the standards, and makes the platform, build-versus-buy, and control-design calls. |
| Principals | The senior engineering leads. Each owns a workstream, makes the hard technical calls, sets the quality bar, and mentors the embedded engineers. |
| Forward-deployed engineers | The embedded build. They sit inside the client's team, build and ship in the client's own environment, and own the last mile to production. |
The Principal holds the outcome, the Architect holds the design, the Principals hold the workstreams, and the forward-deployed engineers hold the keyboard, one team, accountable from strategy to shipped software.
This paper has argued that an agent without a first-class, cryptographic identity cannot be inventoried, scoped, audited, or revoked, and that securing the agent estate is therefore an identity programme before it is anything else. The controls it describes, Entra Agent ID, the Agent 365 registry, conditional access on every token, Purview and Defender integration, and a tested kill-switch, are generally available; the constraint, as the paper records, is configuration and sequence rather than procurement. Volge closes that gap through its forward-deployed engineer model.
A Volge forward-deployed engineer is a senior Volge security engineer embedded directly in the client's identity and security team, building inside the client's own Entra tenant and production environment rather than in a detached advisory document or a vendor sandbox. The engineer does the real-world security engineering, the blueprint authoring, the conditional-access policy design, the credential lifecycle, the audit wiring, and the report-only-to-enforced cutover, alongside the client's people, and stays on the work through to production rather than handing a design over a wall. The deliverable is a governed agent estate running in the client's tenant, not a slide pack about one.
The model is built for exactly the constraint this paper identifies. The licences are largely already owned; what is missing is the senior engineering hand to configure and sequence the controls against a live, predominantly non-human estate without breaking the workloads that depend on it. The forward-deployed engineer supplies that hand inside the client's environment.
What a Volge forward-deployed engineer delivers for the client
The capability set below is the work a forward-deployed engineer owns inside the client's tenant, through to production. Each line maps a capability to the outcome the client landscape gains.
| Capability | Client outcome |
|---|---|
| Entra Agent ID rollout, blueprint, agent-identity, and agent-user object model | Every agent, in-house and third-party, holds a first-class, enumerable, policy-addressable identity in place of a shared key or human credential |
| Agent registry build-out in Microsoft Agent 365 | A complete, attributable inventory of the agent estate, including the shadow and third-party agents that carry the largest exposure |
| Least-privilege and conditional-access design | Tool-scoped permissions, just-in-time purpose-bound credentials, and conditional-access policies that evaluate every token by object identifier, custom security attribute, or blueprint |
| Identity Protection and risk-based blocking | High-risk agents pulled off resource access automatically through the risk signal, validated in report-only before enforcement |
| Audit and revocation engineering | Every authentication, token acquisition, tool invocation, and policy decision logged with a unique agent identifier, and a kill-switch tested against a live agent rather than assumed |
| Defender and Purview integration | Agent activity assembled into a single investigation package; existing data-loss-prevention policies, sensitivity labels, and DSPM for AI extended to agents |
| Posture assessment and maturity placement | The estate placed on the identity maturity model, with the next increment defined and the route to audit-ready Level 2 sequenced |
How the forward-deployed engineer works inside the client's tenant
The engineer works the same sequence the paper sets out, executing each step in the client's own environment rather than recommending it from outside.
The engagement is deliberately conservative on agent autonomy and aggressive on identity foundation, mirroring the rollout discipline this paper sets out: the foundation precedes the first autonomous agent rather than chasing it.
Why the forward-deployed engineer model fits this problem
Four things separate an embedded forward-deployed engineer from a licence-and-hope deployment or a detached advisory report.
Embedded in the client's team, building in the client's tenant. The engineer is not a reviewer who returns a document. The engineer sits in the client's identity and security team, configures the controls in the client's own Entra tenant, and stays through to production, so the agent estate is governed where it actually runs, not on paper. The client's people own the result because they built it alongside the engineer.
Identity-first, by conviction. The engineer treats identity as the control plane and not one control among several, because every downstream control, scoping, conditional access, audit, revocation, depends on the first-class identity beneath it. The build sequence is constructed on that order, not bolted onto it afterwards.
Agent and non-human-identity expertise. The forward-deployed engineer is fielded for the identity inversion this paper documents, in which machine identities outnumber human users by orders of magnitude. The engineer implements the delegated-access versus own-access decision, constrains delegation inheritance down recursive chains, and scopes own-access agents from first principles rather than letting them inherit broad standing authority.
Audit-ready as the standard. The audit trail and the tested kill-switch are treated as the floor of the work, not an optional extra. The engineer builds the logging, the Purview and Defender integration, and the revocation drill so that the estate can demonstrate control of its agents to an auditor: the threshold most estates currently sit below.
How the model serves firm and client together
The forward-deployed engineer model is built as a relationship, not a single transaction.
A feedback loop between the field and the practice. Each engagement runs inside a live tenant against a real agent estate, and what the engineer learns there, the configurations that hold under load, the cutover patterns that avoid breaking workloads, the edge cases in delegated versus own-access, feeds back into Volge's hardening practice. The next client benefits from the last one.
Reusable hardening accelerators. Reusable blueprint templates carrying baseline security policy, the two canonical conditional-access policies, report-only validation harnesses, and a maturity-model assessment shorten the path from an ungoverned estate to an audit-ready one. The engineer carries these in and tailors them to the client's tenant rather than starting from a blank page.
An outcomes-based relationship. The measure of the engagement is a governed, audit-ready estate running in the client's own environment, placed on the maturity model, sequenced to Level 2, and operated rather than merely designed. The engineer is accountable for that outcome, not for a deliverable handed over and left.
Capability to outcome
Outcome figures are illustrative of the direction of change and are not a quantified commitment; the investigation-time reduction is drawn from the vendor capability described in chapter three.
A concrete first step. Volge proposes a fixed-scope agent identity posture assessment, run by an embedded forward-deployed engineer inside the client's own tenant: an inventory of the live agent estate, including third-party and shadow agents, classification of each as delegated-access or own-access, a placement on the identity maturity model, and a costed route to audit-ready Level 2. It answers the question that titles this paper, who is accessing your data, for a specific estate, and it leaves the client with a sequenced plan and a working foundation rather than a slogan. Volge would be glad to scope this assessment against the identity estate in question.
Prepared by Volge · June 2026. This document is a point of view intended to inform security and identity decision-making. It is not legal, security, or compliance advice. Statistics are attributed to their sources and were accurate to the best of available knowledge as of June 2026; readers are advised that the agentic-AI and identity-security field is moving rapidly and figures should be reconfirmed before they are relied upon. Product capabilities, availability dates, and licensing are subject to change by the vendor; configurations should be validated against current vendor documentation. Qualified security counsel should be engaged for decisions bearing on regulatory or contractual obligations.
Voice of Volge: the firm's point of view on the technology it delivers. Sourced, year-stamped, and built to be handed to a board.
Volge is an independent deep-tech enterprise service provider and premier Microsoft delivery partner. That interest is disclosed; the analysis in this book is independently sourced.