Agent Passport: Why 88% of AI Agents Fail Before Production

Hyland's Agent Passport ships June 1 as 88% of AI POCs die before production. Compliance scorecard, vendor matrix, and 10-week rollout for CIOs.

By Rajesh Beri·June 2, 2026·13 min read
Share:

THE DAILY BRIEF

AI Agent GovernanceHylandAgent PassportEnterprise Agent MeshCIO StrategyAI ComplianceAgent Lifecycle ManagementAI ObservabilityEnterprise AIProduction AI

Agent Passport: Why 88% of AI Agents Fail Before Production

Hyland's Agent Passport ships June 1 as 88% of AI POCs die before production. Compliance scorecard, vendor matrix, and 10-week rollout for CIOs.

By Rajesh Beri·June 2, 2026·13 min read

Hyland just gave AI agents a passport. On June 1, the Cleveland-based content services giant shipped Enterprise Agent Mesh and Agent Lifecycle Management at general availability, anchored by a new construct called Agent Passport — a standardized, machine-enforceable certification every agent must carry before it touches production. The launch lands in the middle of an enterprise AI crisis with stark numbers: 88% of AI agent proofs of concept never reach production (IDC), 40% of agentic AI projects will be canceled by end of 2027 (Gartner), and only 14.4% of organizations deploy agents with full security and IT approval. The Agent Passport is Hyland's bet that the bottleneck is no longer model quality — it's governance the org chart can trust.

For CIOs and CFOs trying to justify the next AI budget cycle, this is the conversation that determines whether agentic AI delivers on a forecasted $206.5 billion software market in 2026 or becomes the next decommissioning line item.

What Changed: The Agent Passport Construct

Hyland unveiled four interlocking capabilities at CommunityLIVE 2026, described by CEO Jitesh S. Ghai as the move from "pilots to operationalization":

1. Agent Passport (new). A standardized certification that every agent must hold before running in production. It defines the agent's identity, capabilities, guardrails, and compliance status in a format that is both human-readable and machine-enforceable. Governance is applied before deployment, not bolted on after an incident.

2. Agent Library (new). A governed, searchable catalog of every agent in the enterprise — including ownership, function, and version history. The goal: stop the shadow-agent sprawl that Gartner has warned will undermine AI ROI through 2027.

3. Enterprise Agent Mesh (GA). A multi-agent network of use-case-specific agents tailored to healthcare, banking, insurance, government, and higher education — orchestrated under a single governance layer.

4. Control Tower (new). An operational command center for the Mesh that gives organizations real-time observability, KPI tracking, and the ability to pause or adjust agents based on metric thresholds, guardrail violations, or business impact — the "kill switch" enterprises have been demanding since the Gartner I&O ROI stall report in April.

Hyland also confirmed Headless Mode, which exposes the content and data fabric as APIs into Databricks, Snowflake, and custom workflows. This is the architectural signal: Hyland is positioning itself as governance plumbing, not a walled garden — a direct counter to the all-or-nothing platform pitches from larger vendors.

The Agent Passport concept echoes — and arguably formalizes — work from the broader standards community. Cubitrek published a 2026 specification describing Agent Passport as a single signed JSON document published at /.well-known/agent-passport.json on the organization's domain, declaring the agent's issuer, identity, scope of authority, spend ceiling, human-in-loop threshold, audit URL, compliance posture, and validity window. Signed Ed25519 with a public key in a DNS TXT record. The NIST AI Agent Standards Initiative is moving in the same direction. Hyland productized the concept first inside a commercial platform — which is what makes June 1 a turning point.

Why This Matters: The 88% Problem in Plain English

Two numbers explain the panic in the room: the Deloitte 89% pilot-to-production failure rate and the fact that only 14.4% of organizations ship agents with full security or IT approval. The gap is not technical capability — it's the absence of an enforceable handoff between "the model works in a demo" and "the agent has permission to act on a customer record."

Technical Implications (CTO / CIO)

Agent Passport changes the deployment contract. Today, most enterprises rely on point-in-time security reviews — a slide deck, a meeting, a sign-off. The Agent Passport approach makes the contract continuous and machine-readable: an agent without a valid passport literally cannot execute in the mesh. That maps directly onto the OpenTelemetry GenAI Semantic Conventions, which 89% of production observability users now consider "very important." If your agent stack already emits OTel spans (LangChain, CrewAI, AutoGen, AG2 all do natively), the passport becomes the policy companion to the telemetry you're already collecting.

For architecture teams, the integration question is not "do we adopt Hyland?" — it's "do we have an enforceable certification mechanism before our agent count crosses 50?" Most enterprises don't, and the absence is a leading indicator of the 88% failure rate.

Business Implications (CFO / CMO / COO)

Gartner now sizes the AI governance platform market at $492 million in 2026, surpassing $1 billion by 2030. That growth is funded by enterprises that have learned the hard way: an ungoverned agent that touches a customer or a financial system is a regulatory event waiting to happen. The Hyland announcement makes governance budget defensible: it ships with quantified outcomes — Agentic Hospital projects 5x faster referral assembly and 60% more efficient record intake; Agentic Accounts Payable projects 10x faster invoice cycles with 60% cost reduction per invoice and a six-month ROI window.

For CFOs underwriting agent spend, the math now has a control variable. For CMOs and COOs banking on customer-facing agents, the passport is the difference between a board-level incident and a quarterly KPI.

Market Context: The Governance Race Just Got Three-Way

Hyland is not alone in this market. The June launch reframes a competitive landscape that, six weeks ago, looked like a two-vendor race.

