Greetings!
Thanks for raising this question. Power Pages supports selective deployment of changes (e.g., 2-3 pages) without full republishing via solutions or deployment profiles, allowing patch-like updates to production while preserving existing content. This uses Dataverse packaging for precise control—full deploys take 10-30 mins, but targeted ones complete in 1-5 mins. Here's the short setup (assuming enhanced data model; standard model uses profiles).
Method 1: Solutions (Recommended for Precision)
1. In Dev Environment (Power Apps Maker Portal):
- Go to make.powerapps.com > Solutions > New solution > Name: "PageUpdatesOnly" > Add existing: Your site (adx_website record).
- Add only changed components: Pages (adx_webpage for your 2-3 pages) > Web templates/forms if modified > Site settings (if any) > Publish all customizations.
2. Export Solution:
- Select solution > Export > Unmanaged (for dev) or Managed (for prod) > Advanced: Include "Site" > Export as ZIP.
3. Import to Production:
- In prod maker portal > Solutions > Import solution > Upload ZIP > Install (default settings) > Configure: Skip if no prompts > Import.
- Reactivate site: Power Pages > Sites > Your site > Sync configuration (refreshes only changes).
4. Verify: Browse prod site—only updated pages reflect changes; rest unchanged.
Method 2: Deployment Profiles (For Standard Model/Simpler)
- Power Pages Studio (dev) > Settings > Deployment profiles > Create profile > Select components (pages, templates) > Save.
- Export profile > Import to prod profile > Apply (merges changes selectively).
- Sync config in prod site settings.
Tips
- Changes: Limit to adx_webpage/adx_webtemplate records—avoids overwriting unrelated.
- Automation: Use Power Platform CLI (`pac solution export/import`) in CI/CD for pipelines.
- Rollback: Export before import; solutions are versioned.
- Limits: 100 components max per solution; test in staging first.
This deploys patches efficiently start with solutions for your scenario. If it helps accept this answer and support the community.
Best Regards,
Jerald Felix