> Markdown version of [/jobs/ext/4780086-solution-architect-power-platform-946](https://www.wearedevelopers.com/jobs/ext/4780086-solution-architect-power-platform-946). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Solution Architect - Power Platform (946) - **Company:** ABC Supply Co. Inc. - **Location:** Beloit, WI, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Microsoft Azure, Github, Systems Integration, Model-Driven Development, Enterprise Software Applications, Microsoft Power Automate, Power Platform Integration, Technical Debt, Microsoft Copilot Studio, Powerapps - **Published:** November 19, 2026 - **Apply:** https://abcsupply.wd1.myworkdayjobs.com/ABCSupplyCareers/job/Beloit-WI/Solution-Architect---Power-Platform--946-_68711 ## About the Role * Experience - 8+ years delivering enterprise applications, including 4+ years architecting Dataverse-backed Microsoft Power Platform solutions at scale. * Advisory track record - Has reviewed an existing Power Platform estate, established scalable best practices, and helped delivery teams adopt standards through practical guidance and implementation support. * Technical depth - Dataverse architecture and security, DLP and connector governance, Managed Environments, integrations, and solution ALM with Azure DevOps or GitHub. ## Description Review, build, and expand. The Microsoft Power Platform Solution Architect evaluates the current Power Platform estate, strengthens the standards and patterns already in place, and builds the best practices needed for secure, scalable delivery. The role partners with platform owners, architects, developers, and makers to turn practical findings into reusable guidance, reference architectures, solution patterns, and implementation roadmaps. Success is measured by stronger delivery practices, reduced platform risk, and broader adoption of consistent standards across teams., * Review the current estate - Assess Power Platform applications, Dataverse models, environments, security roles, DLP policies, integrations, solutions, and ownership. Identify risk, inconsistency, technical debt, and opportunities to strengthen delivery. * Build practical Dataverse standards - Establish reusable guidance for canonical tables, publisher and prefix conventions, relationship design, alternate keys, choice vs. lookup, calculated and formula columns, cascade behavior, auditing, and the plug-in vs. Power Fx logic boundary. * Set environment & ALM strategy - Establish personal * dev * test * prod tiering, provisioning and decommissioning, Managed Environments and sharing limits, capacity and storage, managed-solution layering, environment variables, connection references, and Pipelines / Azure DevOps promotion. * Codify the security model - Define business-unit hierarchy, custom roles and privilege depth, owner vs. access teams, row sharing, column-security profiles, Entra ID group teams, and service-principal/connector identity as a maintainable model. * Expand platform best practices - Strengthen DLP and connector policy, Green / Yellow / Red tiering, telemetry, golden-path templates, shared components, reference architectures, and proportionate architecture reviews before production. * Train the trainers - Upskill the Citizen Development team and champions to teach the "license to build" curriculum and run reviews themselves; exit when they own the standards, tooling, and classroom. Core Competencies: * Dataverse data modeling - Normalization and relationship design, alternate keys, rollup/calculated and formula columns, cascade and delete behavior, auditing, and elastic vs. standard tables. * Environments, ALM & solutions - Environment tiering and Managed Environments, capacity and storage planning, managed-solution layering, environment variables, connection references, and source-controlled pipelines. * Dataverse security modeling - Business units, custom roles and privilege depth, owner/access teams, Entra group teams, row sharing, column-security profiles, and least-privilege design for self-service makers. * Integration & performance - Custom connectors, virtual tables, dataflows and Fabric/Synapse Link, delegation limits and API throttling, and when to graduate a build to pro-code. * Platform fluency - Hands-on across model-driven and canvas Power Apps, Power Automate, Copilot Studio, Power Pages, and Power Fx, with the depth to set standards and unblock makers. * Tenant governance - DLP and connector policy, CoE Starter Kit telemetry, licensing and capacity models, Managed Environments, and Power Platform admin-center operations. * Practice enablement - Turns architecture standards into usable playbooks, reference implementations, review checklists, reusable components, and targeted technical coaching. * Assessment & advisory - Estate reviews, gap analysis, reference architecture, best-practice development, and pragmatic roadmaps; credible with business and IT and focused on sustainable adoption., * A current-state Power Platform review with a prioritized roadmap for reducing risk, resolving technical debt, and improving delivery consistency. * Documented and reusable Dataverse, environment/ALM, integration, security, and governance best practices that teams can apply consistently. * Reference architectures, templates, review checklists, and implementation patterns are embedded into delivery, enabling the organization to continue expanding the practice sustainably.