Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Key Takeaways
- Microsoft is adding natural-language app building to both Copilot Cowork (via the new /app skill) and Copilot Studio, rolling out in public preview over the next week.
- Apps are full-stack, use open standards, and connect to enterprise data through connectors and Work IQ — not just read data, but write results back to Microsoft 365 systems.
- Published apps get centralized governance in the Microsoft 365 admin center, with Entra identity and connector policies enforced by default.
What’s New
Microsoft is bringing app building directly into the tools your organization already uses for agents and workflows. In Copilot Cowork, you can now build apps with the new /app skill, available through the Microsoft Frontier program. In Copilot Studio, app building is rolling out in public preview over the next week, sitting alongside agents and workflows so you can turn an idea into a complete business process solution from one place.
The pitch is simple: describe the outcome, users, data, and actions you need, and Copilot Studio uses agentic coding to generate a working app scaffold. From there you keep iterating in plain language, inspect the app in preview, and — if you’re technical — go straight into the underlying code.
How It Works
- Choose App (Preview) from the Copilot Studio home screen, or invoke
/appin a Copilot Cowork chat. - Describe the business outcome, users, data sources, and actions the app needs to support.
- Copilot Studio generates a working app scaffold, which you refine through further conversation.
- Advanced makers and developers can drop into the app’s structure and code for finer control — the experience scales from information worker to developer.
Connecting Apps to Real Business Data
This isn’t just app scaffolding in a vacuum. Apps built with Copilot Cowork and Copilot Studio use connectors — including Work IQ for organizational context — to read from and write back to the Microsoft 365 systems people already work in. Microsoft’s examples include an onboarding app that pulls progress from a business data source, surfaces learning resources, and updates onboarding records, and a field service app that retrieves technical context from a third-party system and writes results back to connected systems.
| Capability | What It Means |
|---|---|
| Full-stack, open standards | Git-backed source control, deployment stages, version isolation |
| Work IQ / connectors | Read and write access to Microsoft 365 tenant data |
| Entra identity by default | Apps respect existing identity and connector policies |
| M365 admin center visibility | Inventory of published apps plus lifecycle controls for IT |
Apps created in Copilot Cowork and Copilot Studio are full-stack apps built using open standards.
— Microsoft Copilot Blog
Why This Matters for IT Admins
The interesting part isn’t that non-developers can generate an app in minutes — that’s already common with agentic coding tools. It’s that Microsoft is pairing that with centralized governance from day one: identity, data access, and connector policies are enforced automatically, and published apps show up in the Microsoft 365 admin center with an inventory and lifecycle controls. That’s the piece that’s usually missing when “citizen developers” start shipping their own tools.
Practical Steps
- Get ahead of shadow apps. If citizen developers in your org are already using agentic coding tools informally, this gives you a governed alternative to point them toward before ungoverned apps proliferate.
- Check Frontier program access. The /app skill in Copilot Cowork is available now through the Microsoft Frontier program — worth confirming your tenant’s enrollment status if you want early access.
- Review connector and data policies now. Since apps inherit existing connector policies and Entra identity, tightening those policies before rollout is more effective than trying to retrofit governance after apps are already published.
- Watch the M365 admin center. Once app building reaches your environment, the admin center becomes your inventory and control point — build a habit of reviewing published apps there regularly.
- Budget for usage-based billing. App building and running follows the usage-based Copilot Credits billing model, so factor that into cost planning rather than treating it as a flat licensing add-on.
Lab Tip
- If you have a Frontier program tenant or test environment, try the /app skill on a low-stakes internal process (like a simple request tracker) before pointing power users at it. It’s a fast way to see what the generated code and governance experience actually look like from an admin’s chair.
Bottom Line
App building in Copilot Cowork and Copilot Studio is Microsoft’s answer to the “everyone’s an app builder now” moment: let people describe what they need, but keep identity, data access, and lifecycle governance centralized in the admin center from the start. For IT teams already juggling shadow IT concerns around AI coding tools, this is worth testing early rather than waiting for it to show up unannounced in your tenant.
Source: Microsoft Copilot Blog, “Build apps in Copilot Cowork and Copilot Studio,” published September 10, 2026.