ServiceNow. At Knowledge 2026 in early May, ServiceNow extended AI Control Tower governance to Microsoft Agent 365, positioning its Control Tower as the cross-platform command center for first- and third-party agents. Control Tower is now bundled across every ServiceNow package — not an add-on. ServiceNow's edge: install base and workflow integration. Its weakness: it presumes you've standardized on ServiceNow as the system of record.

Microsoft Agent 365. Microsoft extended Entra, Defender, Purview, and Intune to govern AI agents across vendors — the governance control plane for Copilot Studio and Microsoft Foundry. Microsoft's edge: identity and endpoint coverage already in place at most Fortune 1000 shops. Its weakness: tightly coupled to the Microsoft agent runtime.

Hyland. Hyland's bet is different. Its Enterprise Context Engine couples agents to industry-specific ontologies — maps of entities, terminology, relationships, and rules for healthcare, insurance, financial services, education, and government. The Agent Passport is the certification layer that sits on top. Hyland's edge: vertical depth and content-aware context. Its weakness: smaller install base outside content services.

The analyst lens is sharpening. Forrester frames 2026 as the year of "ROI gatekeeping" — where governance becomes the precondition for budget. IDC frames it as the "agentic disruption" year — where unmanaged agent sprawl forces a governance reckoning. Gartner's harshest line: most agentic AI propositions lack significant value or ROI today, and over 40% will be canceled by end of 2027. All three converge on the same conclusion: governance is no longer optional infrastructure.

McKinsey's countervailing data: organizations that get to production are seeing an average 5.8x ROI within 14 months. The prize for solving the 88% problem is substantial. The penalty for ignoring it is the cancellation list.

Framework #1: Agent Passport Readiness Scorecard

Before you evaluate a vendor — or build governance in-house — score your organization across the five Agent Passport dimensions. Each scores 1-5; 25 points total.

The 5 Dimensions

1. Identity & Issuer (1-5). Does every agent have a verifiable, cryptographically signed identity tied to a named owner and business unit? Score 1 if agents run under shared service accounts. Score 5 if every agent has a unique signed identity with rotation policy and DNS-anchored or PKI-anchored verification.

2. Scope & Authority (1-5). Are the agent's tools, data access, and decision authority explicitly enumerated and machine-enforced at runtime? Score 1 if scope is documented in a wiki. Score 5 if scope is enforced by the runtime (the agent literally cannot exceed it).

3. Spend & Risk Ceilings (1-5). Are dollar ceilings (API spend, transaction value, refund authority) and risk ceilings (PII access, customer record writes) explicit and rate-limited? Score 1 if there are no ceilings. Score 5 if every passport carries hard caps with automated freeze on breach.

4. Human-in-the-Loop Thresholds (1-5). Are the conditions under which the agent must escalate to a human explicit, enforced, and audited? Score 1 if escalation is the agent's own judgment. Score 5 if thresholds are codified in the passport and observable through Control Tower telemetry.

5. Audit & Lifecycle (1-5). Is there a real-time audit trail, a defined validity window for the passport, a renewal process, and a documented retirement path? Score 1 if "we'll figure it out." Score 5 if every passport has issuance, renewal, revocation, and decommissioning logged automatically.

Scoring

Score Posture What to do
5-9 Not ready. You are in the 88% Stop scaling agents. Build the passport layer first or buy one.
10-14 Low maturity. Material risk Pause new agent deployments. Run a 12-week governance sprint.
15-19 Medium maturity. Manageable Standardize the passport schema across business units. Pilot Control Tower-class observability.
20-25 High maturity. You are in the 12% Focus on lifecycle automation and cross-vendor enforcement.

Take the test once for each business unit running agents. The variance across BUs is usually where the breach happens.

Framework #2: AI Agent Governance Platform Decision Matrix

The three commercial paths plus build-in-house, scored against the questions CIOs ask in vendor reviews.

Criterion Hyland Agent Mesh ServiceNow AI Control Tower Microsoft Agent 365 Build In-House
Time to first governed agent 6-10 weeks 4-8 weeks (if on ServiceNow) 4-6 weeks (if on M365 + Entra) 6-12 months
Cross-vendor agent governance Strong (Headless APIs into Databricks, Snowflake, third parties) Strong (added Microsoft Agent 365 governance May 2026) Moderate (best when M365 is the runtime) Depends on team
Industry vertical depth Strongest (healthcare, banking, insurance, gov, edu ontologies) Moderate (workflow templates) Weak (horizontal) None out of box
Agent Passport / certification primitive Productized "Discovery + risk score" model Identity-anchored (Entra) DIY
Observability standard Control Tower (proprietary + APIs) Bundled across packages Defender/Purview integration OTel preferred
Best fit for Content-heavy verticals, regulated industries Existing ServiceNow shops M365-standardized shops Hyperscalers, AI-native firms
Total annual cost (mid-market, 50-200 agents) $250K-$900K (platform + services) Bundled if on ServiceNow base Bundled if on M365 E5 $1.2M-$3M (engineering + ops)
Risk if wrong Lock-in to Hyland content fabric Lock-in to ServiceNow workflows Lock-in to Microsoft runtime Indefinite build, delayed ROI

How to read it. If your agents operate primarily on content and regulated workflows (claims, referrals, AP, underwriting), Hyland is the shortest path to a defensible production posture. If ServiceNow is already your system of record, the bundled Control Tower is hard to argue against. If your identity backbone is Entra and your agent runtime is Copilot Studio, Microsoft Agent 365 is the lowest-friction option. Build in-house only if you have a dedicated platform team and a multi-year horizon — the $1B+ governance market by 2030 exists because most enterprises came to that conclusion the hard way.

