Answered

Power Page - Life Cycle Management

(1) Share

Report

Posted on by DahPower

Hi Commuinty!

So, I have built my first Power Page in a sandbox environment that we use for development and now I want to deploy it to a test environment and share it with test users before deploying it to the production environment. I am using the enhanced datamodel and expect to do the migration via a solution as per msft. documentation here.

What I am having some trouble with understanding is converting the site from trial to production. Since I created my site in a sandbox environment, the site will expire after 90 days, and then after another 7 days be deleted. However, I don't want this to happen, since I will use the dev environment to implement changes and update to the site before migrating it to either test or prod. I expect this will apply to the test environment as well once I migrate it there.

So my question is, do I need to convert my Power Page site in dev and test to production to avoid them being deleted in the future? I can't seem to find any clear documentation around this and from msft. documentation this seems to be the only option. But is it even possible to have the same site as production accross multiple environments?

Thank you for your support! :)

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

SaiRT14 1,990 Super User 2025 Season 2 on at

Like (0)

Report
Trial vs. Production Power Pages Sites

To prevent deletion, you’ll need to convert the trial Power Pages site to a production site.

Microsoft recommends using solutions to migrate Power Pages sites between environments

Separate Sites for Dev, Test, and Prod:

Keep individual Power Pages sites for dev, test, and prod environments.

Convert each site to a production site in its respective environment to avoid expiration.

Automate Solution Management:

Use ALM (Application Lifecycle Management) tools like Power Platform Build Tools to automate solution export/import and deployment between environments.

Was this reply helpful? Yes No
DahPower 6 on at

Like (0)

Report
Hi SaiRT14,

Thank you for your reply!

So, just to be clear, I would have to follow the steps:

Convert my Power Page site in dev to production to avoid expiration.

Deploy the solution with my Power Page and its components to the test environment (it remains as a production site I assume?).

After testing, then I deploy the site to production where I publish it.

After that I guess it works like any other managed solution, where you implement updates in dev and deploy it to e.g. production where the changes are then published with the latest version. :)

Correct?

Was this reply helpful? Yes No
Verified answer

dax1232 36 on at

Like (1)

Report
Hi,

Yes, you need to convert it to production to avoid deletion. Converting it to production also means that the website is now publicly available.

When you import a site using solution in another environment for the first time, the environment is imported as an inactive website. In your maker you can activate the website where it will ask you for a new URL for the website. You will need to convert it to production too.

You can deploy updates to the website using managed solutions. As a best practice I always Purge cache from the admin portal for the website when I import updates.

Was this reply helpful? Yes No