
Key Takeaways
- Intune + Power Platform in M&A: The Two Workloads That Kill Timelines.
- Frequently Asked Questions.
- Next Steps.
On this page3 sections
Intune + Power Platform in M&A: The Two Workloads That Kill Timelines
In a Microsoft 365 M&A tenant consolidation, Exchange + SharePoint + OneDrive get the spotlight. But the two workloads that consistently kill migration timelines are Microsoft Intune (endpoint management) and Power Platform (Power Apps + Power Automate + Power Pages + Power BI). This is the field guide.
Why These Two Workloads Are Different
Intune = device-bound state. Every endpoint must be re-enrolled or re-targeted. User-visible friction. Conditional Access dependencies. Compliance policy implications.
Power Platform = data-bound + connection-bound state. Custom apps + flows + connectors don't migrate cleanly. Premium licensing applies. Environment variables + connection references need re-validation.
Combined: 30-50% of M&A migration effort despite being 10-15% of stakeholder mindshare during planning.
Microsoft Intune Migration Patterns
Pattern 1: Greenfield re-enrollment (recommended for most)
Acquired subsidiary endpoints re-enroll to parent tenant Intune. New device compliance policies + Conditional Access from parent baseline. User experience: refresh + re-sign-in.
- Timeline: 4-8 weeks for 1,000-5,000 endpoints
- Risk: user friction during re-enrollment window
- Mitigation: phased rollout by business unit + clear comms
Pattern 2: Identity first, devices in later waves
Users are provisioned into the parent tenant first (for example with Microsoft Entra cross-tenant synchronization), and devices stay managed by the source tenant until their wave. Enrollment does not carry over: each Windows device is deleted from the source Intune, deregistered from Windows Autopilot, and then registered and enrolled in the parent tenant.
- Timeline: 6-12 weeks
- Risk: two tenants manage devices at the same time
- Mitigation: pilot wave of 50-100 endpoints
Pattern 3: Hybrid (split workforce)
Some endpoints re-enroll, others stay on source tenant via cross-tenant access. Used when M&A integration is partial or paused.
- Timeline: 8-16 weeks
- Risk: operational complexity of dual tenants long-term
- Mitigation: define decision criteria (which devices migrate vs stay)
Intune-Specific Pitfalls in M&A
Compliance policy baselines differ. Sub-A had relaxed PIN length, Sub-B had biometric required. Unify before re-enrollment.
Conditional Access policies conflict. Each source tenant had bespoke Conditional Access. Merging creates 50+ policies + drift. Rebuild from baseline.
App protection policies vary. Mobile app protection (MAM) for personal devices. Different settings per source tenant. Unify.
Autopilot profile mismatch. New device enrollment depends on Autopilot profile. Source tenant profiles must decommission or update to parent tenant.
Endpoint analytics baselines. Performance + reliability scoring from each source tenant. Consolidate or restart.
Microsoft Tunnel + VPN replacement. If source tenant used Tunnel, evaluate parent tenant pattern.
What Microsoft Supports for Each Workload (Checked 2026-11-02)
Intune and Windows Autopilot. The documented path for a Windows device that leaves an organization is to delete it from Intune first and then deregister it from Windows Autopilot; for Microsoft Entra hybrid joined devices, also delete the computer object from on-premises AD DS so it is not resynced, and do not delete the Entra device object by hand. A partner deregistering a device in Partner Center removes only the Autopilot registration, not the Intune enrollment or the Entra join. Source: Microsoft Learn, Windows Autopilot registration overview.
Power Platform. Microsoft supports tenant-to-tenant migration of production and sandbox environments, started in the Power Platform admin center or with PowerShell and approved by the destination tenant (a request expires after seven days). Default, developer, trial and Teams environments are not supported, and neither are moves between GCC and commercial clouds. Custom connectors, connections and gateways are not migrated; imported flows arrive turned off and HTTP-triggered flows get new URLs; security groups are not migrated; users missing from the user-mapping file are not migrated; managed environments must be re-enabled. Microsoft says to migrate and test a sandbox copy before production, and to allow up to 24 hours. Source: Microsoft Learn, Tenant-to-tenant migrations - Power Platform (ms.date 2026-10-30).
The migration exception log (CSV) lists these exceptions with how each shows up, the test to run before cutover, the fix and the owner. Its rows are examples, not a client record.
Power Platform Migration Patterns
Pattern 1: Replatform to parent tenant (recommended)
Acquired Power Apps + Power Automate flows replatformed in parent tenant. Connectors re-authenticated. Environment variables + connection references re-validated.
- Timeline: 2-6 weeks per app/flow depending on complexity
- Risk: connector behavior differences (custom vs premium licensing)
- Mitigation: connector inventory + replatform plan per app
Pattern 2: Power Platform Center of Excellence (CoE) standardization
Used when acquirer has mature Power Platform CoE. Acquired apps + flows must conform to CoE templates + governance.
- Timeline: 4-12 weeks (longer because rebuild not lift-shift)
- Risk: business process disruption
- Mitigation: phased per-app rollout with business owner sign-off
Pattern 3: Retire + replace
Some acquired apps are obsolete or have parent-tenant equivalents. Retire instead of migrate.
- Timeline: Immediate decommission post-cutover
- Risk: lost business logic if poorly documented
- Mitigation: business process audit before retirement
Power Platform Pitfalls in M&A
Custom connectors don't migrate. Custom connectors built in source tenant must be rebuilt in parent. 40-80 hours per custom connector.
Environment variables + connection references. Hard-coded values in flows. Re-validate every variable + reference after migration.
Premium connector licensing. Some flows used premium connectors (Salesforce, SAP, ServiceNow). Verify parent tenant licensing covers.
Service principal + service account dependencies. Flows using service accounts/SPs need credential rotation post-migration.
Power Apps embedded in Teams. Apps surfaced via Teams require re-deployment after migration.
Power Automate desktop flows. RPA bots have additional licensing + execution endpoint considerations.
Dataverse environment migration. Microsoft's tenant-to-tenant migration moves the Dataverse organization of a production or sandbox environment to the destination tenant; plan it as its own workstream, with a sandbox test first.
Realistic Timeline + Cost
Intune for 1,000-5,000 endpoints across M&A:
- Discovery + planning: 2-3 weeks
- Pilot wave: 2-3 weeks
- Production waves: 4-12 weeks
- Hypercare: 2-3 weeks
- Total: 10-21 weeks, fixed-fee consulting quoted after discovery + internal IT bandwidth
Power Platform for 10-30 acquired apps/flows:
- Inventory + complexity scoring: 2-3 weeks
- Per-app/flow replatform: 1-4 weeks each
- CoE standardization: 4-8 weeks
- Hypercare: 2 weeks
- Total: 12-26 weeks, fixed-fee consulting scoped by app complexity
Combined Intune + Power Platform:
Often 40-60% of total M&A migration consulting budget + 50-70% of internal IT bandwidth.
Why EPC Group Specifically
EPC Group has shipped Power Platform + Intune migrations in dozens of M&A engagements. Specific expertise:
- Power Platform CoE templates from Microsoft Customer Engineering
- Intune compliance policy unification patterns by industry (healthcare, financial services, manufacturing)
- Custom connector + Dataverse environment migration
- Microsoft consulting since 1997 + AI Cloud Partner all six designations
Frequently Asked Questions
Q: Can Intune migration happen in parallel with Exchange + SharePoint migration?
A: Yes but adds risk. We recommend Intune wave AFTER identity unification is complete. Conditional Access depends on identity.
Q: What about endpoints that source tenant manages via Jamf or other MDM?
A: Cross-MDM migration adds 2-4 weeks. Test pilot wave before full rollout.
Q: Should Power Platform apps be modernized during migration?
A: Yes if business priorities align. Migration is a natural inflection point for Power Platform CoE standardization. EPC Group typically recommends.
Q: What if the acquired company has minimal Power Platform usage?
A: Easier scope. Inventory + replatform 0-10 apps takes 4-8 weeks. Often cheaper than maintaining 2 tenants.
Q: Why EPC Group?
A: Microsoft consulting since 1997 + deep M&A practice across Power Platform + Intune. Microsoft Solutions Partner with all six designations under the Microsoft AI Cloud Partner Program. Microsoft Press author. See /reviews.
Next Steps
- Schedule discovery: /contact
- Productized assessment: /services/m-and-a-tenant-migration-assessment
- Full M&A service: /services/m-and-a-microsoft-365-tenant-migration
- Power Platform CoE: /services/power-platform
- Call (888) 381-9725
Errin O'Connor
Founder & Chief AI Architect
Microsoft Press bestselling author with enterprise consulting experience since 1997.
View Full ProfileRelated Articles
Power Automate Approval Workflows: Enterprise Governance in 2026
Approval workflows in Power Automate in 2026: approval types, the 28-day wait limit, Try/Catch error handling, data policies and service-principal ownership.
Microsoft 365The Mid-Market Microsoft Fixed-Fee Catalog: 15 Senior-Led Packages (2026)
Mid-market enterprises are forced to choose between premium-priced senior consulting and offshored junior delivery. EPC Group's Mid-Market Microsoft Fixed-Fee Catalog ends that false choice — 15 fixed-scope, fixed-fee packages across 5 service families. Senior architects only.
Microsoft 365Microsoft 365 Backup GA: Enterprise Operationalization Guide (2026)
Microsoft 365 Backup is now generally available. EPC Group enterprise operationalization guide: scope (Exchange / SharePoint / OneDrive / Teams), recovery patterns, HIPAA + FINRA + FedRAMP overlays, comparison vs Veeam + AvePoint + Druva.
