Microsoft's Work IQ APIs mark an important step towards AI-First: a working model where agents can understand context, act across system boundaries and use information from both Microsoft 365 and Dynamics 365.

For anyone investing in Dynamics 365, the question is therefore not just which features exist, but whether the solution has been developed for people, agents, and new ways of performing work.

What is Work IQ?

Work IQ is an intelligence layer in Microsoft 365 that continuously builds up a semantic understanding of how work actually gets done in your organisation.

This layer:

  • connects signals from Microsoft 365
  • creates context across systems and people
  • makes context available to AI agents via API

What changes with AI-First?

Traditionally:

  • users work in systems
  • processes are manual
  • the system reacts to input

With Work IQ:

  • agents can act in systems
  • decisions are based on context from across the organisation
  • work can be carried out with minimal manual handling (depending on governance)

This is what Microsoft means by AI-First: not AI as an individual feature, but AI as a new working model.

The link to Dynamics 365

Work IQ makes it possible to combine:

  • customer data from Dynamics 365
  • communication from Outlook
  • collaboration in Teams

Example: An agent can read customer history in Dynamics 365, analyse email threads, identify the right internal contact, and progress a case. This is the infrastructure currently being established.

What it means for you when investing in Dynamics 365

If you are planning to invest in Dynamics 365, you should evaluate:

  • Whether the solution is designed for agents, not just users
  • Whether the partner has expertise in Work IQ and Copilot
  • How data governance and control are handled
  • How M365 and D365 are connected
  • How Copilot Credits impact the overall cost structure

Summary

Recommendation: Choose a partner who already thinks in terms of agents, not just users.

Work IQ vs traditional Dynamics 365 implementation

The difference between Work IQ and traditional implementation is not about technology, but about how work is actually carried out.

Area Traditional Work IQ
Focus The user in the system The agent in the workflow
Process Manual Context-driven
Data Dynamics 365 D365 + M365
AI role Add-on Built into the flow
Design System-centric Agent-centric

In-depth comparison

Design: Traditional focuses on forms, views, and roles. Work IQ focuses on flows, decisions, and automation.

Work: Traditionally, the user searches, analyses, and acts themselves. With Work IQ, an agent can retrieve context, analyse, and suggest the next step.

Cost: Traditionally, licensing and implementation dominate. With Work IQ, Copilot Credits and consumption-based AI also need to be factored in.

Risk: Traditionally, risk often revolves around low adoption and complex user interfaces. With Work IQ, risk shifts towards incorrect automation and weak governance.

Key insight: The system goes from supporting work to being increasingly capable of executing work.

Checklist: Is your organisation ready for Work IQ?

How to calculate your score: Choose one answer for each area. Yes = 0 points, Partly = 1 point, No = 2 points. Sum the points for all eight areas. The lower the total score, the better prepared you are for Work IQ and AI in Dynamics 365.

Area What needs to be in place? Yes Partly No
1. Data Quality Customer data, history and duplicates are under control ☐ ☐ ☐
2. M365 Maturity Outlook, Teams and shared ways of working are used consistently ☐ ☐ ☐
3. Process Maturity Processes, decision rules and responsibilities are clear ☐ ☐ ☐
4. Governance AI policy, permissions and agent behaviour are controlled ☐ ☐ ☐
5. Technology Dynamics 365 environment and integrations are stable ☐ ☐ ☐
6. Commercials Copilot Credits, AI consumption and ROI are factored in ☐ ☐ ☐
7. Organisation Leadership and change management are in place ☐ ☐ ☐
8. Partner The partner has AI competence and governance experience ☐ ☐ ☐

Quick interpretation

  • 0–4 points, Relatively ready. Proceed with prioritised pilots.
  • 5–10 points, Partially ready. Start with a pilot and action plan.
  • 11–16 points, Not ready to scale. Strengthen foundational capabilities first.

Conclusion: Organisations that succeed best start with data quality, process maturity, and governance before scaling Dynamics 365 and AI.