Launching a Power Pages site for a government, aged care, or enterprise audience carries obligations that go well beyond functional testing. External portals that serve residents and citizens expose Dataverse data to the public internet, so any gap in table permissions, caching behaviour, or accessibility conformance becomes a direct risk to the organisation and the people it serves. A structured pre-launch health check gives project sponsors confidence that the portal is defensible under scrutiny before it ever handles a real enquiry.
This article sets out a practical audit routine across three dimensions that frequently determine whether a portal passes review: security of data access, performance under load, and conformance with the Web Content Accessibility Guidelines. The intent is to give technical teams and decision makers a shared checklist they can apply consistently. Treating go-live as a controlled gate rather than a deadline reduces the likelihood of remediation after launch, when fixes are costlier and more visible.
Power Pages sits on top of Dataverse, and the security model relies on web roles, table permissions, and column level controls working together. The most common failure is an overly permissive table permission that grants global access where account or contact scoped access was intended, which can expose records belonging to other users. Before go-live, teams should enumerate every table surfaced through lists, forms, and web APIs, then confirm the access scope, the web roles it applies to, and whether create, read, write, and delete privileges are each genuinely required. Anonymous access deserves particular attention, because any table permission assigned to the anonymous role is reachable without authentication.
Beyond table permissions, the audit should verify that page permissions align with the sensitivity of each page and that site settings do not inadvertently disclose diagnostic information. Authentication configuration warrants review, including the identity providers in use, session behaviour, and whether Azure Active Directory B2C or another provider enforces the expected sign in policies. It is also prudent to confirm that the portal does not expose Dataverse metadata or unfiltered web API endpoints, and that server side validation protects against submissions that bypass client side controls. Documenting these findings creates an evidence trail that supports later security assessments and accreditation activities.
Performance review protects the citizen experience and the stability of the underlying platform during peak demand. Power Pages caches server rendered content and Dataverse data to reduce latency, so the audit should confirm that caching is configured deliberately rather than left at defaults that may not suit the data freshness requirements of the portal. Pages that display frequently changing information, such as application status or appointment availability, need caching settings that balance responsiveness with accuracy. Teams should also review the use of Liquid templates, Fetch XML queries, and list filtering, because inefficient queries against large tables are a frequent cause of slow page loads.
Resilience testing should simulate realistic concurrent usage rather than relying on single user navigation. Reviewers can examine asset delivery, including image sizing, bundling of scripts and styles, and whether a content delivery approach is in place for static resources. It is worth confirming that error pages behave gracefully, that timeouts are handled, and that the portal degrades predictably if a dependent service becomes unavailable. Capturing baseline load times and query counts before go-live gives the team a reference point for monitoring the portal in production and for diagnosing regressions after future changes.
Accessibility is both a legal and ethical expectation for public facing government services, and it is often the dimension most heavily scrutinised after launch. Australian government guidance aligns with the Web Content Accessibility Guidelines, with Level AA commonly set as the baseline for public websites. The audit should combine automated scanning with manual testing, because automated tools detect only a portion of conformance issues and cannot assess context, reading order, or the usability of interactive components. Keyboard only navigation, screen reader testing, and verification of visible focus indicators reveal problems that automated checks routinely miss.
Power Pages generates much of its markup from templates and components, so reviewers should confirm that forms expose correct labels, that error messages are announced to assistive technology, and that colour is not the sole means of conveying meaning. Heading structure, alternative text for informative images, and sufficient colour contrast all require deliberate verification against the guidelines. Custom Liquid, scripts, and third party widgets can undermine conformance even when the base platform is compliant, so any bespoke component should be tested in its own right. Recording the outcome against each relevant success criterion produces documentation that supports an accessibility statement and demonstrates due diligence to reviewers.
A one off review is valuable, but portals evolve, and each content update or configuration change can reintroduce risk. Establishing the health check as a repeatable routine, triggered before every significant release, keeps security, performance, and accessibility aligned over the life of the service. Assigning clear ownership for each dimension, maintaining a documented checklist, and retaining evidence from each review turns ad hoc testing into a governable process that withstands audit.
Integrating these checks with existing change management and release practices reinforces accountability without slowing delivery. Where possible, teams can automate parts of the routine, such as accessibility scanning and permission reporting, while reserving manual effort for the judgement based testing that tools cannot replace. The result is a portal that organisations can defend with confidence, and a process that continues to protect residents and citizens long after the initial launch.

Level 7, 12 St Georges Tce
Perth WA 6000
[email protected]
Ph 1300 NOVATA

In the spirit of reconciliation Novata Solutions acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their Elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today. This land always was, and always will be Aboriginal Land.

Novata Solutions is committed to embracing diversity and eliminating all forms of discrimination through education. We welcomes all people and is respectful of individual identities.