# Power Platform support [Read the public page](https://www.adarkcloud.com.au/services/power-platform) Perth Power Platform support with Australia wide remote help. Scope Power Apps, Power Automate, Power Pages and reporting around data and licences. Power Platform support establishes the task, data and ownership behind a Microsoft app, automation or portal. We can review an existing solution or scope new work, with a specialist implementation agreed where the project needs it. 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 - Existing app and flow investigation - Business process and data requirement review - Licensing and environment dependencies - Test scope, ownership and specialist handover A flow runs when its author tests it but fails for everyone else. An app captures job details without giving staff a useful way to correct them. The visible screen is only part of the design. We provide a Perth based starting point for Power Platform work, with remote help across Australia. Separate service pages cover Power Automate, Power Apps and Power Pages in more detail. ## Begin with the work the product must support Take one recent job and describe its inputs, decisions and required result. A request for a new app may reveal a missing approval or inconsistent data rather than a software gap. We review the process before recommending a particular Power Platform product. A smaller configuration change may be enough to address the immediate issue. ## Choose the product against the audience Power Apps can support an internal business application. Power Automate handles defined workflows and connections. Power Pages provides a path for an external website or portal with business data. Reporting has its own data and access requirements. We establish who needs to use the result and where it belongs before deciding the implementation approach. ## Check use rights and operating cost Power Platform licensing depends on the features, users and data connections involved. Some Microsoft 365 plans provide limited rights, which should not be assumed to cover a proposed solution. The feasibility review should identify additional subscriptions or capacity. Actual usage and support also matter when comparing the solution with a simpler existing tool. ## Use data the business can account for Identify the source records, required fields and person responsible for their quality. Access should match the task. Moving bad records through an app faster will still produce bad records. We include duplicate handling, corrections and relevant permissions in the brief. Sensitive data needs an agreed location and handling method. ## Test exceptions alongside normal work A successful demonstration does not establish how a solution behaves when a field is missing, a connection fails or its owner leaves. Agree on acceptance checks using appropriate test records. Larger builds, custom integrations and specialist reporting can be discussed with VibeZero. The project scope should state which business is responsible for each part. ## Give the solution an operational owner The handover should explain the environment, accounts and recurring costs. A person needs to know how to detect a fault and who can make a change. Documentation should cover dependencies and how to stop the solution safely. Maintenance and further development need their own agreement rather than being implied by the initial build. ## Common questions ### Is every Power Platform feature included in Microsoft 365? No. Use rights vary with the product and design. We check users, data sources and features before scoping a solution. ### Can you help with an existing app or flow? Yes. We can review ownership, access and the failing behaviour before discussing repair or specialist work. ### Do you support Power BI requirements? We can help establish the reporting question, data and access needs. Larger reporting work can be scoped with an appropriate specialist, including VibeZero. ### Can we begin with a requirements review? Yes. A defined task and cost review can establish whether a build is useful before development begins. ## Useful next steps - [Power Automate](https://www.adarkcloud.com.au/services/power-automate) - [Power Apps](https://www.adarkcloud.com.au/services/power-apps) - [Power Pages](https://www.adarkcloud.com.au/services/power-pages) - [AI agents](https://www.adarkcloud.com.au/services/ai-agents) - [Reporting guide](https://www.adarkcloud.com.au/blog/why-your-business-reporting-is-a-mess) - [Microsoft Power Platform licensing guidance](https://learn.microsoft.com/en-us/power-platform/admin/pricing-billing-skus) 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)