Power Connector 2.0 integration, migration, and Entra ID requirements
This article provides a complete overview of what changes with the release of Power Connector 2.0. It explains how Power Connector 1.0 continues to operate, how to plan a safe migration, how to prevent disruptions, and which new Entra ID app registrations are required.
This article covers the following topics:
- How Power Connector 1.0 and Power Connector 2.0 can run side by side.
- How to plan the migration from Power Connector 1.0 to 2.0.
- How organizations can prevent service disruption.
- Which app registrations are required for Power Connector 2.0.
1. Understanding coexistence between Power Connector 1.0 and Power Connector 2.0
Power Connector 2.0 is added to the Power Platform but does not replace Power Connector 1.0. Both connectors can run in the same environment.
What continues to work
- Power Connector 1.0 remains fully functional.
- No features are removed when Power Connector 2.0 is released.
- Microsoft only retires a connector version when customers no longer use it.
Key points
- Running both connectors at the same time is technically possible but not ideal due to administrative and user complexity.
- Mavim communicates well in advance when Power Connector 1.0 approaches end of life.
- Customers choose their own timeline for moving to 2.0.
Why this matters
Organizations retain full control over timing, governance, and internal dependencies. You can prepare and deploy Power Connector 2.0 without affecting existing production systems.
2. Migrating from Power Connector 1.0 to Power Connector 2.0
There is no automatic migration. Everything running on Power Connector 1.0 continues to operate as before.
Recommended approach
- Keep using Power Connector 1.0 for existing flows and apps.
- Build new solutions directly with Power Connector 2.0.
- Migrate existing workloads in phases that match your release and governance cycles.
- Track lifecycle announcements for Connector 1.0.
What you migrate
- Connections.
- Power Automate flows.
- Power Apps data connections.
Important notes
- Migration is optional.
- You do not need to rebuild existing solutions.
- Mavim provides documentation and support throughout the migration period.
3. Preventing disruption for organizations using Power Connector 1.0
Large organizations with significant automation workloads do not need to take risks during the introduction of Power Connector 2.0.
Best practices
- Keep using Power Connector 1.0 for existing, business‑critical workloads.
- Use Power Connector 2.0 for all new development.
- Spread migrations over future release cycles.
- Align changes with existing change management processes.
Why this prevents disruption
- No forced rewrites.
- No downtime.
- Organizations decide when components are updated.
- Power Connector 1.0 only reaches end of life after early communication and a generous transition period.
4. App registration requirements for Power Connector 2.0
Power Connector 2.0 uses an updated app registration model within Microsoft Entra ID. This improves security, identity separation, and performance.
What is new
- Power Connector 2.0 requires new enterprise applications in Entra ID.
- These app registrations are mandatory for Power Connector 2.0 to function.
- They are not compatible with Power Connector 1.0.
- The updated model provides clearer identity boundaries and improved performance.
What Mavim provides
- Step‑by‑step installation instructions.
- A list of required permissions.
- Documentation and frequently asked questions.
What administrators need to do
- Review and approve the new app registrations.
- Grant permissions according to internal security policies.
- Plan implementation within standard governance processes.
Important notes
- Mavim does not introduce unexpected changes.
- You decide when to implement Power Connector 2.0.
5. Important warnings and prerequisites
- Power Connector 1.0 is not retired immediately.
- App registrations for Power Connector 2.0 do not work with Power Connector 1.0.
- Change management is needed for structured migration.
- Administrator permissions in Entra ID are required for installation.
