Copilot Studio or Microsoft Foundry?

Copilot Studio for business agents that live inside Microsoft 365 and Dynamics workflows; Foundry when you are building a custom application with its own interface and lifecycle. Most estates end up using both, and the split should be deliberate.

Does agent governance need extra licensing now?

Microsoft has moved agent-security capabilities for Copilot Studio and Foundry agents behind Microsoft Agent 365 licensing as of 1 July 2026. We review your entitlements against your intended deployment before you commit — as your reseller, we can also quote the difference.

Can Microsoft agents act on Coupa data?

Yes. DataMap Connect is the certified Coupa ↔ Dynamics 365 accelerator, so the procurement context an agent needs is already synchronized rather than scraped.

Platform AI

Copilot Studio, Foundry, and Dynamics 365 agents — built and licensed by one partner

DataMap is a full Microsoft reseller: every Microsoft product and Azure consumption, alongside the certified Coupa ↔ Dynamics 365 connectors we build ourselves. That means the agent architecture, the ERP data it runs on, and the licensing all come from the same team.

Talk to a Microsoft AI architect

AI for Microsoft

Three places to build an agent, and the choice matters

Copilot Studio is where most business agents belong. Microsoft Foundry — renamed from Azure AI Foundry and formalized in January 2026 — is the developer platform for custom applications. Dynamics 365's own agents sit inside finance and supply chain. Picking wrong is expensive in licensing before it is expensive in engineering.

Copilot Studio

Business agents where the governance already lives

Agents built in Copilot Studio, with multi-agent orchestration, evaluations, and the governance controls Microsoft has layered on — connected to Foundry models and organizational data.

Multi-agent orchestration and evaluations
Connected to Foundry models and Work IQ
Governed inside your existing tenant

A formal contract being signed on a wooden desk

Foundry & Fabric

Custom applications on governed data

Where a business agent isn't enough, custom AI applications on Microsoft Foundry, grounded in governed Fabric data rather than in a copy of it — the same Azure Data Lake and Fabric layer we already build for spend intelligence.

Custom agents and applications on Foundry
Grounded in governed Fabric data
Azure Data Lake spend intelligence

A desk laid out with a laptop, order paperwork and cartons

Dynamics 365

Agents with real ERP context

Dynamics 365's first-party agents in finance and supply chain, plus our own agents that span D365 and Coupa — because DataMap Connect already keeps requisitions, POs, invoices, and supplier records in sync between them.

D365 finance and supply-chain agents
Coupa ↔ D365 context via DataMap Connect
Approvals routed through Teams

Invoices being reviewed in an open folder

Also included

Microsoft and Azure licensing through DataMap
Agent security and licensing entitlement review
Power Platform automation

Talk to a Microsoft AI architect

Proof

What it looks like in practice

All case studies

40–60% faster requisition-to-PO cycles
Near-zero month-end reconciliation

Whitepaper · Cross-industryApr 15, 2026

Coupa + DataMap + Microsoft: A Unified Spend Intelligence Stack

How DataMap's integration layer connects Coupa's procurement engine with Microsoft's data platform to deliver a single, AI-ready spend intelligence stack across the enterprise.

Read

Coupa integrated with Microsoft Dynamics 365 via DataMap Connect
Procurement and AP processes optimized on Coupa

Case Study · HOPCoJun 18, 2025

HOPCo: Optimizing Procurement and AP with Coupa and Microsoft Dynamics 365

How Healthcare Outcomes Performance Company (HOPCo) connected Coupa to Microsoft Dynamics 365 with DataMap's D365 connector — and presented the results alongside Coupa and DataMap.

Read

FAQ