The listing is new, its status is still "In development," and Microsoft's dates often move. This article covers what the roadmap entry says, how it relates to the developer work Microsoft has already documented, and what admins should check before anyone promises this to their users.
What the App Blocks roadmap entry says
The App Blocks entry has roadmap ID 577743. According to its metadata, it was published on October 26, 2026, and its last-modified date is unknown. Here are the key details:
| Field | Roadmap value |
|---|---|
| Product | Microsoft Copilot (Microsoft 365) |
| Status | In development |
| Release ring | General Availability |
| Estimated GA | October 2026 |
| Platforms | Android, Desktop, iOS, Mac, Web |
| Cloud instance | Worldwide (Standard Multi-Tenant) |
Microsoft's description says App Blocks will let Microsoft 365 Copilot Chat users turn their requests and data into rich, interactive experiences directly in the conversation. You could explore data, change inputs, see outcomes and simulate workflows without leaving the chat. The entry also mentions "grounded" scenarios, where Copilot first fetches current information and then shows it as an interactive app instead of a static summary.
Those are the facts. Several things are missing from the entry:
- an exact rollout date
- licensing terms
- tenant or admin controls
- usage limits
- instructions for users or developers
The roadmap page also includes Microsoft's standard warning: all information is subject to change, and entries are removed once a feature becomes generally available, is cancelled, or is postponed.
The listing arrived on October 26 with a GA estimate of October 2026, which leaves only a few days. Either the rollout is about to start or the date will slip. Don't build a deployment plan around that date.
Section summary: App Blocks is an in-development Copilot Chat feature that shows answers as interactive mini-apps. Microsoft has given it broad platform coverage and an aggressive October 2026 target, but no licensing or admin details yet.
The developer project with a similar idea
App Blocks isn't Microsoft's only effort to put interactive UI inside Copilot. On September 30, 2026, Vesa Juvonen, a Principal Program Manager at Microsoft, wrote about Copilot UX components in the SharePoint Framework (SPFx) roadmap update on the Microsoft 365 Developer Blog. He described them as rich, interactive experiences rendered directly in Microsoft 365 Copilot, on track for general availability in October 2026 for all customers worldwide.
The examples there will look familiar: ask about this quarter's sales and get a live chart you can explore, or ask for time off and get a form where you check the dates and submit. According to that post, agents can show charts, maps, KPIs, forms, approvals and live business data in the Copilot canvas. Components appear inline or can expand to full screen.
The capability has been renamed twice. Microsoft announced it in June as SharePoint Copilot Apps, used Copilot Components as a working name in August, and settled on Copilot UX components as the final name. Microsoft says the capability itself didn't change.
Now there's a fourth name to keep track of: App Blocks. Microsoft has not said that roadmap item 577743 is the same as Copilot UX components, and the two descriptions read differently:
- App Blocks is described from the user's side: Copilot Chat users turn their own requests and data into interactive apps. That sounds like Copilot generating the app on the spot.
- Copilot UX components are described from the developer's side. They are built in SPFx code, packaged and deployed to a tenant, and then shown by an agent.
These may be two layers of the same product, or two separate features that share a release window. Treat them as closely related until Microsoft says otherwise. That comparison is our own reading of Microsoft's published descriptions, not something Microsoft has confirmed.
Section summary: Copilot UX components are the documented, developer-built way to put interactive UI in Copilot. App Blocks looks more like an end-user feature. Microsoft hasn't explained how the two relate.
How Copilot UX components work
Since the App Blocks entry has no technical details, the SPFx documentation is the best guide to Microsoft's design approach. The blog post describes a "human in the loop" pattern:
- Copilot works out the intent. The user asks in natural language, and the agent decides what's needed.
- The component shows the facts. Microsoft says the business data and choices are rendered by your code, not generated by the model.
- The person decides. The user reviews, adjusts and confirms. The action then reaches business systems through APIs the solution calls.
This split matters. A chart drawn by code from real data is a different thing from a chart a language model made up. That guarantee belongs to Copilot UX components specifically. You shouldn't assume every App Block will use code-rendered data or ask for confirmation before acting, especially if App Blocks turn out to be generated on the fly.
The other architecture points from the post:
- Components run on the existing SPFx hosting model in the Microsoft 365 tenant, so there's no new infrastructure to run and no new place for data to live.
- Single sign-on is built in, and security on the client side uses the signed-in user's permissions.
- Development uses React and standard JavaScript libraries and follows the MCP Apps model.
- Each solution is a standard SPFx package that can go to your own tenant or to customers' tenants.
Trying the developer preview
As of Microsoft's September 30 post, the Copilot UX components public preview was turned on in every tenant worldwide, with no special release ring, sign-up or allow-list. Microsoft gave four steps:
- Install the SPFx 1.24 preview generator:
npm install @microsoft/generator-sharepoint@next --global - Create a new Copilot UX component from a template: Minimal, No framework, or React.
- Run and test it locally in the Copilot Workbench.
- Deploy it to your tenant and surface it in Copilot.
If you want to see it without writing code, Microsoft published scenario samples with ready-to-deploy packages, demo data and setup instructions.
Licensing caveat: during the preview, Microsoft said you don't need a Microsoft 365 Copilot licence to develop or test, and there are no consumption-based costs. It also said licensing for general availability is still to be confirmed. Don't assume the free preview terms will apply after GA.
The September post also listed some context and limits:
- SPFx 1.24 GA was planned for October 2026, bringing Copilot UX components GA and React 18.
- Node.js 24 and 26 support was expected in the 1.24 release candidate and GA.
- Microsoft wants to bring components to Copilot in Teams, Cowork, Word, Excel, PowerPoint and Outlook. That's a future plan, not something supported now.
- Microsoft called all of these plans subject to change.
Section summary: Developers can start trying Copilot UX components through the SPFx 1.24 preview today. GA licensing hasn't been announced, and wider Copilot integration is still on the wish list.
What admins should do now
How will Microsoft govern App Blocks? The roadmap entry doesn't say. Microsoft's existing Copilot controls are the best guide to where any App Blocks settings might appear.
Microsoft's documentation on Copilot app admin settings says admins can configure features such as pinning Microsoft 365 Copilot Chat, allowing or blocking agents, and more. For agents, in the Microsoft 365 admin center > Settings > Integrated Apps, admins can deploy or block agents from showing in the Copilot app. Copilot Pages and Notebooks, two other canvas features, are controlled through Cloud Policy, and the same documentation lists both as allowed by default.
If App Blocks follow that pattern, they may arrive switched on, with any controls added afterwards. That's an inference from how Microsoft has handled other features, not a documented fact about App Blocks.
Before App Blocks reach your users, it's worth checking a few things:
- Watch Message Center. Roadmap entries rarely include the rollout timing or settings details that Message Center posts do.
- Check whether your network allows Copilot. Microsoft's guidance on managing Copilot Chat recommends confirming that rules, URL category filters, Conditional Access, or app control policies aren't blocking copilot.cloud.microsoft or the Copilot app. Interactive content can fail in ways plain text won't if part of the path is filtered.
- Revisit data governance. Interactive apps built on live data make oversharing easier to see. If a user can open a dashboard of numbers they shouldn't have access to, that's a permissions problem App Blocks exposed, not one it created.
- Plan for the lack of a licensing answer. Microsoft hasn't said whether App Blocks needs a Copilot licence, or whether unlicensed Copilot Chat users will get any of it.
Static answers become interactive apps
App Blocks fits a wider industry shift: AI chats are starting to return small working apps instead of paragraphs. A loan calculator you can adjust is more useful than three paragraphs explaining amortisation, and a comparison tool beats a bulleted list of pros and cons.
There are reasons to be cautious, though. An interactive interface looks authoritative. If a simulation is built on generated assumptions rather than code-rendered business data, the polish can make it look more reliable than it is. Microsoft's SPFx team addresses this by keeping "the facts" in deterministic code. The App Blocks entry hasn't said whether generated apps get the same protection.
Developers can build with SPFx 1.24 preview today. Admins should wait for the Message Center post, the licensing details and the tenant controls before announcing anything to users.