3 upcoming features available this month

Power Apps 2025 release wave 1

For previous release wave highlight videos:

For archived plans:

All
Features included in release plans: 26
Planned
Upcoming features included in release plans: 9
Coming soon
3 upcoming features available this month
Try now
Features released to market: 16
Filter by:
Sort by:

Status

Availability dates





Enabled For




Availability


Release wave


Share my release plan

Share link

People with the link can view your release plan

Share

Manage link

Click "Delete" to remove access to your release plan

Delete

Business Value

Makers can clean up their list of data sources and consolidate all of them into one. The new Manage feature for stored procedure data sources allows authors to add or removed stored procedures and keep the same data source name. So, all stored procedures are consolidated under one data source name.

Feature Details

Re-editing data sources with stored procedures will provide faster and cleaner development. When a maker creates data sources for an application, each editing session that selects stored procedures creates a new data source. This can make it difficult to keep track of which stored procedures are in each data source if multiple editing sessions create several data sources. This feature allows the author to simply "re-edit' an existing data source with stored procedures to add or remove stored procedures. As a result, all stored procedures can be managed under a single data source.

Enabled for:

Users, automatically
This feature includes changes to the user experience for users and is enabled automatically.
Change history
General availability date moved to Jul 2025 May 01, 2025
Timelines:
Early Access: ---
Public Preview: ---
General Availability : Jul 2025
Last updated: May 19, 2025
Included in:
2025 release wave 1
Enabled for:
Users, automatically

Business Value

With this feature, you can view the underlying code to understand app functionality and manage source control. It’s perfect for developers who need to align with healthy and robust Application Lifecycle Management (ALM) practices. By using this feature, you streamline your development process, improve code quality, and support your app’s growth.

Feature Details

You can now export a canvas app as a binary file with the extension .msapp. You can use Power Platform CLI to convert a .msapp file into source code files. With this feature, you no longer need to use the Power Platform CLI to convert the .msapp files. You can view the source code for the canvas app in an updated, human readable YAML format. Each screen has a separate file.

View the source code of your canvas app directly in Power Apps Studio or use external code editors.

This new capability helps you to:

  • Store the files in a code repository.
  • Automate generation of a canvas app.
  • Improve the generative canvas app models.
  • Refactor canvas apps without using the designer.
  • Integrate natively with Git for Power Platform.

Enabled for:

Admins, makers, marketers, or analysts, automatically
This feature is meant to be used by administrators, makers, or business analysts and is enabled automatically.
Change history
Public preview date moved to Aug 2024
General availability date moved to Aug 2024		 Aug 01, 2024
Timelines:
Early Access: ---
Public Preview: Apr 22, 2025
General Availability : Jul 2025
Last updated: Jun 10, 2025
Included in:
2025 release wave 1
Enabled for:
Admins, makers, marketers, or analysts, automatically

Business Value

Customers that use custom schema names in the same database to partition their database for dev, test, and prod can now use environment variables to save time when deploying their application from dev to test and to prod. Rather than manually dropping and re-adding data sources between dev, test, and prod, authors can use environment variables to speed up the transfer between these environments.

Feature Details

Many customers use schemas for DEV, TEST, and PROD to manage Application Lifecycle Management (ALM). To access a table, you must specify the schema explicitly, as the default "DBO" schema cannot be assumed. This requires a four-part reference: server, database, schema, and table.

For example:

<myserver>/<mydatabase>/<DEV>/<mytable>

versus

<myserver>/<mydatabase>/<PROD>/<mytable>

Current SQL environment variables only support server and database, assuming separate databases for DEV and PROD, making four-part references impossible. This feature allows specifying the schema as an environment variable. Power Apps binds to specific table names, which must remain consistent across environments, though schemas may vary. This feature enables customers using schemas for DEV, TEST, and PROD to utilize SQL environment variables in their applications.

Enabled for:

Users, automatically
This feature includes changes to the user experience for users and is enabled automatically.
Note:
  • The author created this article with assistance from AI. Learn more
Change history
Timelines:
Early Access: ---
Public Preview: ---
General Availability : Jul 2025
Last updated: May 19, 2025
Included in:
2025 release wave 1
Enabled for:
Users, automatically