Code Apps - Office Hours February 2026 Highlights

February 25, 2026

4 min read

Code Apps

Today, I attended the Power Apps Office Hours meeting that was hosted by Austin Laugesen. This was packed with some valuable insights. Here's a summary of the key updates and discussions

Latest News

The latest news is that a new node-based command-line interface has been released. This is currently in preview and the plan is to make this generally available in approximately one month. This node-based tool aims to reduce prerequisites for starting with Code Apps and improve compatibility with AI coding agents

The features in the new CLI match those that exist in the PAC CLI. An important point is that 'PAC Code' will be deprecated, so it's important to transition to the new CLI. There are details on how to get started with this here:

https://learn.microsoft.com/en-us/power-apps/developer/code-apps/how-to/npm-quickstart

The next piece of news relates to improvements in Copilot Studio Integration. Official documentation is now available for invoking agents, including support for conversational agents and asynchronous background agents. You can find details of this here:

https://learn.microsoft.com/en-us/power-apps/developer/code-apps/how-to/connect-to-copilot-studio

Finally, for help on working with Dataverse, a new Dataverse CRUD example app has been released to demonstrate how to carry out data operations.

Technical Questions and Answers

During this meeting, there were several insightful questions from attendees. Below is a recap of the topics covered and the answers provided.

Are many-to-many (N:N) Dataverse relationships supported in Code Apps?

Many-to-many relationships are currently officially unsupported. The team plans to update documentation to reflect this and has added it to the backlog to provide a confident implementation path in the future.

What is the best way to surface a Code App in an existing Model-Driven App (MDA)?

The only possible way now is via an iFrame, but it is "kludgy" because it lacks Single Sign-On (SSO) and shared authentication context. The team is exploring ways to streamline this scenario.

Does the SDK support $expand for retrieving related records?

Not currently. This functionality is tied to the broader relationship support currently in the backlog.

Will it be possible in the near future to retrieve the security roles or attributes on the Dataverse side?

Yes. This is a high-priority backlog item. The team aims to manifest this through an API in the SDK, potentially by the end of summer.

Do we have a date for Mobile Code Apps?

The team is targeting summer for mobile online support. They are currently seeking feedback on whether offline support is a "day-one" requirement for users.

What is the best way to insert an AI agent from Microsoft Foundry into Code Apps?

The team recommends using the connector framework. They took an action item to check when the current preview connector will reach GA. Alternatively, wrapping an Azure Function in a custom connector is a viable GA path.

Any plans for npm CLI / MCP server?

The team is focusing more on building internal plugins (specifically for Claude) to make coding agents more proficient at scaffolding and building apps. There are no immediate external commitments for an MCP server.

Does solution checker scan Code Apps for hard-coded sensitive values?

No, solution checker does not currently perform code scanning for Code Apps. The team is in the explorative phase to determine the best out-of-the-box scanning tools to offer.

Is there a broader announcement coming regarding GitHub support for native git?

Yes. While Code Apps currently work with Azure DevOps, a parallel investment is being made to enable GitHub as a provider for native git integration.

Is there any difference between Code Apps and the Vibe experience?

They use the same underlying infrastructure, SDK, and host. They also respect the same governance and licensing models.

Is the Code App source stored in Dataverse when published?

Historically no, but changes are being implemented so that the source code moves with the app package during ALM processes, rather than just the compiled assets.

Could we bring in Choices separately from a Dataverse column?

The team acknowledged this as a convenience feature that is relevant and will be added to the backlog, though foundational work must be completed first.

Conclusion

Today's Code Apps Office Hours was a highly informative event, packed with useful content from the Power Apps Team. It's great to see the progress that's currently being made in this space.