Microsoft’s coming Copilot Super App is shaping up less as a new standalone AI product than as the front door for Microsoft’s existing work, coding, and agent services—and Charles Lamanna is responsible for much of the machinery that must make that consolidation work. GeekWire’s new profile of Lamanna, Microsoft’s EVP of Copilot, Agents and Platform, adds unusually direct detail to a strategy Microsoft has described publicly but has not yet turned into a shipping product.
The immediate practical point for Windows and Microsoft 365 administrators is restraint: there is still no announced launch date, supported-platform list, tenant rollout plan, or definitive licensing model for the Super App. Microsoft CEO Satya Nadella said at Build on June 2 that Chat, Cowork, and Code would come together “this summer,” while GeekWire now reports the launch is expected in the coming weeks. On August 6, that leaves the product in the awkward gap between a public strategy and a deployable service.
Lamanna’s account makes clear why Microsoft thinks it needs the app. The company’s Copilot portfolio has accumulated consumer Copilot, Microsoft 365 Copilot, GitHub Copilot, Copilot Studio, Security Copilot, agents, and the newly launched Cowork service. Each has different entry points, data boundaries, purchasing paths, and administrative controls. Microsoft’s answer is to make a single Copilot surface the place users start, then route their request to the appropriate back-end service.
That is a major architectural ambition. It is also an admission that Microsoft’s earlier Copilot rollout produced a product map that customers—and often Microsoft’s own branding—struggled to explain.
GeekWire reports that Lamanna calls the internal sprawl “Copilot Palooza,” saying Microsoft fragmented its Copilot efforts among consumer, commercial, coding, and other products. His remedy is the Super App: one home containing Chat, Code, Cowork, and “Autopilots,” Microsoft’s term for always-on agents.
But Lamanna is not the sole executive charged with making Copilot coherent. Microsoft’s March 17 leadership announcement assigned Jacob Andreou, EVP of Copilot, responsibility for the unified consumer and commercial Copilot experience, including design, product, growth, and engineering. Lamanna, alongside Ryan Roslansky and Perry Clarke, was assigned to Microsoft 365 apps and the Copilot platform.
That division matters. Andreou’s team is responsible for whether people understand and use the front end. Lamanna’s teams have to make it capable of reaching Microsoft 365 data, Dynamics 365 records, Power Platform workflows, SharePoint sites, OneDrive files, agent tools, and external systems without turning every interaction into a permissions, cost, or latency problem.
Microsoft’s current biography for Lamanna confirms that his remit includes Copilot, Agent 365, Copilot Studio, Power Platform, Dynamics 365, SharePoint, and OneDrive. GeekWire’s description of him as part of the Copilot Leadership Team is therefore consistent with Microsoft’s organizational record, but it should not be read as a transfer of consumer-Copilot ownership away from Andreou. The Super App is being built across a deliberately split experience-and-platform structure.
Microsoft is trying to organize its management model around the product architecture it wants: a common Copilot shell above distinct context, productivity, business-data, agent, and model layers. Whether that makes the product simpler for customers is still unproven.
Lamanna’s description goes further: he characterizes Work IQ as a background, application-independent way to reach Microsoft 365. In that model, a user would not need to open Outlook to ask about email, SharePoint to find a document, or Dynamics 365 to retrieve customer information. Copilot would determine which intelligence layer, connector, or Model Context Protocol server to use and return the result inside its own interface.
This is the real change embedded in the Super App strategy. Office applications are not disappearing; Microsoft’s existing documentation still positions Copilot inside Word, Excel, PowerPoint, Outlook, Teams, Edge, and the Microsoft 365 Copilot app. But Microsoft is trying to make the application boundary less important for routine retrieval and delegated work.
For users, that could reduce app-switching. For administrators, it raises a less glamorous but more consequential issue: a centralized conversational interface makes existing permissions, oversharing, retention, sensitivity labels, and data-governance mistakes easier to expose at scale. Copilot can only retrieve what the signed-in identity can access, but that is not a complete safeguard when years of loosely governed SharePoint sites, mailbox permissions, and Dynamics records are suddenly queryable through a single prompt box.
Microsoft has already incorporated this concept into the existing Microsoft 365 Copilot app. Its updated chat-centered interface is rolling out broadly, with a Work IQ control that determines whether Copilot uses enterprise context. The redesigned app also adds a Tasks view for long-running agent activity and lets people pin agents, Microsoft 365 apps, and Copilot experiences in the navigation pane.
That means the Super App is unlikely to arrive as a clean break from today’s Microsoft 365 Copilot app. The current redesign looks more like its operational precursor: an app shell that combines chat, work context, agents, task tracking, and links out to familiar Office applications.
Cowork requires a Microsoft 365 Copilot User Subscription License, but its long-running tasks are billed on top through usage-based Copilot Credits. Microsoft says task costs reflect model use, context retrieval, tool calls, and runtime. Administrators can set tenant, group, and user spending limits, and Cowork access requires usage-based billing to be enabled.
The result is that the AI assistant’s visible entry point may be free or broadly available while meaningful agent work becomes metered infrastructure consumption. That is a material shift from traditional Office economics, where cost was principally tied to a named user’s subscription.
In the ordinary Microsoft 365 model, an employee opening Outlook 100 times does not create a separate compute bill. In the agent model, a Copilot that repeatedly reads mail, retrieves records, calls tools, browses, generates files, and keeps working after the user leaves may generate consumption that varies by task and by model. Lamanna’s warning of a large back-end demand surge is therefore not merely a capacity concern; it helps explain the pricing model.
Admins should treat the Super App as a potential consolidation of consumption surfaces, not as a simple new chat client. If Microsoft succeeds in placing Cowork, code execution, agent actions, and business-data access behind one interface, finance and IT teams will need cost controls that span more than one Copilot SKU.
GeekWire reports that Lamanna expects Dynamics 365 to evolve into agents connected to Dynamics Model Context Protocol servers, and that Microsoft is testing tighter Dataverse integration with Copilot. Dataverse is the data platform underneath much of Power Platform and Dynamics 365. Bringing it directly into Copilot would let users query CRM and ERP information from the same place they ask about email, meetings, documents, and work tasks.
Microsoft has already signaled the underlying direction. Its Work IQ material says it is selecting among MCP server tools, agent flows, APIs, and plugins to let Copilot observe, retrieve, reason, and execute. The company also says broad Dataverse access through Work IQ across Microsoft 365 Copilot experiences is planned for summer 2026.
The difference between a connector and Microsoft’s proposed Super App model is control of the user journey. A connector lets Copilot retrieve data. A central Copilot surface can keep the user inside Microsoft’s AI interface while it reaches the data, invokes agents, and possibly triggers actions in Dynamics, Power Platform, Salesforce, ServiceNow, or another connected system.
That makes the Super App a strategic bid to own the working session, not merely the chat interaction. If it becomes the place where users discover data, ask for analysis, approve actions, and inspect agent work, traditional business applications risk becoming systems of record that users visit mainly for exceptions and detailed editing.
The unanswered questions include whether the Super App will be a new Windows application, a replacement for or evolution of the Microsoft 365 Copilot app, a web-first experience, or a combination of all three. Microsoft has not said which functions will be available to consumer accounts versus Microsoft Entra work accounts, whether GitHub Copilot functionality will require separate entitlements, or how cross-product data boundaries will appear in the interface.
Nor has Microsoft announced the Super App’s support status for government clouds, its accessibility and device-management requirements, or whether it will create new telemetry, audit, retention, or eDiscovery considerations beyond those already attached to Copilot and Cowork. Those omissions are normal for a product that has not launched, but they are why organizations should avoid rewriting user guidance around an app that remains unnamed in official product documentation.
For now, the tangible deployment work is in the services Lamanna wants to unify: clean up Microsoft 365 permissions, decide who may use Work IQ-grounded experiences, establish Copilot Credit budgets, and identify which agents can access sensitive business systems. The Super App may eventually become the visible symbol of Microsoft’s “Copilot company” ambition. The administrative consequences are already arriving through the products underneath it.
Lamanna’s account makes clear why Microsoft thinks it needs the app. The company’s Copilot portfolio has accumulated consumer Copilot, Microsoft 365 Copilot, GitHub Copilot, Copilot Studio, Security Copilot, agents, and the newly launched Cowork service. Each has different entry points, data boundaries, purchasing paths, and administrative controls. Microsoft’s answer is to make a single Copilot surface the place users start, then route their request to the appropriate back-end service.
That is a major architectural ambition. It is also an admission that Microsoft’s earlier Copilot rollout produced a product map that customers—and often Microsoft’s own branding—struggled to explain.
Lamanna owns the platform half of the consolidation
GeekWire reports that Lamanna calls the internal sprawl “Copilot Palooza,” saying Microsoft fragmented its Copilot efforts among consumer, commercial, coding, and other products. His remedy is the Super App: one home containing Chat, Code, Cowork, and “Autopilots,” Microsoft’s term for always-on agents.But Lamanna is not the sole executive charged with making Copilot coherent. Microsoft’s March 17 leadership announcement assigned Jacob Andreou, EVP of Copilot, responsibility for the unified consumer and commercial Copilot experience, including design, product, growth, and engineering. Lamanna, alongside Ryan Roslansky and Perry Clarke, was assigned to Microsoft 365 apps and the Copilot platform.
That division matters. Andreou’s team is responsible for whether people understand and use the front end. Lamanna’s teams have to make it capable of reaching Microsoft 365 data, Dynamics 365 records, Power Platform workflows, SharePoint sites, OneDrive files, agent tools, and external systems without turning every interaction into a permissions, cost, or latency problem.
Microsoft’s current biography for Lamanna confirms that his remit includes Copilot, Agent 365, Copilot Studio, Power Platform, Dynamics 365, SharePoint, and OneDrive. GeekWire’s description of him as part of the Copilot Leadership Team is therefore consistent with Microsoft’s organizational record, but it should not be read as a transfer of consumer-Copilot ownership away from Andreou. The Super App is being built across a deliberately split experience-and-platform structure.
Microsoft is trying to organize its management model around the product architecture it wants: a common Copilot shell above distinct context, productivity, business-data, agent, and model layers. Whether that makes the product simpler for customers is still unproven.
Work IQ is the dependency, not a cosmetic Copilot feature
The important technical element in Lamanna’s profile is Work IQ. Microsoft describes Work IQ as its workplace intelligence layer, built to supply agents with context from people, emails, documents, meetings, organizational relationships, and connected external sources. At Build, Microsoft said Work IQ APIs became generally available on June 16.Lamanna’s description goes further: he characterizes Work IQ as a background, application-independent way to reach Microsoft 365. In that model, a user would not need to open Outlook to ask about email, SharePoint to find a document, or Dynamics 365 to retrieve customer information. Copilot would determine which intelligence layer, connector, or Model Context Protocol server to use and return the result inside its own interface.
This is the real change embedded in the Super App strategy. Office applications are not disappearing; Microsoft’s existing documentation still positions Copilot inside Word, Excel, PowerPoint, Outlook, Teams, Edge, and the Microsoft 365 Copilot app. But Microsoft is trying to make the application boundary less important for routine retrieval and delegated work.
For users, that could reduce app-switching. For administrators, it raises a less glamorous but more consequential issue: a centralized conversational interface makes existing permissions, oversharing, retention, sensitivity labels, and data-governance mistakes easier to expose at scale. Copilot can only retrieve what the signed-in identity can access, but that is not a complete safeguard when years of loosely governed SharePoint sites, mailbox permissions, and Dynamics records are suddenly queryable through a single prompt box.
Microsoft has already incorporated this concept into the existing Microsoft 365 Copilot app. Its updated chat-centered interface is rolling out broadly, with a Work IQ control that determines whether Copilot uses enterprise context. The redesigned app also adds a Tasks view for long-running agent activity and lets people pin agents, Microsoft 365 apps, and Copilot experiences in the navigation pane.
That means the Super App is unlikely to arrive as a clean break from today’s Microsoft 365 Copilot app. The current redesign looks more like its operational precursor: an app shell that combines chat, work context, agents, task tracking, and links out to familiar Office applications.
Cowork proves the business model is moving beyond per-seat licenses
Lamanna told GeekWire that the Super App itself will probably be free, while the services it exposes will not be. Microsoft has not published pricing for the Super App, so that remains an executive characterization rather than a commercial commitment. However, Microsoft’s June general-availability launch for Copilot Cowork demonstrates the pricing direction Lamanna described.Cowork requires a Microsoft 365 Copilot User Subscription License, but its long-running tasks are billed on top through usage-based Copilot Credits. Microsoft says task costs reflect model use, context retrieval, tool calls, and runtime. Administrators can set tenant, group, and user spending limits, and Cowork access requires usage-based billing to be enabled.
The result is that the AI assistant’s visible entry point may be free or broadly available while meaningful agent work becomes metered infrastructure consumption. That is a material shift from traditional Office economics, where cost was principally tied to a named user’s subscription.
In the ordinary Microsoft 365 model, an employee opening Outlook 100 times does not create a separate compute bill. In the agent model, a Copilot that repeatedly reads mail, retrieves records, calls tools, browses, generates files, and keeps working after the user leaves may generate consumption that varies by task and by model. Lamanna’s warning of a large back-end demand surge is therefore not merely a capacity concern; it helps explain the pricing model.
Admins should treat the Super App as a potential consolidation of consumption surfaces, not as a simple new chat client. If Microsoft succeeds in placing Cowork, code execution, agent actions, and business-data access behind one interface, finance and IT teams will need cost controls that span more than one Copilot SKU.
Dynamics and Dataverse are the commercial test
The strongest incentive for Microsoft to pull users into a Copilot front door is not consumer chat. It is business data.GeekWire reports that Lamanna expects Dynamics 365 to evolve into agents connected to Dynamics Model Context Protocol servers, and that Microsoft is testing tighter Dataverse integration with Copilot. Dataverse is the data platform underneath much of Power Platform and Dynamics 365. Bringing it directly into Copilot would let users query CRM and ERP information from the same place they ask about email, meetings, documents, and work tasks.
Microsoft has already signaled the underlying direction. Its Work IQ material says it is selecting among MCP server tools, agent flows, APIs, and plugins to let Copilot observe, retrieve, reason, and execute. The company also says broad Dataverse access through Work IQ across Microsoft 365 Copilot experiences is planned for summer 2026.
The difference between a connector and Microsoft’s proposed Super App model is control of the user journey. A connector lets Copilot retrieve data. A central Copilot surface can keep the user inside Microsoft’s AI interface while it reaches the data, invokes agents, and possibly triggers actions in Dynamics, Power Platform, Salesforce, ServiceNow, or another connected system.
That makes the Super App a strategic bid to own the working session, not merely the chat interaction. If it becomes the place where users discover data, ask for analysis, approve actions, and inspect agent work, traditional business applications risk becoming systems of record that users visit mainly for exceptions and detailed editing.
What Microsoft still has not said
Microsoft has supplied the concept and enough component parts to make the Super App believable. It has not yet supplied the operational facts that enterprise customers need before treating it as a deployment target.The unanswered questions include whether the Super App will be a new Windows application, a replacement for or evolution of the Microsoft 365 Copilot app, a web-first experience, or a combination of all three. Microsoft has not said which functions will be available to consumer accounts versus Microsoft Entra work accounts, whether GitHub Copilot functionality will require separate entitlements, or how cross-product data boundaries will appear in the interface.
Nor has Microsoft announced the Super App’s support status for government clouds, its accessibility and device-management requirements, or whether it will create new telemetry, audit, retention, or eDiscovery considerations beyond those already attached to Copilot and Cowork. Those omissions are normal for a product that has not launched, but they are why organizations should avoid rewriting user guidance around an app that remains unnamed in official product documentation.
For now, the tangible deployment work is in the services Lamanna wants to unify: clean up Microsoft 365 permissions, decide who may use Work IQ-grounded experiences, establish Copilot Credit budgets, and identify which agents can access sensitive business systems. The Super App may eventually become the visible symbol of Microsoft’s “Copilot company” ambition. The administrative consequences are already arriving through the products underneath it.
References
- Primary source: GeekWire
Published: 2026-08-06T14:41:27+00:00
Microsoft 2.5: How EVP Charles Lamanna is helping turn Microsoft into the ‘Copilot company’ – GeekWire
Charles Lamanna, who leads Microsoft's Copilot, agents, and platform work, is helping build the coming Copilot Super App — a single front door meant to unify the company's sprawling AI products. He talks with Mary Jo Foley about the plan, the "Copilot Palooza" it's meant to fix, and why...www.geekwire.com - Related coverage: techcommunity.microsoft.com
A closer look at Work IQ | Microsoft Community Hub
Work IQ is the intelligence layer that personalizes Microsoft 365 Copilot to you and your organization.
techcommunity.microsoft.com
- Related coverage: geekwire.com
Mary Jo Foley: No Copilot 'Super App' at Microsoft Build, but plenty of agentic fodder – GeekWire
Microsoft teased its rumored Copilot "Super App" at Build but didn't demo it. Longtime Microsoft watcher Mary Jo Foley assesses the no-show, explains why the initiative matters, and considers what the company actually did announce.www.geekwire.com - Related coverage: microsoft.com
Charles Lamanna | Author at Microsoft 365 Blog
Read the latest posts and insights by Charles Lamanna, part of Microsoft's team of experts at Microsoft 365 Blog.www.microsoft.com - Related coverage: learn.microsoft.com
Decide which Copilot is right for you | Microsoft Learn
Microsoft has several Copilot AI virtual assistants, including Microsoft 365 Copilot Chat, Microsoft 365 Copilot, Microsoft Copilot, Microsoft Security Copilot, GitHub Copilot, and Copilot Studio. Decide which Copilot is right for you and your organization. Which Copilot is right for me?learn.microsoft.com - Related coverage: news.microsoft.com
Introducing the Frontier Suite - Source EMEA
news.microsoft.com
- Related coverage: blogs.microsoft.com
Microsoft Build 2026: Be yourself at work - The Official Microsoft Blog
Platforms shift when developers build. We explore, choose tools, dream, create. This platform shift comes with more information than ever, ready at your fingertips. This shift, it’s about building fast AND THEN: it’s about building, operating, optimizing and observing. Securing your...blogs.microsoft.com - Related coverage: techcommunity.microsoft.com
- Related coverage: blogs.microsoft.com
Announcing Copilot leadership update - The Official Microsoft Blog
Satya Nadella, Chairman and CEO, and Mustafa Suleyman, Executive Vice President and CEO of Microsoft AI, shared the below communications with Microsoft employees this morning. SATYA NADELLA MESSAGE I want to share two org changes we’re making to our Copilot org and superintelligence effort. It’s...blogs.microsoft.com - Related coverage: news.microsoft.com
Copilot Cowork ya está disponible de forma general - Source EMEA
news.microsoft.com
- Related coverage: devblogs.microsoft.com
MCP Apps now available in Copilot chat - Microsoft 365 Developer Blog
Learn how MCP Apps transform agent capabilities in Microsoft 365 Copilot, enabling seamless app interactions.devblogs.microsoft.com - Related coverage: newsroom.workday.com
Workday and Microsoft to Deliver Unified AI Agent Experience for the Enterprise - Sep 16, 2025
PDF documentnewsroom.workday.com
- Related coverage: windowscentral.com
Microsoft Copilot Changes: Moving Away From OpenAI? | Windows Central
Ex-SnapChat exec takes over Copilot AI experiences as Microsoft AI CEO doubles down on in-house modelswww.windowscentral.com - Related coverage: techradar.com
Microsoft makes Copilot Cowork open to everyone, and wants to help you tackle even the trickiest work tasks | TechRadar
Copilot Cowork gets an upgrade as it opens to all userswww.techradar.com - Related coverage: tomsguide.com
Biggest Microsoft Build 2026 announcements — agentic AI, RTX Spark Dev Box, GitHub Copilot app, new MAI models, and more | Tom's Guide
All the big news from Microsoft's AI-focused eventwww.tomsguide.com - Related coverage: techradar.com
Microsoft 365 confirms new premium tier focused on AI and productivity | TechRadar
Microsoft adds new E7 plan to cope with AI usagewww.techradar.com - Related coverage: itpro.com
Satya Nadella says “our multi-model approach goes beyond choice’ as Microsoft adds Claude AI models to 365 Copilot | IT Pro
Users can choose between both OpenAI and Anthropic models in Microsoft 365 Copilotwww.itpro.com - Related coverage: microsoft.com
Microsoft Fiscal Year 2026 Third Quarter Earnings Conference Call
www.microsoft.com
- Related coverage: aiweekly.co
Microsoft Builds Unified Copilot Super App for Summer | AI Weekly
Microsoft is consolidating its Copilot products into a unified super app targeting launch by end of summer 2026. The project, internally called…
aiweekly.co
- Related coverage: investing.com
Microsoft Analysis & Opinion (MSFT) - Investing.com
This page contains all of the latest analysis and reports for the Microsoft Corporation stock.www.investing.com - Related coverage: tomsguide.com
Microsoft earnings — 'You can think of agents as the new apps,' CEO Satya Nadella | Tom's Guide
Will we finally learn whether Microsoft’s big bet on AI has paid off?www.tomsguide.com - Related coverage: learn.microsoft.com
What's new in Copilot Cowork | Microsoft Learn
Discover the latest features and improvements in Microsoft 365 Copilot Cowork.learn.microsoft.com - Related coverage: support.microsoft.com
- Related coverage: cdn-dynmedia-1.microsoft.com
- Related coverage: cdn-dynmedia-1.microsoft.com