# Power Pages support [Read the public page](https://www.adarkcloud.com.au/services/power-pages) Perth Power Pages support with Australia wide remote help. Scope customer portals and external business websites around access, Dataverse and cost. Power Pages support helps scope or review an external Microsoft business website or portal connected to Dataverse. We establish the audience, records and permissions before deciding whether the platform suits the requirement. Perth based, with remote support across Australia. From $79 an hour ex GST, with the fee agreed before work begins. Call Josh C on 0408 530 303. ## What we can help with - Portal audience and task requirements - Dataverse and environment review - Authentication and table access scoping - Capacity, test scope and specialist handover A customer needs to submit a request or view their own job information. That is a different requirement from publishing a brochure website or giving staff an internal app. Start with what the visitor must be able to do. A Dark Cloud Creative provides Perth based scoping and remote help across Australia. Implementation responsibilities and fees are agreed once the access and data requirements are clear. ## Decide whether a portal is needed A public information page may only need a conventional website. A visitor who must sign in and reach business records introduces a broader application requirement. We establish that distinction before recommending Power Pages. Use one visitor journey to explain the task. Include what they submit, what they can see and how staff respond. ## Review the records behind the website Power Pages works with business data stored in Microsoft Dataverse. The environment and records need to support the intended process. A portal should not become a separate place to maintain conflicting copies. We identify data ownership and the fields visitors need. Any required integration or migration belongs in the scope before pages are built. ## Define authentication and record access A signed in customer should only reach the information intended for them. Public forms, authenticated pages and administrator functions require different access decisions. The design must account for the underlying data permissions. Agree on user roles and account recovery. Relevant tests should include attempts to reach another customer’s records as well as ordinary successful use. ## Check capacity and subscription dependencies Power Pages has its own licensing and capacity considerations. User audiences, environments and connected features affect the operating arrangement. An existing Microsoft 365 subscription is not proof that a portal is covered. We document assumptions and required subscriptions in the feasibility review. The business should understand ongoing costs before accepting a development proposal. ## Test the complete visitor task A working sign in page does not prove the visitor can submit a request, correct an error or find the result. Test normal use and relevant failures with appropriate accounts and sample data. Larger portal builds can be scoped with VibeZero where appropriate. The acceptance brief should explain the expected result and each provider’s responsibilities. ## Plan updates and support after launch The handover needs to identify the environment, domain and operational owner. Include access changes, support contacts and how faults are reported. Content editing and data administration may have different responsibilities. Any ongoing arrangement should state its coverage and availability. A launch does not imply unlimited development or continuous incident monitoring. ## Common questions ### Is Power Pages the same as Power Apps? No. Power Pages is intended for external business websites and portals. Power Apps addresses business application requirements with a different audience and design. ### Do we need Dataverse? Power Pages uses Dataverse for connected business data. We review the required environment and records when scoping the portal. ### Can one customer be restricted to their own records? That must be designed and tested through the relevant authentication and data permissions. A signed in screen alone does not establish the restriction. ### Would a normal website be cheaper or simpler? It may be, if visitors only need public information or a basic enquiry form. We compare the requirement before recommending a portal. ## Useful next steps - [Power Apps](https://www.adarkcloud.com.au/services/power-apps) - [Website design](https://www.adarkcloud.com.au/services/web-development) - [Power Platform support](https://www.adarkcloud.com.au/services/power-platform) - [Microsoft guidance on Power Pages](https://learn.microsoft.com/en-us/power-pages/introduction) - [Microsoft Power Pages capacity guidance](https://learn.microsoft.com/en-us/power-pages/admin/capacity-management) Reviewed 2026-10-08 - [Ask for IT help](https://www.adarkcloud.com.au/contact) - [Check your IT basics](https://www.adarkcloud.com.au/tools/it-health-check)