Senior Consultant - Power Platform CoE, ALM & Copilot Studio

The role in one sentence Lead the Power Platform Center of Excellence and Application Lifecycle Management lane of a 90‑day governance engagement that turns a Fortune‑class regulated enterprise’s unmanaged Power Platform and Copilot Studio estate into a governed, observable, ROI‑tracked capability — and convert into a PTM Fusion full‑time hire on successful delivery. Why this role exists Proactive Technology Management (PTM) Fusion has committed to a 90‑day governance program for a Fortune‑class regulated enterprise client. The program has two delivery lanes running in parallel – Power Platform / Copilot Studio CoE & ALM and Microsoft Purview / M365 Compliance . This posting is for the Power Platform lane. The engagement runs in two phases: Phase 1 — Discovery & Assess (30 days). Inventory and risk‑rank the estate (apps, flows, agents, environments). Map current ALM, identity, and CoE Kit posture against PTM and Microsoft baselines. Quantify Copilot Studio agent exposure, observability gaps, and maker behavior. Deliver a prioritized governance backlog with measurable ROI. Phase 2 — Implement & Govern (60 days). Stand up the CoE Kit, environment strategy, and Power Platform DLP. Wire Application Lifecycle Management (ALM) pipelines for both makers and pro‑developers. Operationalize Copilot Studio agent governance – authentication, content moderation, audit. Light up an Azure Monitor and Log Analytics observability surface tied to the agreed value metric. You will work in lockstep with a Microsoft Purview / M365 compliance specialist who owns the data classification, DLP, retention, and Purview‑for‑Copilot side. The two lanes share a Solution Architecture Document, a milestone roadmap, and a value metric – so coordination matters. What you’ll deliver A risk‑ranked inventory of every app, flow, agent, and environment across the client tenant, with a connector‑usage analysis that informs DLP scope. A current‑state assessment of ALM, identity, environment strategy, and CoE Kit posture, mapped to PTM and Microsoft reference architectures. A prioritized governance backlog with one‑line ROI rationale per item, ready to drive Phase 2 scope confirmation. A deployed and operating Power Platform CoE Kit with environment strategy, tenant‑ and environment‑level DLP policies, connector classification rationale, and maker‑onboarding flow. ALM pipelines (Power Platform Pipelines or ALM Accelerator + GitHub Actions / Azure DevOps) serving both citizen‑developer and pro‑developer paths – solution layering, managed solution promotion, source‑controlled artifacts, and gated environment promotion. Dataverse design uplift where needed: security roles, table and relationship design, plug‑in patterns, business rules, and auditing posture. Copilot Studio agent governance – authenticated Entra‑bound knowledge sources, content controls, audit logging, and red‑team review of high‑exposure agents. Coordination with the Purview lane on DSPM‑for‑AI configuration. Azure Monitor and Log Analytics observability – diagnostic settings on Power Platform, Dataverse, and Copilot Studio, KQL workbooks for maker activity, app and flow health, and agent usage, alert rules on policy drift, and an executive Power BI dashboard reporting against the value metric agreed during Discovery. Solution Architecture Document (SAD), Solution Design Document (SDD), and milestone roadmap authored against PTM templates and reviewed under our Maker‑Checker discipline. Who you are You can hold a discovery conversation with a Chief Information Officer in the morning, run an Event Storming session with a finance director after lunch, and ship a Dataverse security‑role design before dinner. You communicate in plain language to business owners and in precise technical terms to engineers, often in the same meeting. You believe governance is a value engine, not a brake. You measure success in ROI delivered, not artifacts produced. Power Platform CoE & ALM (depth required) 5+ years delivering on Microsoft Power Platform in enterprise or mid‑market environments, with at least 2 full lifecycles of CoE Kit deployment and operation. Power Platform Center of Excellence Kit – deployment, configuration, customization, and ongoing operation of the inventory, audit, telemetry, and nurture components. Power Platform ALM – solution layering, managed solutions, environment strategy, and Power Platform Pipelines or the ALM Accelerator . CI/CD integration with GitHub Actions or Azure DevOps – solution checker, automated test, source‑controlled solution artifacts, gated promotion, and rollback patterns. Power Platform DLP policies – connector classification (Business / Non‑Business / Blocked), tenant‑vs environment‑level scoping, endpoint filtering for and SQL connectors, and custom connector handling. Environment strategy – environment types, capacity management, sandbox / production discipline, and Dataverse‑vs‑default‑environment routing. Dataverse & Copilot Studio (depth required) Dataverse – security model (security roles, business units, teams, column‑level security, row‑level security, hierarchical security), table and relationship design, plug‑ins, business rules, calculated and roll‑up columns, and auditing. Copilot Studio – agent topic design, knowledge sources, generative answers, plugins and connectors, authentication via Entra , content moderation, and audit. You have stood up at least one production‑grade agent end‑to‑end. Working knowledge of Microsoft Purview for Copilot so DSPM‑for‑AI controls compose with your agent design – you will partner with the Purview lane on this, but you must be able to reason about it end‑to‑end. Identity & observability (depth required) Microsoft Entra ID – app registrations, service principals, conditional access, and how all of the above bind to Power Platform DLP and Copilot Studio agent authentication. Azure Monitor and Log Analytics – workspace design, diagnostic settings on Power Platform and Dataverse, KQL fluency , workbook authoring, alert rules, and action groups. Application Insights for component‑level telemetry on custom connectors, plug‑ins, and Copilot Studio agents. Power BI dashboards that report a value metric a non‑technical executive can act on (maker activity, app health, flow run success, agent usage, governance posture). Consulting craft (depth required) Demonstrated ability to author and present architecture artifacts to a CTO‑level audience: C4 diagrams, SADs, SDDs, milestone roadmaps. A discovery toolkit you actually use – Lean UX, BPMN, Event Storming, or comparable methods for translating ambiguous client problems into a prioritized backlog with measurable outcomes. Strongly Preferred Microsoft certifications: PL‑600 (Power Platform Solution Architect), PL‑400 (Developer), PL‑500 (RPA Developer), PL‑200 (Functional Consultant), AZ‑104 (Azure Administrator) . Experience integrating Power Platform with Microsoft Fabric, Dataverse long‑term retention, or Azure SQL. Familiarity with Bicep + Azure Developer CLI (azd) for any Azure‑side resources adjacent to the Power Platform estate (custom connector backends, function apps, Container Apps). Power Automate Desktop and Document Intelligence experience for RPA and intelligent‑document scenarios. Prior delivery in regulated environments (medical device, life sciences, healthcare, or financial services) and comfort with the documentation discipline that comes with them. Experience as a subcontractor or partner‑of‑partner – you know how to represent PTM cleanly inside multi‑vendor delivery teams and inside the end‑client’s governance forums. How you work Search before assumptions. You verify against current docs, the client tenant, and runtime evidence before recommending. Confidence without evidence is not a substitute for either. Contracts before code. You define the interface – security roles, environment policies, ALM gates, agent authentication boundaries – before anyone builds against it. Validators before delivery. Every governance control ships with a test that proves it works and an alert that fires when it stops working. Maker‑Checker over solo heroics. You welcome a second pair of eyes on every material design decision, and you give the same in return. Plain language. A 12‑year‑old can follow your milestone narrative. A CTO trusts your architecture. A business owner sees the ROI line. Engagement details Engagement structure. Contract‑to‑hire. Initial term covers the full 90‑day engagement (30 days Discovery + 60 days Implementation). Conversion to PTM Fusion full‑time hire on successful delivery and mutual fit. Capacity. One full‑time‑equivalent role, paired with a Microsoft Purview / M365 compliance specialist on the same engagement. Location. Remote, US‑based. Possible occasional travel to client sites. Compensation. Competitive contract rate during the engagement; market‑aligned base, performance bonus, and benefits package on conversion. Final terms commensurate with experience and certifications. Start. Immediate. Discovery kicks off as soon as the right candidate is in seat. Possibility of contract‑to‑hire #J-18808-Ljbffr Proactivemgmt