For the first time, the UN has declared that exceeding the Paris Agreement's 1.5C warming limit is "imminent and unavoidable." "We are now saying this window has closed, but we can open it again by making the overshoot as brief as possible," UN Environment Program Executive Director Inger Andersen said on a call with reporters. "This is about how to find a way back as shortly and as quickly as possible with as limited an overshoot as possible." CNN reports: Past reports have examined the distance between countries' emissions reduction commitments and what it would take to limit global warming to 1.5 C above preindustrial levels. However, this year's report redefines the gap. Instead, it examines new emissions overshoot scenarios, and what it would take to limit peak warming to just 1.7 to 1.8 degrees C before bringing temperatures back down to 1.5 C through emissions cuts and the use of carbon removal technologies.
The report makes clear that every additional fraction of a degree of warming above 1.5 C "raises the risk of irreversible changes including in ice sheets, permafrost carbon, ocean circulation, and coral systems, along with devastating human impacts." Each added fraction of a degree of warming can have an "immense" impact "as measured in terms of damage, cost and loss of lives," said climate scientist Michael Mann of the University of Pennsylvania. Mann was not involved in producing the UNEP report.
According to the UNEP, which is based in Nairobi, the lowest overshoot scenario would keep peak warming to between 1.7 and 1.8 degrees C and return global average temperatures to at or below 1.5 C by 2100. However, to follow such a pathway, global greenhouse gas emissions would need to be slashed by far more than anything currently on the table at the upcoming COP31 talks. This would require an 18% cut by 2030, 45% by 2035, and 69% by 2040, relative to 2025 levels.
Meeting this lowest-possible overshoot scenario would require a tripling of renewable electricity capacity by 2035, and dramatic cuts to fossil fuels, including the phaseout of coal by 2040, the report states. In addition, there would need to be a major scaling up of carbon removal technologies, which so far have not been proven to work at such a large scale. In stark contrast to these figures, the fulfillment of existing emissions reduction pledges would only yield a 5-to-8% emissions cut by 2030 and an 11-to-15% reduction by 2035, the report found. This would be associated with a peak warming of about 2.6 degrees C.
If countries simply follow their current policies, then warming could reach a peak of about 2.8 C. That estimate has increased since last year, in part because of the withdrawal of the United States from the Paris Agreement and retraction of its emissions reduction commitments, the report states. Even the scenario that assumes countries meet their existing reduction commitments, and nations with net-zero pledges succeed in fulfilling them, still brings warming to a peak of 2.1 C.
Who gets to shape a future that will impact us all, and what happens when the voices we need most are missing from the room?
In this episode, Toni Townes-Whitley joins the WIT Podcast for a wide-ranging conversation about leadership, technology, and the responsibility that comes with having a seat at the table. She explores the growing intersection of technology and civic life, the need for greater accountability as AI outpaces policy, and why women must be part of shaping what comes next. Toni also reflects on resilience, building a career beyond titles, and what it means to get in the room, stay in the room, and ultimately open it for others.
This week, we discuss sovereign cloud, Postgres conference takeaways, CoreWeave's debt, and why AI is a single-player game. Plus, whether home automation is worth it.
Hey everyone, and welcome back to The Modern .NET Show; the premier .NET podcast, focusing entirely on the knowledge, tools, and frameworks that all .NET developers should have in their toolbox. I'm your host Jamie Taylor, bringing you conversations with the brightest minds in the .NET ecosystem.
Today's episode is a little different from the norm. There's no guest; it's just me. And there's a date coming that I'd rather tell you about early than late.
So let's sit back, open up a terminal, type in `dotnet new podcast` and we'll dive into the core of Modern .NET.
Remember to rate and review the show on Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend.
And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch.
When software engineers build enterprise AI assistants, connecting an agent to static PDF manuals is only half the battle. Real business decisions happen inside live Outlook email threads, Microsoft Teams chats, calendar meetings, SharePoint documents, and Dynamics 365 workflows.
Previously, giving an AI agent secure access to this daily collaboration data required stitching together dozens of Microsoft Graph endpoints and managing complex OAuth scopes. Microsoft eliminates this plumbing with Microsoft Work IQ, a production-ready workplace intelligence layer. In this technical deep dive, we explore what Work IQ is, how its four core pillars operate, and how developers integrate it using MCP, A2A, and REST APIs.
Microsoft Work IQ: Powering workplace context, SharePoint Embedded agent workspaces, compact MCP tools, and A2A collaboration across Microsoft 365.
Workplace Intelligence Layer: Work IQ continuously builds a live semantic understanding across Microsoft 365 (Outlook, Teams, SharePoint, OneDrive, Planner), Dynamics 365, and Power Platform.
Four Integrated Pillars: Combines conversational Chat memory, zero-orchestration Context grounding, composable Tools, and persistent SharePoint Embedded Workspaces.
Compact MCP Tool Surface: Collapses hundreds of Microsoft 365 API operations into generic verb tools (such as fetch, create_entity, do_action, ask, retrieve, and get_schema) with runtime schema discovery.
Multi-Protocol Flexibility: Supports JSON-RPC 2.0 Agent-to-Agent (A2A v1.0) delegation, Local and Remote MCP servers, a conversational REST API, and the Microsoft Work IQ CLI.
Rego Policy & Delegated Security: Enforces user-scoped Microsoft Entra ID delegated authentication and evaluates every request through a centralized Rego-based policy engine.
What Is Microsoft Work IQ
Microsoft Work IQ is the contextual workplace intelligence layer of the Microsoft IQ stack that enables AI agents to access, reason over, and act on live organizational data and tools. While Microsoft Foundry IQ manages multi-source enterprise knowledge bases on Azure AI Search, Work IQ focuses on how people work and collaborate across Microsoft 365, Dynamics 365, and Power Platform.
Instead of exposing raw data endpoints like traditional Microsoft Graph APIs, Work IQ continuously builds a semantic understanding of organizational relationships, active projects, meetings, and communication habits. It combines conversational memory, pre-grounded workplace context, executable tools, and persistent storage into a single permission-aware platform.
Crucially, Work IQ API access operates independently of standard Microsoft 365 Copilot seat licenses. Organizations can enable usage-based billing through Copilot Credits in the Microsoft 365 admin center, allowing custom agents and third-party applications to tap into workplace intelligence on demand.
The Four Core Pillars: Chat, Context, Tools, and Workspaces
The Work IQ architecture rests on four integrated capabilities: Chat, Context, Tools, and Workspaces. The Chat pillar provides conversational intelligence backed by auditable Conversational Memory—retaining Session Memory for active chats, Persistent Memory for user work styles, and Process-Tied Memory for long-running projects.
The Context pillar removes retrieval orchestration overhead from your application code. Work IQ automatically assembles and grounds signals across Outlook mail, Teams channels, OneDrive files, Planner boards, and Dynamics 365 records so agents receive ready-to-reason context without maintaining separate vector databases.
For multistep, long-running workflows, the Workspaces pillar gives agents a dedicated persistent storage area powered by SharePoint Embedded inside your Microsoft 365 tenant boundary. Agents store intermediate research drafts, track task progression, and hand off work artifacts to human teammates or downstream agents without leaking data outside the tenant.
Inside the Work IQ MCP Server and Runtime Schema Introspection
When developers wire traditional APIs into Model Context Protocol (MCP) clients, exposing hundreds of individual endpoints quickly overflows the model's context window and degrades tool-selection accuracy. The Work IQ MCP server solves this problem using three core design principles: fewer tools with more paths, runtime introspection over static enumeration, and policy over scopes.
Work IQ collapses hundreds of Microsoft 365 operations into a compact surface of generic verb tools grouped into three categories: Entity tools (fetch, fetch_blob, create_entity, update_entity, delete_entity, do_action, and call_function), Copilot tools (ask, retrieve, and list_agents), and Schema tools (get_schema and search_paths).
Instead of pre-loading thousands of static OpenAPI definitions into the prompt, an agent calls search_paths and get_schema at runtime to inspect the exact data structure it needs. The agent then pairs a simple verb with a relative resource path—such as fetch /me/messages to read emails or do_action /me/sendMail to dispatch a reply—keeping token consumption minimal.
Integrating via Agent-to-Agent (A2A), REST APIs, and Work IQ CLI
As documented in the Work IQ API overview, developers integrate Work IQ using three standard protocols tailored to different application patterns. When building autonomous multi-agent systems that delegate tasks to one another, teams use the Agent-to-Agent (A2A) protocol over JSON-RPC 2.0 at the workiq.svc.cloud.microsoft/a2a endpoint.
By passing the A2A-Version 1.0 header and a persistent contextId, an operations agent can ask Work IQ to investigate a project delay across Teams and Outlook while maintaining multi-turn state. For traditional web backends and custom orchestrators, the Work IQ REST API offers direct request-response conversational access.
Delegated Entra Authentication and Rego Policy Governance
In our enterprise architecture audits across Kolkata and Bengaluru, security teams consistently reject AI tools that use broad, unattended application-only permissions. Work IQ addresses this concern by requiring Microsoft Entra ID delegated authentication and supporting On-Behalf-Of (OBO) flows, while blocking unattended application-only tokens.
Every Work IQ request executes strictly within the signed-in user's identity context. Rather than managing hundreds of brittle OAuth scopes, Work IQ uses four high-level boundary permissions backed by a centralized, Rego-based policy engine.
On every single tool invocation, the Rego policy engine evaluates the resource path, request method, user identity, and Microsoft Purview sensitivity labels in real time. Every action is logged for admin auditability and rate limiting, giving enterprises complete confidence as they scale from generative assistants to autonomous agentic workflows.
Architectural Comparison of Work IQ Integration Protocols
MULTI-AGENT DELEGATION
Agent-to-Agent (A2A)
Primary Caller: Autonomous peer or orchestrator agents.
Transport & Format: JSON-RPC 2.0 POST with A2A-Version 1.0 header.
State Management: Multi-turn task tracking via persistent contextId.
Best Scenario: Delegating complex workplace investigations across agents.
TOOL-BASED ACCESS
Local & Remote MCP
Primary Caller: IDEs, GitHub Copilot CLI, and LLM tool hosts.
Transport & Format: Standard Model Context Protocol (stdio or remote HTTP).
State Management: Dynamic runtime schema introspection (get_schema).
Best Scenario: Invoking M365 CRUD actions and grounding inside coding tools.
DIRECT APPLICATION API
Work IQ REST API
Primary Caller: Custom web applications and backend microservices.
Transport & Format: Standard HTTPS request/response conversational endpoints.
State Management: Programmatic session start and continuation.
Best Scenario: Embedding Copilot-grade workplace chat in custom portals.
Frequently Asked Questions (FAQ)
What is Microsoft Work IQ?
Microsoft Work IQ is the workplace intelligence layer of the Microsoft IQ stack that enables AI agents and applications to securely access, reason over, and act on organizational data, context, and tools across Microsoft 365, Dynamics 365, and Power Platform.
What are the four core architectural pillars of Work IQ?
Work IQ is built on four pillars: Chat (conversational intelligence and memory), Context (pre-grounded workplace and business signals), Tools (compact verb-based actions across M365), and Workspaces (persistent SharePoint Embedded storage for long-running agent tasks).
How does Work IQ differ from Microsoft Foundry IQ?
Work IQ focuses on user-specific workplace collaboration signals, emails, Teams chats, meetings, and M365 actions, whereas Foundry IQ manages multi-source enterprise knowledge bases and agentic retrieval on Azure AI Search.
How does the Work IQ MCP server prevent context window bloat?
Instead of exposing hundreds of separate API tools, Work IQ MCP collapses Microsoft 365 operations into a small set of generic verb tools (such as fetch, create_entity, do_action, ask, retrieve, and get_schema) that operate on relative resource paths and discover schemas dynamically at runtime.
Which communication protocols does the Work IQ API support?
Work IQ supports the Agent-to-Agent (A2A v1.0 and v0.3) protocol over JSON-RPC 2.0, Local and Remote Model Context Protocol (MCP) servers, and a conversational REST API.
What are Workspaces in Microsoft Work IQ?
Workspaces provide persistent working storage powered by SharePoint Embedded inside your Microsoft 365 tenant boundary, allowing long-running agents to save intermediate outputs and hand off work across multi-agent workflows.
Does Work IQ support unattended application-only authentication?
No. Work IQ requires Microsoft Entra ID delegated authentication (including On-Behalf-Of flows) so that every request executes strictly under a signed-in user's identity and respects their exact access permissions.
How does Work IQ enforce fine-grained security policies?
Work IQ combines four broad OAuth boundary permissions with a centralized Rego-based policy engine that evaluates resource paths, request methods, user identity, and Microsoft Purview sensitivity labels on every tool invocation.
Do users need a Microsoft 365 Copilot license to use custom Work IQ agents?
No. Work IQ API usage is independent of Microsoft 365 Copilot seat licensing and is available through usage-based billing using Copilot Credits managed in the Microsoft 365 admin center.
How do developers fix a 400 AuthenticationError in multitenant organizations?
In multitenant setups, the access token issuer (iss) must match the signed-in user's home tenant. Developers must register the application as multitenant (AzureADMultipleOrgs) and authenticate users through their home tenant authority.
End Note
Microsoft Work IQ transforms Microsoft 365 from a collection of productivity apps into an intelligent, self-describing execution environment for AI agents. By combining auditable conversational memory, SharePoint Embedded workspaces, a compact verb-based MCP surface, and Rego policy governance, it removes the integration friction that previously stalled workplace AI.
## 1 Introduction and the Paradigm Shift in Agentic Testing
A customer asks a support agent to refund a damaged order. The agent finds the order, checks the policy, calls the payment service, and replies, “Your refund is complete.” The answer reads well. But did the service accept the refund? Was it the right order? Did a retry issue the payment twice?
Testing AI agents before production means answering those questions with evidence. An agent's quality depends on its decisions, the tools it executes, the state it changes, and what it tells the user afterward. Evaluating the final response alone leaves most of that behavior untested.
The running example is a customer-support refund agent. Separating model decisions from tool execution lets software tests, live LLM evaluations, and failure simulations exercise the same application boundaries.
### 1.1 Why Traditional Unit and Integration Tests Fail for AI Agents
Traditional tests remain essential. They fail as a complete strategy when they assume that validating each component proves the workflow behaves correctly.
Log in
