Power Platform Administrator
Confirmed on the employer's own hiring board on Nov 4, 2026. First seen by Alion on Oct 26, 2026.
About TQA
TQA is the Agentic AI Experts. We’re an international technology services and consultancy, partnering with enterprises across North America and Europe to deliver next-generation results through emerging technologies. We’re expanding rapidly in 2026 and beyond, and we offer an accelerated career path, work on advanced projects and the chance to grow into leadership roles quickly.
About the Role
Most of our clients adopted Power Platform faster than they governed it. Nobody is sure what is deployed, who owns it, what it can reach or what it will cost. As a Power Platform Administrator, you make the platform safe to scale inside our clients’ tenants: sensible environments, data policies that hold, and capacity and licensing that surprise nobody.
This is a client-facing operator role, not a build role. You run environment governance, data policy and the platform day to day, Copilot Studio agents included, across several client estates. You diagnose apps, flows and agents; you don’t build them. You execute a governance model independently and contribute to its design, while tenant-wide design and licensing strategy stay with our Solution Architects.
Key Responsibilities
Strategy and plan: contribute evidence from the estate to each client’s governance model, forecast license, capacity and Copilot Credit needs, and flag platform changes that will cost money or break things.
Environments and capacity: implement environment topologies, contain the default environment, configure Managed Environments and environment groups (settling the licensing consequence first), run backup, restore and recovery safely, and watch Dataverse capacity before it runs out.
Data policies, access and security: maintain a defensible DLP baseline, fix DLP-driven failures in live solutions, govern what Copilot Studio agents can reach, manage access (Entra groups, Dataverse security roles, least-privilege service principals) and configure tenant isolation.
Monitoring and automation: configure Dataverse auditing and Purview logging, keep an inventory of apps, flows and agents with named owners, track Message center and deprecations, investigate incidents to an accepted root cause, and automate administration with PowerShell, pac CLI or the Power Platform API.
Support and enablement: provide second and third-line support, onboard makers and agent authors, run Pipelines from the admin side (you govern promotion, you don’t build what’s promoted), and write runbooks and handover documentation clients can operate from.
Required Skills and Experience
Everything below is assessed on demonstrated experience.
Governance you’ve built and operated: [4+] years hands-on with Power Apps, Power Automate and Dataverse, including [2+] years where administration and governance was your primary responsibility.
Independent client delivery: you’ve implemented and run a governance model end to end and defended your recommendations.
Environment strategy and Managed Environments: including the rule that every active user in a managed environment needs a premium license.
Data policy design and troubleshooting: precedence, unblockable connectors, predicting what a classification change will break, and fixing a live solution a policy has stopped.
Copilot Studio agent governance through generally available controls (agent data policies, knowledge-source rules, sharing limits, maker credentials, credit allocation). Building agents is not part of the role.
Security and access: Entra security groups, Dataverse security roles, admin role scoping, least-privilege service principals.
Licensing and capacity to a client-facing standard, including Copilot Credits and Dataverse capacity. You don’t quote a figure you haven’t re-checked.
Monitoring, audit and change: Dataverse auditing, Purview activity logging and Message center.
Scripted administration with PowerShell, pac CLI or the Power Platform API, using service principal authentication.
Deployment operations: solution ALM discipline and Pipelines from the admin side.
Enterprise controls (reasoning, not necessarily hands-on): IP firewall, customer-managed keys, Customer Lockbox and virtual network support.
Communication: clear English, credible with both a platform engineer and a finance stakeholder, and able to say no to a connector request while offering a workable alternative.
Nice to Have
Advanced connector policies, Microsoft 365 Copilot and agent administration, Microsoft Agent 365 or Entra Agent ID, Sentinel or Purview beyond the audit log, the CoE Starter Kit or ALM Accelerator at scale, CI/CD beyond Pipelines, regulated-sector experience, Dynamics 365 administration, and Azure adjacency (identity, networking, cost management).