Better decisions. Faster work. One trusted context. The agentic enterprise runs on context. A reference architecture for the agentic enterprise.
Agents help people move from question to action with less friction. The business advantage comes from giving every human and digital colleague the same trusted understanding. Agents can reason, plan, and act. But they only create enterprise value when they understand your language, your data, your rules, and the situation now. Dependable agents require a coordinated runtime, governed tools, observable data products, semantic retrieval, policy enforcement, and evidence. The modern data platform anchors the context plane.
The agentic enterprise lets people delegate well-defined work to digital colleagues—without giving up human ownership, control, or accountability. An agentic enterprise is an organization where people delegate bounded goals to software agents that can interpret context, use tools, coordinate work, and act—inside explicit authority, evidence, and oversight. The architecture separates model reasoning from enterprise truth. Context is assembled at request time from identity, task state, semantic data, retrieval policy, permissions, evidence, and tool contracts.
“Which customers need attention before renewal—and what should we do next?”
What changes for the business?
The goal is not “more AI.” It is an enterprise that can move from intent to dependable action with less delay, less duplication, and clearer accountability.
The group’s combined capabilities turn fragmented information and isolated tools into a shared operating advantage.
People and agents work from the same definitions, current facts, and visible evidence.
Routine coordination moves across systems without waiting for every manual handoff.
Data, meaning, integrations, and controls are built for reuse instead of rebuilt for every assistant.
More work can be delegated while people retain ownership of policy, exceptions, and consequential decisions.
Every curated data product, semantic definition, and safe action becomes useful to the next workflow too.
Individual agents and models will change. The group creates lasting value by making enterprise knowledge, data, permissions, and actions dependable and reusable across them.
Context is the product agents consume.
A model knows patterns. An enterprise context layer knows what is true here: which definition applies, how fresh the data is, who is asking, what they may do, and where the answer came from.
The model is replaceable. Enterprise context compounds.
Models, interfaces, and individual agents will change. Curated data, shared semantics, quality controls, policy, lineage, and feedback become more valuable as more humans and agents reuse them.
The enabling stack is wider than AI.
The agent is the visible part. The dependable capability is a coordinated stack in which each layer provides a clear contract to the next—and the modern data platform turns enterprise data into reusable context.
- Human edgeWork surfaces & channels
- ComponentsMicrosoft 365, analytics apps, custom applications, chat, search, notifications.PurposeCaptures intent and returns work where people already operate.
- DelegationAgents & automation
- ComponentsMicrosoft 365 agents, custom agents, workflow automation, human checkpoints.PurposeInterprets goals, plans tasks, coordinates tools, and manages state.
- ReasoningAI runtime & orchestration
- ComponentsModels and inference, routing, retrieval, memory, tool calling, evaluations, cost controls.PurposeChooses how to reason and which bounded capability to invoke.
- Shared contextModern data platform
- ComponentsWarehouses and lakehouses, pipelines, curated data products, semantic layers, catalogs, lineage, quality and freshness monitoring.PurposePublishes trusted meaning and state through governed, observable interfaces that humans, analytics, and agents can reuse.
- ExecutionSystems of record & action
- ComponentsCRM, ERP, line-of-business systems, files, operational stores, APIs, event streams.PurposeHolds operational truth and performs controlled changes in the business.
- FoundationInfrastructure & platforms
- ComponentsCloud and data centers, networks, identity, endpoint management, Microsoft licensing.PurposeProvides resilient compute, access, connectivity, sovereignty, and commercial entitlement.
Without a shared context foundation
- Each agent rebuilds point-to-point integrations.
- Definitions drift between analytics, workflows, and assistants.
- Quality failures are discovered inside an answer.
- Permissions and business rules are copied into prompts and code.
- Evidence is difficult to reconstruct after an action.
With a modern data platform
- Curated data products serve many human and agent experiences.
- A semantic layer keeps business meaning consistent.
- Quality, freshness, and lineage travel with the context.
- Governed interfaces reduce bespoke access paths.
- Outcomes feed back into monitoring and improvement.
One group. One system. Different responsibilities.
No single company owns the whole agentic enterprise. The advantage appears when the group’s capabilities exchange context through clear contracts. Select a capability to see what it contributes and what it needs.
Shared meaning, trusted state, authority, and evidence. The modern data platform curates and serves its reusable data foundation.
Coordinated—not centralized ownershipThe data company holds a crucial coordinating role because trusted data and shared semantics are reused everywhere. But enterprise context is co-produced: workplace services provide situation, Microsoft provides identity and entitlement, infrastructure provides the runtime, developers provide actions, domain owners provide meaning, and agents return evidence and feedback.
Autonomy changes the control points—not the need for context.
Whether an agent drafts, recommends, or acts, the enterprise still needs the same operating loop. More autonomy raises the bar for explicit authority, evidence, monitoring, and recovery.
The human directs the task and uses the agent to find, summarize, draft, or analyze.
Context improves relevance and consistency; the human remains the action boundary.
The agent plans and executes multiple steps, pausing at named checkpoints.
Context must include policy, intermediate state, tool contracts, and inspectable evidence.
The agent operates within a bounded goal, authority, budget, and escalation path.
Context must stay fresh and observable; controls, recovery, and feedback become part of the product.
Design context as a product.
The technical objective is a context supply chain: assemble the smallest authorized set of meaning, data, state, evidence, and tools for the task—then observe what the agent actually did with it.
Resolve the user, role, goal, workflow, risk tier, and current case.
Identity + task stateSelect domains, time boundaries, policy, memory, and permitted sources.
Context policyQuery semantic data and knowledge, rerank evidence, and expose uncertainty.
Retrieval + semanticsChoose steps and tools, validate parameters, and place approval gates.
Orchestration + policyInvoke bounded, idempotent operations with explicit side effects and recovery.
Tool contractsCapture sources, tool calls, outcome, latency, cost, correction, and drift.
Evidence + evaluationMake the interfaces explicit
Agents scale when the important assumptions stop living inside prompts. Each reusable capability needs a contract that both software and owners can inspect.
Data product contract
Defines what a governed dataset means, who owns it, when it is fit for use, and how consumers can discover and access it.
Context contract
Defines how identity, task, time, retrieval scope, semantic definitions, evidence, and uncertainty are assembled for a request.
Tool & action contract
Defines a bounded operation the agent may invoke, including permissions, validation, side effects, failure behavior, and audit evidence.
Evaluation contract
Defines what good means before release and in operation, from data health and retrieval relevance to action safety and business outcome.
Observe the whole chain
A correct model response can still produce a poor enterprise outcome. Monitoring must connect the data, retrieval, reasoning, tool, and business layers.
| Layer | What to observe | Typical failure | Primary response |
|---|---|---|---|
| Data | Completeness, validity, freshness, distribution, lineage | Stale or contradictory facts | Stop or degrade the affected data product; route to its owner |
| Retrieval | Coverage, relevance, authorization, source diversity | Relevant evidence is missed or unauthorized evidence is exposed | Adjust retrieval policy, indexing, ranking, or permissions |
| Reasoning | Instruction adherence, groundedness, uncertainty, model drift | A fluent conclusion outruns the available evidence | Constrain the task, require evidence, change model or review gate |
| Tools | Validation, authorization, side effects, retries, recovery | An action is duplicated, partially completed, or cannot be reversed | Harden the tool contract and escalation path |
| Outcome | Human acceptance, correction, cycle time, risk, value | The workflow works technically but does not improve the business | Change the workflow, context, ownership, or stop the use case |
Architecture traps to avoid
- Embedding business definitions and permissions inside prompts that no owner governs.
- Letting every agent create its own source integrations and private memory.
- Measuring model quality without testing retrieval, tools, and business outcomes.
- Using vector search as a substitute for curated data products and a semantic layer.
- Granting broad system access instead of exposing bounded, observable actions.
Invest in a reusable operating capability.
A portfolio of isolated copilots repeats integration, governance, and quality work. The strategic move is to fund valuable workflows and the shared context capabilities they can reuse.
Start with a consequential decision
Choose a workflow where better context changes speed, quality, risk, or customer outcome. Define the human owner and the action boundary before selecting an agent.
Build the minimum reusable context
Curate the data, definitions, quality signals, identity, policy, and evidence needed for that decision. Publish them as contracts, not as logic trapped inside one assistant.
Deliver one end-to-end slice
Connect the work surface, agent, model runtime, context, and action system. Test the entire loop with real users and explicit human checkpoints.
Scale what became shared
Reuse data products, semantic models, tools, controls, and evaluations across the next workflows. Let usage and outcomes guide platform investment.
Questions for the investment committee
Build the context once. Improve every decision that uses it.
The modern data platform becomes central because every useful agent eventually needs dependable answers to four enterprise questions:
- What is true?
- What does it mean?
- What am I allowed to do?
- Can I prove what happened?
The data platform anchors truth, meaning, quality, and lineage. The wider group completes the picture with identity, work surfaces, models, infrastructure, tools, and human ownership.