Power Pages
Power Pages 2026 Release Wave 1: Security and Maker Updates
Power Pages 2026 release wave 1 includes new security, administrative and maker functionalities. This article explains how Power Pages supports authentication, Power BI embedding, server-side extensibility, AI coding, and planned monitoring functionality. It concludes with a useful checklist portal administrators should review before making any changes.
Portal change needs a security lens
Power Pages sites often expose business processes to customers, suppliers, partners or citizens. That makes release planning a security and service-management activity, not only a maker experience.
The Power Pages 2026 release wave 1 plan includes features expected to be released between April and September 2026. Some features are in general availability (GA), while others are still in preview. Please note that these dates may vary. The Microsoft Power Platform 2026 release introduces updates designed to improve security, administration and the maker experience.
Notable areas in Power Pages 2026 release wave 1
Authentication assistance: configuration that includes a security agent entered public preview on 30 April 2026 and will become available in August 2026. However, the teams will need to analyse the configuration and test all the supported sign-in paths.
Power BI embedding: embed token v2 support became available on 15 July 2026. Review report access, token handling and whether embedded content could reveal information beyond the portal user’s intended permissions.
Server-side extensibility: secure server-side logic reached general availability on 6 April 2026. This provides more development flexibility, but custom logic still requires code review, controlled deployment and appropriate monitoring.
AI-assisted development: AI coding tools for Power Platform 2026 release wave 1 reached general availability on 29 May 2026. Generated code can accelerate routine work, although makers remain responsible for its security, accessibility, maintainability and behaviour.
Planned administration controls: site analytics, server logging and threat detection are listed for public preview from September 2026. Granular controls for external authentication providers are also listed for preview in September, with general availability planned for November 2026.
Security principle
Compare the generated configuration and code against table permissions, web roles, identity flows, data exposure and the organisation’s secure development process. Automation can cut setup time, but it cannot know every business rule and regulation or how to share data. Teams should also review what is new in Dynamics 365 where connected data, permissions or processes could affect the portal.
A portal-owner rollout checklist
- Document authentication providers, web roles, table permissions and the business owner for each external-user journey.
- Test changes using representative external accounts, not only maker or administrator accounts. Include failed sign-ins, expired invitations and attempts to access unauthorised records.
- Review custom JavaScript, Liquid templates, APIs and server-side logic for input validation, excessive privileges, exposed secrets and unsupported dependencies.
- Confirm monitoring, logging, incident ownership and data-retention requirements. Decide who reviews alerts and how to escalate security or availability issues.
- Use staged deployment and regression tests for high-volume or regulated portals. Keep a rollback route and record the evidence required for approval.
- Recheck accessibility, mobile behaviour and performance after changes.
Incorporate the checklist into the regular change control process, not just as a point-in-time release task. Journeys that handle sensitive data, record creation or modification, payment collection, or large external user groups should take priority. Review these higher-risk journeys after significant platform, security or business-process changes. Keep evidence of each review, including test results, approved decisions and any remaining risks.
Official source
Checked 5 August 2026: Microsoft Learn — what’s new and planned for Power Pages, 2026 release wave 1.
Turn the guidance into a practical next step.
Use the article as a starting point for a focused review of your portal, security controls and release process. Bring representative user journeys, current constraints and the outcome you want to improve. Record gaps, agree on priorities, assign an owner and set a target date for each action before introducing new capabilities into production. Revisit the action plan regularly to confirm that agreed improvements have been completed and remain effective.