Real-World Example: The Agentic AP Case

Hyland's most concrete proof point is its Agentic Accounts Payable solution, projected to drive 10x faster invoice cycle times with a 60% reduction in cost per invoice and a six-month ROI window. Translate that into a Fortune 500 manufacturing comparison:

  • Baseline. 250,000 invoices/year. Average processing cost: $14/invoice. Annual cost: $3.5M. Average cycle: 12 days.
  • Post-deployment. Cost per invoice drops to $5.60 (60% reduction). Annual cost: $1.4M. Cycle compresses to ~1.2 days.
  • Annual savings: $2.1M. Platform + services (12-month): ~$650K. Payback: ~3.7 months — inside Hyland's six-month projection.

The lesson is not that the savings are unique to Hyland — they're attainable on multiple platforms. The lesson is that the savings are only bankable if the agents are governed enough to survive a controller's audit. Without a passport-equivalent, the same automation is one PII incident away from being shut down by Legal. That is exactly the failure mode behind the Gartner cancellation forecast.

For banking, the parallel proof point is Agentic Bank: applications to underwriter-ready status in days instead of weeks. The economic value is enormous; the governance prerequisite is the gating function.

Implementation Timeline: 10-Week Pilot to Production

Whether you choose Hyland, ServiceNow, Microsoft, or a hybrid, the rollout shape is similar.

Weeks 1-2: Inventory and scorecard. Run the 25-point readiness scorecard for each BU. Inventory existing agents (most enterprises discover 2-3x what they thought). Identify the top three governance gaps.

Weeks 3-4: Passport schema and policy. Define your passport schema: identity, scope, ceilings, HITL thresholds, audit. Align with legal, security, and finance. Pick one high-stakes use case for pilot (AP, claims, underwriting, clinical referral).

Weeks 5-6: Pilot deployment. Deploy one agent under full passport governance. Wire Control Tower-class observability (OTel spans, KPI dashboards). Set thresholds and verify the kill switch works in a real freeze drill.

Weeks 7-8: Expand to three agents. Add two more agents in the same business unit. Validate the passport renewal and revocation flows. Run the first cross-agent audit.

Weeks 9-10: Production criteria and scale plan. Codify production gates: every agent ships with a passport or it doesn't ship. Publish the agent library to the BU. Set the cadence for quarterly recertification and the budget envelope for the next 50 agents.

Success criteria at week 10: zero shadow agents in the pilot BU, 100% of production agents carry a valid passport, mean-time-to-pause under 5 minutes, full audit trail for every agent action, and a documented retirement playbook.

What to Do About It

For CIOs. Schedule the readiness scorecard for every business unit running agents in the next 30 days. Treat any BU scoring below 15 as a pause-and-fix situation. Build the vendor shortlist around your existing system-of-record gravity (ServiceNow, Microsoft, content-heavy verticals → Hyland). Demand that any pilot ship with a passport-equivalent or an explicit timeline to one. Make passport-readiness a precondition for next-year agent budget approval.

For CFOs. Add governance line items to the AI budget — Gartner's $492M market is funded by enterprises that learned the hard way that ungoverned agents are unbookable. Use the 5.8x McKinsey ROI as your underwriting baseline, and require the readiness score in every business case. Hold the six-month payback expectation tight for content/back-office automation (AP, claims), and longer for customer-facing agents where the regulatory load is heavier.

For Business Leaders. Read the passport schema. If you cannot explain in two sentences what your customer-facing agent is authorized to do, your agent is not ready for production — regardless of the demo. Sponsor the change management work: governance is a behavior change, not just a tool.

The 88% failure rate is not a model problem. It is a governance problem. The vendors that productize the answer first — Hyland on June 1, ServiceNow in May, Microsoft across May and June — are converging on the same conclusion: the agent that ships is the agent with a passport.


Continue Reading

THE DAILY BRIEF

Enterprise AI insights for technology and business leaders, twice weekly.

thedailybrief.com

Subscribe at thedailybrief.com/subscribe for weekly AI insights delivered to your inbox.

LinkedIn: linkedin.com/in/rberi  |  X: x.com/rajeshberi

© 2026 Rajesh Beri. All rights reserved.

Agent Passport: Why 88% of AI Agents Fail Before Production

Photo by Lukas on Pexels

Hyland just gave AI agents a passport. On June 1, the Cleveland-based content services giant shipped Enterprise Agent Mesh and Agent Lifecycle Management at general availability, anchored by a new construct called Agent Passport — a standardized, machine-enforceable certification every agent must carry before it touches production. The launch lands in the middle of an enterprise AI crisis with stark numbers: 88% of AI agent proofs of concept never reach production (IDC), 40% of agentic AI projects will be canceled by end of 2027 (Gartner), and only 14.4% of organizations deploy agents with full security and IT approval. The Agent Passport is Hyland's bet that the bottleneck is no longer model quality — it's governance the org chart can trust.

For CIOs and CFOs trying to justify the next AI budget cycle, this is the conversation that determines whether agentic AI delivers on a forecasted $206.5 billion software market in 2026 or becomes the next decommissioning line item.

What Changed: The Agent Passport Construct

Hyland unveiled four interlocking capabilities at CommunityLIVE 2026, described by CEO Jitesh S. Ghai as the move from "pilots to operationalization":

1. Agent Passport (new). A standardized certification that every agent must hold before running in production. It defines the agent's identity, capabilities, guardrails, and compliance status in a format that is both human-readable and machine-enforceable. Governance is applied before deployment, not bolted on after an incident.

2. Agent Library (new). A governed, searchable catalog of every agent in the enterprise — including ownership, function, and version history. The goal: stop the shadow-agent sprawl that Gartner has warned will undermine AI ROI through 2027.

