Last updated July 17, 2026 by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Every EPC Group stat has a counting rule behind it. This page documents those rules — what qualifies as an engagement, implementation, deployment, initiative, migration, migrated user, or client. Time windows, exclusions, and edge-case handling all specified so external reviewers can validate independently.
Key Facts
- Enterprise engagement = signed SOW + senior architect delivery + written deliverable (multi-year retainer counts once per year)
- SharePoint implementation = stood-up environment reaching production acceptance + content-load
- Power BI deployment = tenant/gateway/workspace/semantic-model reaching production (assessments alone excluded)
- Microsoft Fabric project = production Fabric workload (Lakehouse, Warehouse, Real-Time Intelligence, Data Factory, Data Science, Data Activator)
- Copilot initiative = production rollout OR completed readiness assessment (300+ = 60+ rollouts + 240+ assessments)
- Tenant migration = cross-tenant M365 cutover with content preservation; migrated user = per-seat cutover across mailbox/OneDrive/SharePoint/Teams/Copilot
Definitions
What counts as an "enterprise engagement"?
An enterprise engagement is a paid EPC Group consulting engagement with a written Statement of Work signed by both parties, delivered by at least one EPC Group senior architect, terminating in a written deliverable (assessment, design, migration, implementation, or managed-service acceptance). Multi-year retainers count as one engagement per year of contract term. Pro-bono, referral, and Microsoft-funded work is excluded from the 11,000+ count.
What counts as a "SharePoint implementation"?
A SharePoint implementation is a stood-up SharePoint environment (SharePoint Server 2007 through Subscription Edition, SharePoint Online, or hybrid) that reached production acceptance and content-load. New farms, tenant provisions, migrations from a non-SharePoint DMS to SharePoint, and major upgrades that touched site collection architecture all count. Ongoing managed support of an existing farm does NOT count as a new implementation.
What counts as a "Power BI deployment"?
A Power BI deployment is a delivered engagement that landed a Power BI tenant, gateway, workspace architecture, semantic model, or paginated-report footprint into production. Assessments alone do not count. Custom dashboard delivery counts when the semantic model was built or materially refactored by EPC Group. Row-level security and governance rollouts each count as one deployment.
What counts as a "Microsoft Fabric project"?
A Microsoft Fabric project is delivered work that involved Microsoft Fabric workloads (Lakehouse, Warehouse, Real-Time Intelligence, Data Factory, Data Engineering, Data Science, or Data Activator) in production. Includes Fabric-native builds and migrations from Synapse / Power BI Premium to Fabric SKUs. Preview-only pilots that never reached general availability are excluded.
What counts as a "Microsoft Copilot initiative"?
A Microsoft Copilot initiative is either (a) a Copilot rollout — a delivered Microsoft 365 Copilot, Copilot for Sales/Service/Finance, Copilot Studio agent, or Security Copilot deployment reaching production, OR (b) a Copilot readiness assessment — a scoped assessment producing a written report on Copilot fit, data-estate readiness, governance gap, and licensing recommendation. The 300+ number is the sum of both (60+ rollouts + 240+ readiness assessments).
What counts as a "Microsoft tenant migration"?
A Microsoft tenant migration is a completed cross-tenant M365 migration — mailboxes, OneDrive, SharePoint sites, Teams, Copilot licensing, security policies, and identity — from a source tenant to a target tenant. Typically part of an M&A carve-out or divestiture. The 216+ number reflects tenant migrations completed by EPC Group between January 2023 and December 2025 across the M&A program.
What counts as a "user migrated"?
A migrated user is an M365 licensed user seat whose mailbox, OneDrive, SharePoint access, Teams identity, and Copilot licensing was cutover from a source tenant to a target tenant with content preservation. The 1.83 million figure is the total across all 216+ tenant migrations. Includes both interactive and shared / resource mailboxes but not guest/B2B accounts.
What counts as a "client"?
EPC Group does NOT publish a unique-clients count because the same customer often runs multiple concurrent engagements across different divisions or business units. Publishing a client count without deduplication rules would be misleading. Where "clients served" is referenced, it means distinct legal entities where at least one signed Statement of Work has closed. Rules: legal entity = ultimate parent + wholly-owned subsidiaries counted as one; federal agencies counted as one per agency; state/local by discrete government body.
Why is the founding year 1997?
EPC Group (O'Connor Enterprise Group Inc.) was incorporated March 30, 1997 in Texas. This is the canonical founding date used in all schema.org Organization nodes, PR boilerplate, and partner directory listings. Wikidata: Q140423071. The "29 years" statement is derived from BRAND.legalFounded and updates annually at year-end.
What trust signal does EPC Group publish?
G2 verified reviews are our canonical trust signal — currently 4.4/5 across 15 verified engagements plus six consecutive quarters as a G2 Leader in Microsoft consulting. G2 is used because reviews are third-party verified, comparable across the Microsoft consulting category, and independent of the reviewed vendor. Adjacent trust signals include Clutch (3.8/5 across 4 verified reviews) and the Microsoft Solutions Partner designation attainment tracked by Microsoft. Aggregate cross-platform ratings are intentionally not published because each platform's methodology and reviewer base differs — a single blended number would mislead.
Change log
When a definition changes (e.g., a category is renamed, a counting window is adjusted), the change is announced here with the effective date. As of 2026-07-17, this page is at version 1.0.
Adjacent references
- /proof — current stats
- /about/facts — canonical fact page with source links
- /about — narrative about EPC Group
Questions about a definition? Contact contact@epcgroup.net.