EPC Group has shipped Power Apps across every industry vertical. Six enterprise patterns dominate. Each has a distinct audience, surface choice, integration footprint, and security profile. The right pattern matches the audience, the data, and the team’s skills.
Regulated-industry forms replacing InfoPath
Audience
Internal employees in HIPAA, FINRA, CMMC, and GxP-relevant flows
Twenty years of InfoPath-on-SharePoint investment is end-of-life. The right successor is a model-driven Power App on Dataverse for the structured intake (RBAC, column-level security, audit logging, Microsoft Purview sensitivity labels) paired with a canvas app for any mobile-first capture and a Power Automate flow for downstream orchestration. This is the largest InfoPath-modernization workload EPC Group sees in 2026.
Real-world examples
A specialty hospital migrating 180 InfoPath forms covering quality, incident, patient-rights, and IRB submissions. A broker-dealer modernizing 60 continuing-education and recordkeeping forms. A defense supplier replacing self-attestation forms with a Dataverse-backed CMMC evidence-capture app.
Design note
Most InfoPath modernizations start as a 1:1 port and end as a re-platform. Model-driven lets the team consolidate seven near-identical forms into one table with three views. Compliance frameworks in scope: HIPAA, SOC 2, FedRAMP, FINRA, CMMC, GxP.
Field service mobile apps
Audience
Field technicians, inspectors, drivers, route reps on phones and tablets
A canvas app on the Power Apps mobile player gives field workers an offline-tolerant, task-focused screen they complete one-handed at the job site. Inspections, work-order completions, signature capture, photo capture, route updates, and parts-consumption logging sit inside a single canvas app bound to Dataverse or the system of record. Cards extend the same workflow into Teams chat for exception acknowledgement.
Real-world examples
A national HVAC contractor running 1,200 technicians on a canvas inspection app with offline sync. A utility running 600 line workers on a Dataverse-backed asset-inspection app with GIS integration. A food-service company running daily safety walkthroughs across 4,800 store locations.
Design note
Offline-and-sync drives everything. Dataverse offline sync, SharePoint offline lists, and SQL local cache each have a place. EPC Group selects the right approach during Assess and models the conflict-resolution policy before any code ships.
M&A onboarding and integration runbook apps
Audience
M&A program managers, IT integration leads, HR onboarders, deal-team operators
Every M&A integration is a 90-to-365-day project with hundreds of tasks across IT, HR, finance, legal, and operations. A model-driven Power App on Dataverse is the right surface for the runbook — tasks, owners, dependencies, milestones, status, risk — with a canvas companion for cutover capture and Cards in Teams for daily check-ins. EPC Group has used this pattern across 216+ M&A tenant consolidations spanning 1.83 million users.
Real-world examples
A healthcare system absorbing a 7,200-employee hospital with full M365 cutover, AD consolidation, and 19 line-of-business app migrations. A PE portfolio operator running 180-day integration runbooks across 14 add-on acquisitions per year. A bank integrating a 240-advisor wealth arm.
Design note
The runbook is the asset. EPC Group ships a packaged Dataverse solution with the model-driven runbook, a Power BI dashboard, and a Cards distribution policy as a managed-solution accelerator. Subsequent M&A events deploy the solution and configure the tenant — not rebuild from scratch.
Vendor and supplier portals (internal companion)
Audience
Internal procurement, AP, supplier-management, and vendor-onboarding teams
The external-facing vendor portal is built on Microsoft Power Pages. The internal counterpart — the model-driven app procurement, AP, and supplier-management teams use to review qualifications, approve onboarding, manage contracts, and resolve disputes — is built on the same Dataverse schema. Together they form a single procurement experience without an integration layer.
Real-world examples
A manufacturer running supplier qualification across 14 buyers and 2,400 vendors. A healthcare system running credentialing, W-9, and COI tracking with model-driven internal and Power Pages external. A federal prime contractor running subcontractor CMMC self-attestation capture for compliance review.
Design note
The Dataverse schema is the contract between internal and external surfaces. EPC Group designs the schema once and binds both to it — procurement gets advanced views and bulk operations; vendors get a clean portal experience; both work from the same row.
Employee self-service and HR companion apps
Audience
Employees on desktop and mobile, HR business partners, internal-comms teams
A canvas app on mobile for time-off, expense capture, desk booking, and equipment-loan requests. A model-driven app for HR business partners to triage employee-relations cases, track personnel actions, and manage onboarding cohorts. Cards inside Outlook and Teams for one-tap approvals. One of the highest-frequency Power Apps deployments in modern Microsoft 365 environments.
Real-world examples
An 18,000-employee health system running mobile time-off, expense, and shift-swap on canvas with HR triage on model-driven. A multi-state retailer running canvas onboarding for high-turnover frontline roles. A professional-services firm running desk-booking with manager-approval Cards in Outlook.
Design note
Entra SSO is mandatory — employees should never need a separate password. Canvas must respect conditional access, device-compliance, and Microsoft Intune mobile-application-management policies. Cards inherit the host trust boundary, which simplifies governance materially.
ISV and multi-tenant Power Apps
Audience
ISVs and multi-business-unit enterprises distributing apps across tenants
Power Apps is increasingly the build surface for ISVs publishing line-of-business apps through Microsoft AppSource. Multi-tenant architecture, AppSource certification, managed-solution packaging, and ISV licensing models are supported. Multi-business-unit enterprises use the same pattern to distribute a corporate app across subsidiary tenants while preserving subsidiary autonomy.
Real-world examples
A vertical ISV publishing a healthcare-quality-reporting app on AppSource with 40+ customer tenants. A holding company distributing a capital-projects model-driven app across 12 subsidiary tenants. A consulting firm publishing an engagement-management solution for alliance-ecosystem resale.
Design note
ISV economics depend on the embed license model and the AppSource certification path. EPC Group has shipped both AppSource-listed ISV apps and large-enterprise multi-tenant distributions. AppSource vs managed-solution distribution is a business-model decision, not a technical one.