Microsoft had plenty of news at Ignite, with much of it focused on operationalizing AI:
• Copilot and agents: How people and agents work together
• Agent 365 and security: Agent identities, permissions, security, and the watchword of the year, spending
• Microsoft IQ: Managing/connecting business knowledge and context across agents and applications
• Data and AI infrastructure: HorizonDB, Fabric, and other services bringing operational data, analytics, and AI closer together
What caught my attention was Microsoft IQ.
Multiple keynote speakers drove home the point that “context is your IP.” It's an asset enterprises need to actively manage and build on. More on that in a future post.
The IQ family was introduced previously. What's new is Microsoft's move to manage and reuse context across agents through business plugins and an open architecture that can incorporate knowledge from other systems, including process intelligence from Celonis.
That's important because context is already one of the harder problems in enterprise AI, and even how we define and manage it is still evolving.
Five implications stand out:
1. Context conflicts need resolution. Different systems and domains may have conflicting definitions, rules, or views of the business. Enterprises need to establish which sources are authoritative for a given decision and how conflicts get resolved.
2. Shared context becomes operational infrastructure. When multiple agents depend on the same context, its accuracy, freshness, and availability become critical. One bad definition can affect multiple workflows.
3. Domain ownership still matters. Sales, finance, and supply chain have different definitions, processes, and rules. The teams that understand those domains need to own their context.
4. Federation matters. Enterprises need to bring context from different domains and systems together without rebuilding everything in one global model. Microsoft's open approach is a step in that direction.
5. Trusted execution requires more. Agents need current operational state, business policies, and authority to act. Understanding the business doesn't automatically mean an agent can safely execute a decision.
What should CIOs and CDAOs do next?
Start with a process where multiple agents need the same context. Determine what can be shared, who owns it, and which systems remain authoritative.
Then measure whether reuse actually reduces development effort and improves decision consistency, while testing the controls needed to execute reliably.
Microsoft is making progress. The test is whether shared context can support real business decisions and actions across the enterprise.
Read more
• Larry Dignan coverage: https://buff.ly/fRcNNHD
• Microsoft’s IQ introduction: https://buff.ly/ywkF34k