Power Platform: Add Custom Code to Apps

Key insights

• Power Apps Code Apps: A new capability shown in a community demo (September 17, 2025) that lets developers build, test, and deploy full custom-code applications directly inside the Power Platform.
  It brings traditional coding into the low-code environment so teams can combine custom logic with platform services.
• Native hosting & governance: Code apps run natively in the Power Platform and follow built-in security, data loss prevention, and sharing rules.
  Admins enable the feature per environment and the platform enforces access, consent dialogs, and conditional access policies.
• Licensing & connectors: End users need Power Apps Premium licenses to run code apps, and apps can use the platform’s connector ecosystem to access data across services.
  This removes the need for separate infrastructure while keeping enterprise integrations available.
• Developer toolchain: Developers use familiar tools like Visual Studio Code, Node.js, and the Power Platform CLI to code, debug, and deploy apps.
  The workflow supports local development, previews, and seamless deployment into managed Power Platform environments.
• Performance, scale & control: Code apps give full control over application logic and performance, enabling complex, enterprise-grade solutions that scale beyond pure low-code limits.
  The platform handles hosting, monitoring, and lifecycle management so teams focus on features and reliability.
• AI-assisted development & community resources: Microsoft integrates AI tools (for example Copilot Studio) to speed coding, testing, and app maintenance, and the community publishes samples and demos to help adoption.
  Start by enabling the environment setting, use official docs and sample repos, and join community calls or demos to learn best practices.

Introduction

Microsoft released a recorded demo that explains how developers can embed custom code inside the Power Platform. The presentation, delivered during a Power Platform community call on 17 September 2025, shows the new capability called Power Apps code apps. In plain terms, the demo illustrates how teams can build, test, and deploy fully coded applications directly within the platform instead of hosting them separately. Consequently, this marks a shift toward more flexible, integrated development within Microsoft’s low-code environment.

What the Demo Showed

The presenter walked viewers through the end-to-end workflow for creating a custom web application and running it inside a Power Apps canvas. He demonstrated development using common tools and sample repositories that were prepared to speed adoption, while also showing how apps appear and behave inside the Power Apps runtime. Moreover, the demo highlighted built-in lifecycle features such as deployment previews and runtime health metrics that administrators can use to monitor apps. As a result, viewers could see both developer and administrator perspectives in a single session.

Technical Details and Requirements

The session clarified that code apps run natively within Power Apps and rely on environment settings that administrators control. End users will typically need premium licenses to access these apps, and developers can use familiar tooling like Visual Studio Code and standard server runtimes during development. Additionally, the demo emphasized compatibility with the existing connector ecosystem, including support for OpenAPI v3 and integration with PowerFx logic, allowing custom code to work alongside low-code components. Therefore, organizations can combine traditional coding practices with the platform’s governance and connector model.

Tradeoffs in Design and Deployment

The new approach brings advantages but also introduces tradeoffs that teams must weigh carefully. On the one hand, developers gain full control over application logic and can deliver more complex and performant solutions than low-code-only options allow. On the other hand, adding fully coded apps increases responsibilities around testing, dependency management, and runtime security, so teams must adopt stricter development practices. Consequently, organizations should balance the flexibility of custom code against the operational overhead it creates.

Challenges and Governance Considerations

Running custom code inside a managed platform raises several governance challenges that the demo addressed only in part. Administrators must configure policies and environment settings to enforce data loss prevention and conditional access while still enabling developer productivity. Moreover, troubleshooting custom apps requires different skills than classic low-code monitoring, so teams may need to expand their operational capabilities and adjust center-of-excellence practices. In short, the feature provides power but demands stronger coordination between developers, security, and IT governance.

AI Integration and Developer Productivity

During the demonstration, Microsoft also showcased how AI-assisted tools can accelerate development and maintenance, with features from Copilot Studio and other AI services mentioned as productivity helpers. These tools can assist in code generation, testing, and diagnostics, which reduces routine effort and helps teams iterate faster. However, dependence on AI assistance introduces its own considerations: teams must validate AI outputs carefully and maintain human oversight to prevent logic or security gaps. Thus, AI can be a force multiplier when combined with disciplined review processes.

Community Resources and Adoption Path

Microsoft and contributors have published samples and tooling to help developers get started, and the demo referenced repositories that include templates and guidance. Consequently, early adopters can experiment with examples before rolling out code apps in production environments, which helps surface integration issues and governance needs early. Meanwhile, community calls and documentation continue to evolve, offering a route for teams to learn and share best practices. Therefore, a staged adoption path will likely reduce friction and improve outcomes for organizations.

Implications for Teams and Next Steps

For development teams, the feature offers a new way to bridge low-code and pro-code workstreams, enabling closer collaboration with citizen developers and administrators. Yet, teams must invest in testing, dependency control, and monitoring to ensure reliable operation at scale. In practical terms, organizations should pilot the capability in a controlled environment, adjust licensing and governance policies, and train operations staff on new diagnostics and lifecycle tooling. Ultimately, this feature broadens options for enterprise application delivery while requiring intentional process and tooling updates.

Conclusion

The recorded Microsoft demo presents a clear direction: embed custom code into the Power Platform to gain flexibility without abandoning the platform’s governance and connector capabilities. While the approach simplifies infrastructure management by hosting code apps inside Power Apps, it also shifts responsibility for code quality, security, and operations onto teams. Therefore, organizations should evaluate both benefits and tradeoffs, adopt a phased rollout, and use available resources to align development practices with platform governance. As the community and tooling mature, the balance between low-code ease and pro-code control will continue to evolve.

Keywords

Power Platform custom code, Power Apps custom code, Power Platform extensibility, Power Automate custom connectors, Power Fx custom functions, Azure Functions Power Platform integration, custom connectors Power Platform, bring custom code to Power Platform