3. Enterprise Agent Mesh (GA). A multi-agent network of use-case-specific agents tailored to healthcare, banking, insurance, government, and higher education — orchestrated under a single governance layer.

4. Control Tower (new). An operational command center for the Mesh that gives organizations real-time observability, KPI tracking, and the ability to pause or adjust agents based on metric thresholds, guardrail violations, or business impact — the "kill switch" enterprises have been demanding since the Gartner I&O ROI stall report in April.

Hyland also confirmed Headless Mode, which exposes the content and data fabric as APIs into Databricks, Snowflake, and custom workflows. This is the architectural signal: Hyland is positioning itself as governance plumbing, not a walled garden — a direct counter to the all-or-nothing platform pitches from larger vendors.

The Agent Passport concept echoes — and arguably formalizes — work from the broader standards community. Cubitrek published a 2026 specification describing Agent Passport as a single signed JSON document published at /.well-known/agent-passport.json on the organization's domain, declaring the agent's issuer, identity, scope of authority, spend ceiling, human-in-loop threshold, audit URL, compliance posture, and validity window. Signed Ed25519 with a public key in a DNS TXT record. The NIST AI Agent Standards Initiative is moving in the same direction. Hyland productized the concept first inside a commercial platform — which is what makes June 1 a turning point.

Why This Matters: The 88% Problem in Plain English

Two numbers explain the panic in the room: the Deloitte 89% pilot-to-production failure rate and the fact that only 14.4% of organizations ship agents with full security or IT approval. The gap is not technical capability — it's the absence of an enforceable handoff between "the model works in a demo" and "the agent has permission to act on a customer record."

Technical Implications (CTO / CIO)

Agent Passport changes the deployment contract. Today, most enterprises rely on point-in-time security reviews — a slide deck, a meeting, a sign-off. The Agent Passport approach makes the contract continuous and machine-readable: an agent without a valid passport literally cannot execute in the mesh. That maps directly onto the OpenTelemetry GenAI Semantic Conventions, which 89% of production observability users now consider "very important." If your agent stack already emits OTel spans (LangChain, CrewAI, AutoGen, AG2 all do natively), the passport becomes the policy companion to the telemetry you're already collecting.

For architecture teams, the integration question is not "do we adopt Hyland?" — it's "do we have an enforceable certification mechanism before our agent count crosses 50?" Most enterprises don't, and the absence is a leading indicator of the 88% failure rate.

Business Implications (CFO / CMO / COO)

Gartner now sizes the AI governance platform market at $492 million in 2026, surpassing $1 billion by 2030. That growth is funded by enterprises that have learned the hard way: an ungoverned agent that touches a customer or a financial system is a regulatory event waiting to happen. The Hyland announcement makes governance budget defensible: it ships with quantified outcomes — Agentic Hospital projects 5x faster referral assembly and 60% more efficient record intake; Agentic Accounts Payable projects 10x faster invoice cycles with 60% cost reduction per invoice and a six-month ROI window.

For CFOs underwriting agent spend, the math now has a control variable. For CMOs and COOs banking on customer-facing agents, the passport is the difference between a board-level incident and a quarterly KPI.

Market Context: The Governance Race Just Got Three-Way

Hyland is not alone in this market. The June launch reframes a competitive landscape that, six weeks ago, looked like a two-vendor race.

ServiceNow. At Knowledge 2026 in early May, ServiceNow extended AI Control Tower governance to Microsoft Agent 365, positioning its Control Tower as the cross-platform command center for first- and third-party agents. Control Tower is now bundled across every ServiceNow package — not an add-on. ServiceNow's edge: install base and workflow integration. Its weakness: it presumes you've standardized on ServiceNow as the system of record.

Microsoft Agent 365. Microsoft extended Entra, Defender, Purview, and Intune to govern AI agents across vendors — the governance control plane for Copilot Studio and Microsoft Foundry. Microsoft's edge: identity and endpoint coverage already in place at most Fortune 1000 shops. Its weakness: tightly coupled to the Microsoft agent runtime.

Hyland. Hyland's bet is different. Its Enterprise Context Engine couples agents to industry-specific ontologies — maps of entities, terminology, relationships, and rules for healthcare, insurance, financial services, education, and government. The Agent Passport is the certification layer that sits on top. Hyland's edge: vertical depth and content-aware context. Its weakness: smaller install base outside content services.

The analyst lens is sharpening. Forrester frames 2026 as the year of "ROI gatekeeping" — where governance becomes the precondition for budget. IDC frames it as the "agentic disruption" year — where unmanaged agent sprawl forces a governance reckoning. Gartner's harshest line: most agentic AI propositions lack significant value or ROI today, and over 40% will be canceled by end of 2027. All three converge on the same conclusion: governance is no longer optional infrastructure.

McKinsey's countervailing data: organizations that get to production are seeing an average 5.8x ROI within 14 months. The prize for solving the 88% problem is substantial. The penalty for ignoring it is the cancellation list.

Framework #1: Agent Passport Readiness Scorecard

Before you evaluate a vendor — or build governance in-house — score your organization across the five Agent Passport dimensions. Each scores 1-5; 25 points total.

The 5 Dimensions

1. Identity & Issuer (1-5). Does every agent have a verifiable, cryptographically signed identity tied to a named owner and business unit? Score 1 if agents run under shared service accounts. Score 5 if every agent has a unique signed identity with rotation policy and DNS-anchored or PKI-anchored verification.

