Microsoft’s Power Apps is being positioned by its owners and professional services partners as a practical route to faster, cheaper digital solutions created by frontline staff — but businesses must decide how to govern and maintain those tools, industry voices say.
Employees build, IT supervises
On a recent industry podcast, the platform’s general manager for Power Apps and EY’s business applications lead for the Americas set out a shared view: the low-code service empowers subject-matter experts to produce departmental apps that solve specific problems, while professional developers and IT teams remain central to ensuring stability, compliance and scalability.
The argument reframes the debate about so-called "citizen developers." Rather than cutting IT teams out, Power Apps is presented as a way to relieve the backlog of requests that can arise when a small IT group is expected to deliver an expanding set of digital changes across an organisation.
Practical takeaways for firms
From the podcast transcript and commentary, several practical considerations emerge for companies adopting low-code platforms:
- IT oversight is essential: technology teams must still check that simpler apps use secure and maintainable building blocks.
- Monitoring and support: organisations should track how employees use the tools and identify where support or escalation is needed.
- Governance and lifecycle: firms must define when a custom-built app is appropriate, and who will manage it after launch.
Those items reflect a broader corporate reality: enabling more people to create software can raise productivity and responsiveness, but without rules and resource planning it risks sprawl, duplication or security gaps.
Where low-code fits in a company’s stack
Speakers described Power Apps as suited to less complex use-cases where a departmental owner understands the problem and can assemble a fit-for-purpose solution. More sophisticated or enterprise-critical systems still require professional developers, robust architecture and often, significant investment.
| Use-case | Who builds | IT role |
|---|---|---|
| Simple departmental workflow | Subject-matter expert using low-code | Governance, security checks |
| Complex, enterprise solution | Professional developers | Architecture, scaling, long-term support |
Implications for IT teams and business leaders
The discussion underlines a shift in how business change gets delivered. Rather than all new tools passing through a central IT pipeline, firms may adopt a hybrid approach where business teams launch targeted apps backed by IT policies and escalation paths.
For IT departments this means stepping away from being the sole builders and towards roles that include: policy design, monitoring usage, and curating templates and best practices. The podcast stressed that such teams remain vital to avoid solutions that are brittle or risky.
Executives face choices about procurement and support. The guidance on offer encourages decision-makers to ask not just "can this be built faster?" but also "how will it be governed over time, and who maintains it after deployment?" Those answers determine whether low-code investments deliver sustained value or create ongoing technical debt.
The full transcript of the podcast is available from the host for those seeking more detail on the platform’s role in boosting organisational agility.
Bottom line: Power Apps can unlock employee-led innovation and help firms move faster, but only if companies pair the capability with clear governance, oversight and a plan for maintenance — otherwise the short-term gains risk becoming long-term headaches.
