Find the insights and best practices about our product.
Publishing to Power Apps
Publishing pages and page groups directly into Power Apps — as a Web Resource embedded in a D365 solution, or as a runnable App.

Publishing to Power Apps

The Power Apps tab of the Publish side panel deploys your page or page group directly into your Microsoft Power Platform tenant. You get two delivery modes — embed it as a Web Resource inside an existing D365 solution, or publish it as a top-level runnable App.

Choosing a Target Solution

The Power Apps tab starts by asking for a Target Solution — the Power Platform solution that will own the new artifact. Pick from the dropdown (e.g., Default Solution, or any unmanaged solution your account has access to in the current environment).

Publish Web Resource

Choose Publish Web Resource to deploy an HTML web resource into your D365 solution. Use this when you want to:

  • Embed an EasePage dashboard inside a D365 form or sitemap
  • Reuse the page across multiple solutions/apps without managing a separate URL
  • Inherit your D365 environment's security model (the web resource respects D365 row-level / table-level security)

Publish as App

Choose Publish as App to create a runnable Canvas / Model-driven app entry. Use this when the page or page group is a standalone destination — its own tile in the Power Apps app launcher.

Page Group Publish Tab

Page Groups expose the same publish controls, plus a Manual Export → Download HTML button that bundles the whole multi-page app as a single HTML file you can host anywhere.

The Publish tab with Manual Export and Publish to Power Apps options.

Figure 12.5a — Page Group Publish tab.

Publish tab with Default Solution chosen; Cal Group 2 already shows a Live v1.0 badge.

Figure 12.5b — Default Solution chosen; live version visible behind.

Tips

  • Web Resource vs. App: Web Resource for embedding inside D365 sitemaps; App for top-level Canvas / Model-driven entry.
  • Pick an unmanaged solution as your Target Solution if you plan to edit the artifact later inside Power Apps Studio.
  • Re-publishing overwrites the existing Web Resource / App in the chosen Target Solution; old versions remain in EasePage's Version History.