2. Scope & Authority (1-5). Are the agent's tools, data access, and decision authority explicitly enumerated and machine-enforced at runtime? Score 1 if scope is documented in a wiki. Score 5 if scope is enforced by the runtime (the agent literally cannot exceed it).

3. Spend & Risk Ceilings (1-5). Are dollar ceilings (API spend, transaction value, refund authority) and risk ceilings (PII access, customer record writes) explicit and rate-limited? Score 1 if there are no ceilings. Score 5 if every passport carries hard caps with automated freeze on breach.

4. Human-in-the-Loop Thresholds (1-5). Are the conditions under which the agent must escalate to a human explicit, enforced, and audited? Score 1 if escalation is the agent's own judgment. Score 5 if thresholds are codified in the passport and observable through Control Tower telemetry.

5. Audit & Lifecycle (1-5). Is there a real-time audit trail, a defined validity window for the passport, a renewal process, and a documented retirement path? Score 1 if "we'll figure it out." Score 5 if every passport has issuance, renewal, revocation, and decommissioning logged automatically.

Scoring

Score Posture What to do
5-9 Not ready. You are in the 88% Stop scaling agents. Build the passport layer first or buy one.
10-14 Low maturity. Material risk Pause new agent deployments. Run a 12-week governance sprint.
15-19 Medium maturity. Manageable Standardize the passport schema across business units. Pilot Control Tower-class observability.
20-25 High maturity. You are in the 12% Focus on lifecycle automation and cross-vendor enforcement.

Take the test once for each business unit running agents. The variance across BUs is usually where the breach happens.

Framework #2: AI Agent Governance Platform Decision Matrix

The three commercial paths plus build-in-house, scored against the questions CIOs ask in vendor reviews.

Criterion Hyland Agent Mesh ServiceNow AI Control Tower Microsoft Agent 365 Build In-House
Time to first governed agent 6-10 weeks 4-8 weeks (if on ServiceNow) 4-6 weeks (if on M365 + Entra) 6-12 months
Cross-vendor agent governance Strong (Headless APIs into Databricks, Snowflake, third parties) Strong (added Microsoft Agent 365 governance May 2026) Moderate (best when M365 is the runtime) Depends on team
Industry vertical depth Strongest (healthcare, banking, insurance, gov, edu ontologies) Moderate (workflow templates) Weak (horizontal) None out of box
Agent Passport / certification primitive Productized "Discovery + risk score" model Identity-anchored (Entra) DIY
Observability standard Control Tower (proprietary + APIs) Bundled across packages Defender/Purview integration OTel preferred
Best fit for Content-heavy verticals, regulated industries Existing ServiceNow shops M365-standardized shops Hyperscalers, AI-native firms
Total annual cost (mid-market, 50-200 agents) $250K-$900K (platform + services) Bundled if on ServiceNow base Bundled if on M365 E5 $1.2M-$3M (engineering + ops)
Risk if wrong Lock-in to Hyland content fabric Lock-in to ServiceNow workflows Lock-in to Microsoft runtime Indefinite build, delayed ROI

How to read it. If your agents operate primarily on content and regulated workflows (claims, referrals, AP, underwriting), Hyland is the shortest path to a defensible production posture. If ServiceNow is already your system of record, the bundled Control Tower is hard to argue against. If your identity backbone is Entra and your agent runtime is Copilot Studio, Microsoft Agent 365 is the lowest-friction option. Build in-house only if you have a dedicated platform team and a multi-year horizon — the $1B+ governance market by 2030 exists because most enterprises came to that conclusion the hard way.

Real-World Example: The Agentic AP Case

Hyland's most concrete proof point is its Agentic Accounts Payable solution, projected to drive 10x faster invoice cycle times with a 60% reduction in cost per invoice and a six-month ROI window. Translate that into a Fortune 500 manufacturing comparison:

  • Baseline. 250,000 invoices/year. Average processing cost: $14/invoice. Annual cost: $3.5M. Average cycle: 12 days.
  • Post-deployment. Cost per invoice drops to $5.60 (60% reduction). Annual cost: $1.4M. Cycle compresses to ~1.2 days.
  • Annual savings: $2.1M. Platform + services (12-month): ~$650K. Payback: ~3.7 months — inside Hyland's six-month projection.

The lesson is not that the savings are unique to Hyland — they're attainable on multiple platforms. The lesson is that the savings are only bankable if the agents are governed enough to survive a controller's audit. Without a passport-equivalent, the same automation is one PII incident away from being shut down by Legal. That is exactly the failure mode behind the Gartner cancellation forecast.

For banking, the parallel proof point is Agentic Bank: applications to underwriter-ready status in days instead of weeks. The economic value is enormous; the governance prerequisite is the gating function.

Implementation Timeline: 10-Week Pilot to Production

Whether you choose Hyland, ServiceNow, Microsoft, or a hybrid, the rollout shape is similar.

Weeks 1-2: Inventory and scorecard. Run the 25-point readiness scorecard for each BU. Inventory existing agents (most enterprises discover 2-3x what they thought). Identify the top three governance gaps.

Weeks 3-4: Passport schema and policy. Define your passport schema: identity, scope, ceilings, HITL thresholds, audit. Align with legal, security, and finance. Pick one high-stakes use case for pilot (AP, claims, underwriting, clinical referral).

Weeks 5-6: Pilot deployment. Deploy one agent under full passport governance. Wire Control Tower-class observability (OTel spans, KPI dashboards). Set thresholds and verify the kill switch works in a real freeze drill.

Weeks 7-8: Expand to three agents. Add two more agents in the same business unit. Validate the passport renewal and revocation flows. Run the first cross-agent audit.

