Moving from trial to production

When working with Microsoft Power Pages, many users start with a trial environment to explore capabilities, build prototypes, or test features. However, once your portal is ready for real-world use, it’s essential to move from a trial setup to a full production environment. This ensures stability, scalability, compliance, and security.

Here’s a detailed step-by-step guide (approx. 1000 words) explaining how to properly migrate your Power Pages site from trial to production.

---

1. Understand the Difference: Trial vs. Production

Feature	Trial Environment	Production Environment
Duration	Expires after 30 days	No expiry (based on licensing)
Capacity	Limited storage and users	Scalable based on license
Licensing	Free for evaluation only	Requires Power Pages, Dataverse, or Dynamics
Use case	Prototyping, learning	Real-world usage, go-live scenarios

Moving to production is more than just copying content — it’s about compliance, scalability, and long-term availability.

---

2. Purchase the Right Licensing

Before migrating, make sure you have the correct Power Pages license.

A. License Options

• Authenticated users: Based on per-login or per-user license
• Anonymous users: Based on page views
• Dataverse Capacity: Included in paid environments or can be purchased separately

B. Purchase Steps

1. Visit Microsoft 365 Admin Center
2. Go to Billing > Purchase services
3. Search for Power Pages and select a plan
4. Assign licenses to the environment where you plan to host your portal

---

3. Create a Production Environment

Use the Power Platform Admin Center to create a clean production environment.

Steps:

1. Go to https://admin.powerplatform.microsoft.com
2. Click on Environments > + New
3. Select:
   • Environment type: Production
   • Region: Same as your trial (for easier migration)
   • Dataverse: Enabled
4. Name the environment (e.g., “CustomerPortal-Prod”)

This production environment will host your live Power Pages site.

---

4. Export Your Trial Solution

In your trial environment, create and export a solution that contains all relevant portal components.

A. What to include:

• Web Pages
• Web Files
• Templates
• Web Roles
• Entity Forms and Lists
• Site Settings
• Content Snippets

B. Export Process:

1. Go to Power Apps > Solutions
2. Create a new unmanaged solution
3. Add all portal-related components
4. Click Export, choose unmanaged or managed format
   • Managed: Ideal for production (read-only structure)
   • Unmanaged: Ideal for further editing

Save the exported .zip file.

---

5. Import Solution into Production

Now move your exported portal components into the production environment.

Steps:

1. Go to Power Apps > Environments > [Your Production Env]
2. Navigate to Solutions > Import
3. Upload your solution .zip file
4. Resolve any missing dependencies (if prompted)
5. Publish all customizations

Your portal structure and logic will now exist in the production environment.

---

6. Reconfigure Site Bindings

Site bindings connect your portal to a domain and make it accessible.

In Production:

1. Go to Power Pages > Sites
2. Select your site
3. Choose Set up and configure custom domains, authentication, and SSL certificates
4. Use your own domain (e.g., portal.yourcompany.com)
5. Update DNS settings as per Microsoft documentation

---

7. Migrate Data (If Needed)

If your portal uses Dataverse tables for storing data (e.g., user feedback, registrations), migrate this data too.

Options:

• Excel Export/Import: Export data from tables in the trial, import into production
• Configuration Migration Tool: For structured, schema-based data movement
• Power Automate: Create flows to copy/move data between environments

---

8. Test Everything Thoroughly

Before going live:

• Validate site navigation
• Test all forms and lists
• Check user permissions and web roles
• Test authentication and login scenarios
• Confirm responsive design on multiple devices
• Verify domain binding and SSL

Perform user acceptance testing (UAT) with stakeholders.

---

9. Decommission the Trial Environment

Once the production portal is running successfully:

1. Inform users to stop using the trial environment
2. Disable trial login access
3. Export a final backup of the trial environment (just in case)
4. Let the environment expire or delete it manually via Admin Center

---

10. Set Up Monitoring and Maintenance

In production:

• Enable Application Insights: To track performance and logs
• Set up portal usage analytics
• Configure alerts for errors or high traffic
• Schedule regular backups and include in ALM pipeline

This ensures that your live portal remains healthy and scalable.