It is a product-strategy post from a Microsoft executive. The adoption, performance and reliability figures are Microsoft's own claims. Microsoft's Learn documentation shows what admins and makers still have to configure, and that is where this story gets practical.
The numbers Microsoft is citing
Microsoft says 9,000 makers attended the Power Platform Community Conference last month. I'm using the post's own wording for the conference figure, since the search results don't independently confirm it. The post also reports the following:
- 80 million monthly users across Power Platform.
- 20% growth in daily active Power Apps users over the past year.
- 20% growth in Power Automate flow runs.
- Doubled AI usage in Power Apps.
The post doesn't define "user" or "AI usage," and it gives no baseline counts. Read these as directional marketing metrics, not audited findings.
Pillar 1: quality over novelty
Microsoft says it shipped more than 130 capabilities this year. It says 65% of them targeted quality and experience, and that it retired 24 features. The post doesn't list the retired features, so admins should check their own estates against Microsoft's deprecation notices.
The named improvements are:
- Performance: new canvas controls, faster model-driven app loads, and faster mobile app startup.
- User experience: calendar, card and timeline views in model-driven apps, native mobile experiences, and fewer steps to connect cloud flows to on-premises systems.
- Reliability: fewer canvas-app customer incidents, and offline sync that keeps working while the app is in the background.
- Maker productivity: a detachable formula bar, a delegation limit raised to 10,000 items, and a grid container for responsive layouts. Power Automate gains inline views in cloud flows, plus Flowchart and Flow Map views in the desktop app.
The post gives no benchmarks and doesn't say what "faster" is measured against. It also gives no rollout dates by feature. Test any performance claim in your own environment before you cite it internally.
Pillar 2: hybrid human-and-agent building
Microsoft describes agents as optional collaborators. They can analyze, refactor and extend existing apps and flows, not just create new ones. Makers can bring them in and remove them when they're done. If a team runs out of tokens, the post says, it can keep building with the non-AI tooling.
The technical hook is Model Context Protocol (MCP) servers. Through them, agents build with Power Platform's own controls and components. That keeps the output low-code, so teammates can open and edit it. It is also meant to remain governable like any other solution.
The post names these entry points:
- Professional developers: GitHub Copilot or other supported coding agents.
- Makers: dedicated studios inside Power Platform products.
- Business users: Microsoft Copilot and Cowork.
The post doesn't give token pricing, supported agent versions or prerequisites. It uses G&J Pepsi, which it calls the largest independent Pepsi bottler in the US, as its example. The example is anecdotal, and the post offers no measured outcome for it.
Pillar 3: Copilot inside the apps you already run
The post says Copilot in model-driven apps became generally available in April. It says Copilot in canvas apps reaches general availability this November, with no exact date.
Microsoft's release-plan page for Microsoft 365 Copilot in canvas apps lists a public preview start of April 13, 2026. The general availability field was blank in the snippet I retrieved. Makers turn it on from the app's settings panel in Power Apps Studio. After the app is enabled and published, users see a Copilot entry point in the app header and can open the chat pane alongside the app. Check your tenant for the actual GA state before you plan a rollout.
The fine print in Microsoft Learn
Microsoft's documentation for model-driven apps sets limits that the blog post doesn't mention:
- An administrator must enable Copilot before it appears in the app.
- Power Apps users need both a Power Apps premium license and a Microsoft 365 Copilot license.
- Dynamics 365 app users need a Dynamics 365 Enterprise or Premium license. Full Work IQ capabilities beyond Dataverse grounding also require a Microsoft 365 Copilot license.
- The feature answers questions about Dataverse table data using read-only operations. Users can't change data with it, and the documentation says changes require customization with an agent.
- It isn't available in the Power Apps mobile app.
- Selecting an explicit agent in the pane stops it answering questions about Dataverse table data unless you configure the agent to do so.
Don't confuse this with the old Copilot control
There is an older Copilot control for canvas apps. Since February 2, 2026, it can't be added to new canvas apps. Existing uses keep working for a limited time but will eventually lose support. Microsoft names Microsoft Copilot in canvas apps as the recommended replacement. If you have apps using the old control, start planning the migration now.
Third-party guides also say the replacement isn't available in the Power Apps mobile app during preview. That comes from secondary sources, so confirm it in current documentation.
Pillar 4: Business Applications in Work IQ
This is the most consequential idea in the post. Microsoft says apps, flows and sites hold processes, rules and approvals that agents need. Business Applications in Work IQ is meant to expose them to agents in Microsoft Copilot, Cowork, Copilot Studio, GitHub Copilot and custom agents. It says this works without opening the app or rebuilding it, and within existing permissions.
Microsoft Learn describes Work IQ as the context layer for Copilot and agents. Business Applications in Work IQ adds Dynamics 365 and Power Apps data and process context, while Dataverse permissions and app controls still apply.
It isn't one switch
The documentation lists several connection paths:
| Path | Intended use |
|---|---|
| Microsoft Copilot and Copilot Cowork | Business context inside Microsoft 365 experiences |
| Work IQ MCP | Agents or coding clients that need Microsoft 365 and business app context through one MCP server |
| Dataverse MCP | Direct, environment-specific Dataverse tools or business skills, configured per environment |
| Dataverse Ask API | Application code that needs answers grounded in a Dataverse semantic model |
| Dataverse plugin for coding agents | Building solutions; not end-user data grounding |
The prerequisites are:
- Power Platform administrators must enable Work IQ in the environments that provide business context.
- AI administrators manage availability of Microsoft Copilot and the Work IQ MCP server.
- Makers manage model-driven app participation.
The documented boundaries include:
- Copilot Cowork is in preview.
- Dynamics 365 ERP is in preview.
- Preview features can change or be discontinued.
- Underlying consumption-based services can still incur license fees during preview.
- Work IQ MCP has no retrieval-only mode that skips response generation. Teams that need deterministic retrieval should use the source API or another targeted integration.
One third-party Ignite recap rates Business Applications in Work IQ as generally available with ERP in preview. Microsoft's own Learn page, updated Nov. 17, still labels some parts as preview, so check each component rather than assume.
What admins and makers should do now
- Inventory legacy Copilot controls in canvas apps and plan migration to Microsoft Copilot in canvas apps.
- Check licensing early. Power Apps premium plus Microsoft 365 Copilot is the documented combination for Power Apps users.
- Decide who owns enablement. Power Platform admins, AI admins and makers each control a different layer of Work IQ.
- Review Dataverse permissions before exposing apps to agents. The permission model is the main safeguard Microsoft points to.
- Treat preview items as non-production until Microsoft marks them generally available.
- Measure the performance and reliability claims in your own environment.
Analysis
Reusing existing investments is a sensible pitch for organizations with years of canvas and model-driven apps. It also has a commercial side. It points customers toward Copilot and Work IQ licensing and consumption, and the post leaves out the cost details.
Microsoft says users "decide when to pay for AI," and that is worth testing against your actual billing. The broader point is that the agent features lean heavily on Dataverse and Microsoft 365 Copilot. Teams with data outside Dataverse will need extra integration work. The documentation says you don't have to move every data source into Dataverse, but it does expect each source to be connected through an appropriate tool or service.
Microsoft's direction is clear, and the post tells you where the platform is heading. The practical cost, rollout dates and preview status are in the documentation, not the blog.
References
- Turn AI ambition into real business value with Power Platform - Microsoft Microsoft · 2026-11-18T19:00:00+00:00
- Use Microsoft Copilot in model-driven apps - Power Apps | Microsoft Learn learn.microsoft.com
- Add a Copilot control to a canvas app (preview) - Power Apps learn.microsoft.com