Weeks 9-10: Production criteria and scale plan. Codify production gates: every agent ships with a passport or it doesn't ship. Publish the agent library to the BU. Set the cadence for quarterly recertification and the budget envelope for the next 50 agents.

Success criteria at week 10: zero shadow agents in the pilot BU, 100% of production agents carry a valid passport, mean-time-to-pause under 5 minutes, full audit trail for every agent action, and a documented retirement playbook.

What to Do About It

For CIOs. Schedule the readiness scorecard for every business unit running agents in the next 30 days. Treat any BU scoring below 15 as a pause-and-fix situation. Build the vendor shortlist around your existing system-of-record gravity (ServiceNow, Microsoft, content-heavy verticals → Hyland). Demand that any pilot ship with a passport-equivalent or an explicit timeline to one. Make passport-readiness a precondition for next-year agent budget approval.

For CFOs. Add governance line items to the AI budget — Gartner's $492M market is funded by enterprises that learned the hard way that ungoverned agents are unbookable. Use the 5.8x McKinsey ROI as your underwriting baseline, and require the readiness score in every business case. Hold the six-month payback expectation tight for content/back-office automation (AP, claims), and longer for customer-facing agents where the regulatory load is heavier.

For Business Leaders. Read the passport schema. If you cannot explain in two sentences what your customer-facing agent is authorized to do, your agent is not ready for production — regardless of the demo. Sponsor the change management work: governance is a behavior change, not just a tool.

The 88% failure rate is not a model problem. It is a governance problem. The vendors that productize the answer first — Hyland on June 1, ServiceNow in May, Microsoft across May and June — are converging on the same conclusion: the agent that ships is the agent with a passport.


Continue Reading

Share:

THE DAILY BRIEF

AI Agent GovernanceHylandAgent PassportEnterprise Agent MeshCIO StrategyAI ComplianceAgent Lifecycle ManagementAI ObservabilityEnterprise AIProduction AI

Agent Passport: Why 88% of AI Agents Fail Before Production

Hyland's Agent Passport ships June 1 as 88% of AI POCs die before production. Compliance scorecard, vendor matrix, and 10-week rollout for CIOs.

By Rajesh Beri·June 2, 2026·13 min read

Hyland just gave AI agents a passport. On June 1, the Cleveland-based content services giant shipped Enterprise Agent Mesh and Agent Lifecycle Management at general availability, anchored by a new construct called Agent Passport — a standardized, machine-enforceable certification every agent must carry before it touches production. The launch lands in the middle of an enterprise AI crisis with stark numbers: 88% of AI agent proofs of concept never reach production (IDC), 40% of agentic AI projects will be canceled by end of 2027 (Gartner), and only 14.4% of organizations deploy agents with full security and IT approval. The Agent Passport is Hyland's bet that the bottleneck is no longer model quality — it's governance the org chart can trust.

For CIOs and CFOs trying to justify the next AI budget cycle, this is the conversation that determines whether agentic AI delivers on a forecasted $206.5 billion software market in 2026 or becomes the next decommissioning line item.

What Changed: The Agent Passport Construct

Hyland unveiled four interlocking capabilities at CommunityLIVE 2026, described by CEO Jitesh S. Ghai as the move from "pilots to operationalization":

1. Agent Passport (new). A standardized certification that every agent must hold before running in production. It defines the agent's identity, capabilities, guardrails, and compliance status in a format that is both human-readable and machine-enforceable. Governance is applied before deployment, not bolted on after an incident.

2. Agent Library (new). A governed, searchable catalog of every agent in the enterprise — including ownership, function, and version history. The goal: stop the shadow-agent sprawl that Gartner has warned will undermine AI ROI through 2027.

3. Enterprise Agent Mesh (GA). A multi-agent network of use-case-specific agents tailored to healthcare, banking, insurance, government, and higher education — orchestrated under a single governance layer.

4. Control Tower (new). An operational command center for the Mesh that gives organizations real-time observability, KPI tracking, and the ability to pause or adjust agents based on metric thresholds, guardrail violations, or business impact — the "kill switch" enterprises have been demanding since the Gartner I&O ROI stall report in April.

Hyland also confirmed Headless Mode, which exposes the content and data fabric as APIs into Databricks, Snowflake, and custom workflows. This is the architectural signal: Hyland is positioning itself as governance plumbing, not a walled garden — a direct counter to the all-or-nothing platform pitches from larger vendors.

The Agent Passport concept echoes — and arguably formalizes — work from the broader standards community. Cubitrek published a 2026 specification describing Agent Passport as a single signed JSON document published at /.well-known/agent-passport.json on the organization's domain, declaring the agent's issuer, identity, scope of authority, spend ceiling, human-in-loop threshold, audit URL, compliance posture, and validity window. Signed Ed25519 with a public key in a DNS TXT record. The NIST AI Agent Standards Initiative is moving in the same direction. Hyland productized the concept first inside a commercial platform — which is what makes June 1 a turning point.

Why This Matters: The 88% Problem in Plain English

Two numbers explain the panic in the room: the Deloitte 89% pilot-to-production failure rate and the fact that only 14.4% of organizations ship agents with full security or IT approval. The gap is not technical capability — it's the absence of an enforceable handoff between "the model works in a demo" and "the agent has permission to act on a customer record."

Technical Implications (CTO / CIO)

Agent Passport changes the deployment contract. Today, most enterprises rely on point-in-time security reviews — a slide deck, a meeting, a sign-off. The Agent Passport approach makes the contract continuous and machine-readable: an agent without a valid passport literally cannot execute in the mesh. That maps directly onto the OpenTelemetry GenAI Semantic Conventions, which 89% of production observability users now consider "very important." If your agent stack already emits OTel spans (LangChain, CrewAI, AutoGen, AG2 all do natively), the passport becomes the policy companion to the telemetry you're already collecting.

For architecture teams, the integration question is not "do we adopt Hyland?" — it's "do we have an enforceable certification mechanism before our agent count crosses 50?" Most enterprises don't, and the absence is a leading indicator of the 88% failure rate.

Business Implications (CFO / CMO / COO)

Gartner now sizes the AI governance platform market at $492 million in 2026, surpassing $1 billion by 2030. That growth is funded by enterprises that have learned the hard way: an ungoverned agent that touches a customer or a financial system is a regulatory event waiting to happen. The Hyland announcement makes governance budget defensible: it ships with quantified outcomes — Agentic Hospital projects 5x faster referral assembly and 60% more efficient record intake; Agentic Accounts Payable projects 10x faster invoice cycles with 60% cost reduction per invoice and a six-month ROI window.

For CFOs underwriting agent spend, the math now has a control variable. For CMOs and COOs banking on customer-facing agents, the passport is the difference between a board-level incident and a quarterly KPI.

Market Context: The Governance Race Just Got Three-Way

Hyland is not alone in this market. The June launch reframes a competitive landscape that, six weeks ago, looked like a two-vendor race.

ServiceNow. At Knowledge 2026 in early May, ServiceNow extended AI Control Tower governance to Microsoft Agent 365, positioning its Control Tower as the cross-platform command center for first- and third-party agents. Control Tower is now bundled across every ServiceNow package — not an add-on. ServiceNow's edge: install base and workflow integration. Its weakness: it presumes you've standardized on ServiceNow as the system of record.

Microsoft Agent 365. Microsoft extended Entra, Defender, Purview, and Intune to govern AI agents across vendors — the governance control plane for Copilot Studio and Microsoft Foundry. Microsoft's edge: identity and endpoint coverage already in place at most Fortune 1000 shops. Its weakness: tightly coupled to the Microsoft agent runtime.

Hyland. Hyland's bet is different. Its Enterprise Context Engine couples agents to industry-specific ontologies — maps of entities, terminology, relationships, and rules for healthcare, insurance, financial services, education, and government. The Agent Passport is the certification layer that sits on top. Hyland's edge: vertical depth and content-aware context. Its weakness: smaller install base outside content services.

The analyst lens is sharpening. Forrester frames 2026 as the year of "ROI gatekeeping" — where governance becomes the precondition for budget. IDC frames it as the "agentic disruption" year — where unmanaged agent sprawl forces a governance reckoning. Gartner's harshest line: most agentic AI propositions lack significant value or ROI today, and over 40% will be canceled by end of 2027. All three converge on the same conclusion: governance is no longer optional infrastructure.

McKinsey's countervailing data: organizations that get to production are seeing an average 5.8x ROI within 14 months. The prize for solving the 88% problem is substantial. The penalty for ignoring it is the cancellation list.

Framework #1: Agent Passport Readiness Scorecard

Before you evaluate a vendor — or build governance in-house — score your organization across the five Agent Passport dimensions. Each scores 1-5; 25 points total.

The 5 Dimensions

1. Identity & Issuer (1-5). Does every agent have a verifiable, cryptographically signed identity tied to a named owner and business unit? Score 1 if agents run under shared service accounts. Score 5 if every agent has a unique signed identity with rotation policy and DNS-anchored or PKI-anchored verification.

2. Scope & Authority (1-5). Are the agent's tools, data access, and decision authority explicitly enumerated and machine-enforced at runtime? Score 1 if scope is documented in a wiki. Score 5 if scope is enforced by the runtime (the agent literally cannot exceed it).

3. Spend & Risk Ceilings (1-5). Are dollar ceilings (API spend, transaction value, refund authority) and risk ceilings (PII access, customer record writes) explicit and rate-limited? Score 1 if there are no ceilings. Score 5 if every passport carries hard caps with automated freeze on breach.

4. Human-in-the-Loop Thresholds (1-5). Are the conditions under which the agent must escalate to a human explicit, enforced, and audited? Score 1 if escalation is the agent's own judgment. Score 5 if thresholds are codified in the passport and observable through Control Tower telemetry.

5. Audit & Lifecycle (1-5). Is there a real-time audit trail, a defined validity window for the passport, a renewal process, and a documented retirement path? Score 1 if "we'll figure it out." Score 5 if every passport has issuance, renewal, revocation, and decommissioning logged automatically.

Scoring

Score Posture What to do
5-9 Not ready. You are in the 88% Stop scaling agents. Build the passport layer first or buy one.
10-14 Low maturity. Material risk Pause new agent deployments. Run a 12-week governance sprint.
15-19 Medium maturity. Manageable Standardize the passport schema across business units. Pilot Control Tower-class observability.
20-25 High maturity. You are in the 12% Focus on lifecycle automation and cross-vendor enforcement.

Take the test once for each business unit running agents. The variance across BUs is usually where the breach happens.

Framework #2: AI Agent Governance Platform Decision Matrix

The three commercial paths plus build-in-house, scored against the questions CIOs ask in vendor reviews.

Criterion Hyland Agent Mesh ServiceNow AI Control Tower Microsoft Agent 365 Build In-House
Time to first governed agent 6-10 weeks 4-8 weeks (if on ServiceNow) 4-6 weeks (if on M365 + Entra) 6-12 months
Cross-vendor agent governance Strong (Headless APIs into Databricks, Snowflake, third parties) Strong (added Microsoft Agent 365 governance May 2026) Moderate (best when M365 is the runtime) Depends on team
Industry vertical depth Strongest (healthcare, banking, insurance, gov, edu ontologies) Moderate (workflow templates) Weak (horizontal) None out of box
Agent Passport / certification primitive Productized "Discovery + risk score" model Identity-anchored (Entra) DIY
Observability standard Control Tower (proprietary + APIs) Bundled across packages Defender/Purview integration OTel preferred
Best fit for Content-heavy verticals, regulated industries Existing ServiceNow shops M365-standardized shops Hyperscalers, AI-native firms
Total annual cost (mid-market, 50-200 agents) $250K-$900K (platform + services) Bundled if on ServiceNow base Bundled if on M365 E5 $1.2M-$3M (engineering + ops)
Risk if wrong Lock-in to Hyland content fabric Lock-in to ServiceNow workflows Lock-in to Microsoft runtime Indefinite build, delayed ROI

How to read it. If your agents operate primarily on content and regulated workflows (claims, referrals, AP, underwriting), Hyland is the shortest path to a defensible production posture. If ServiceNow is already your system of record, the bundled Control Tower is hard to argue against. If your identity backbone is Entra and your agent runtime is Copilot Studio, Microsoft Agent 365 is the lowest-friction option. Build in-house only if you have a dedicated platform team and a multi-year horizon — the $1B+ governance market by 2030 exists because most enterprises came to that conclusion the hard way.

Real-World Example: The Agentic AP Case

Hyland's most concrete proof point is its Agentic Accounts Payable solution, projected to drive 10x faster invoice cycle times with a 60% reduction in cost per invoice and a six-month ROI window. Translate that into a Fortune 500 manufacturing comparison:

  • Baseline. 250,000 invoices/year. Average processing cost: $14/invoice. Annual cost: $3.5M. Average cycle: 12 days.
  • Post-deployment. Cost per invoice drops to $5.60 (60% reduction). Annual cost: $1.4M. Cycle compresses to ~1.2 days.
  • Annual savings: $2.1M. Platform + services (12-month): ~$650K. Payback: ~3.7 months — inside Hyland's six-month projection.

The lesson is not that the savings are unique to Hyland — they're attainable on multiple platforms. The lesson is that the savings are only bankable if the agents are governed enough to survive a controller's audit. Without a passport-equivalent, the same automation is one PII incident away from being shut down by Legal. That is exactly the failure mode behind the Gartner cancellation forecast.

For banking, the parallel proof point is Agentic Bank: applications to underwriter-ready status in days instead of weeks. The economic value is enormous; the governance prerequisite is the gating function.

Implementation Timeline: 10-Week Pilot to Production

Whether you choose Hyland, ServiceNow, Microsoft, or a hybrid, the rollout shape is similar.

Weeks 1-2: Inventory and scorecard. Run the 25-point readiness scorecard for each BU. Inventory existing agents (most enterprises discover 2-3x what they thought). Identify the top three governance gaps.

Weeks 3-4: Passport schema and policy. Define your passport schema: identity, scope, ceilings, HITL thresholds, audit. Align with legal, security, and finance. Pick one high-stakes use case for pilot (AP, claims, underwriting, clinical referral).

Weeks 5-6: Pilot deployment. Deploy one agent under full passport governance. Wire Control Tower-class observability (OTel spans, KPI dashboards). Set thresholds and verify the kill switch works in a real freeze drill.

Weeks 7-8: Expand to three agents. Add two more agents in the same business unit. Validate the passport renewal and revocation flows. Run the first cross-agent audit.

Weeks 9-10: Production criteria and scale plan. Codify production gates: every agent ships with a passport or it doesn't ship. Publish the agent library to the BU. Set the cadence for quarterly recertification and the budget envelope for the next 50 agents.

Success criteria at week 10: zero shadow agents in the pilot BU, 100% of production agents carry a valid passport, mean-time-to-pause under 5 minutes, full audit trail for every agent action, and a documented retirement playbook.

What to Do About It

For CIOs. Schedule the readiness scorecard for every business unit running agents in the next 30 days. Treat any BU scoring below 15 as a pause-and-fix situation. Build the vendor shortlist around your existing system-of-record gravity (ServiceNow, Microsoft, content-heavy verticals → Hyland). Demand that any pilot ship with a passport-equivalent or an explicit timeline to one. Make passport-readiness a precondition for next-year agent budget approval.

For CFOs. Add governance line items to the AI budget — Gartner's $492M market is funded by enterprises that learned the hard way that ungoverned agents are unbookable. Use the 5.8x McKinsey ROI as your underwriting baseline, and require the readiness score in every business case. Hold the six-month payback expectation tight for content/back-office automation (AP, claims), and longer for customer-facing agents where the regulatory load is heavier.

For Business Leaders. Read the passport schema. If you cannot explain in two sentences what your customer-facing agent is authorized to do, your agent is not ready for production — regardless of the demo. Sponsor the change management work: governance is a behavior change, not just a tool.

The 88% failure rate is not a model problem. It is a governance problem. The vendors that productize the answer first — Hyland on June 1, ServiceNow in May, Microsoft across May and June — are converging on the same conclusion: the agent that ships is the agent with a passport.


Continue Reading

THE DAILY BRIEF

Enterprise AI insights for technology and business leaders, twice weekly.

thedailybrief.com

Subscribe at thedailybrief.com/subscribe for weekly AI insights delivered to your inbox.

LinkedIn: linkedin.com/in/rberi  |  X: x.com/rajeshberi

© 2026 Rajesh Beri. All rights reserved.

Newsletter

Stay Ahead of the Curve

Weekly enterprise AI insights for technology leaders. No spam, no vendor pitches—unsubscribe anytime.

Subscribe