Power Platform Deprecations: Key Dates and Required Actions
Microsoft is retiring or changing several Power Platform features and environment types. The following table highlights the important deadlines and actions that administrators, developers and makers should plan for.
| Feature / Service | Deprecation Date | What You Need to Do |
|---|---|---|
| AI-Generated App Descriptions Model-driven Apps |
November 30, 2026 | Prepare to write and maintain app descriptions manually. Existing descriptions remain unchanged. |
| Copresence in Power Apps Plans | November 30, 2026 | Coordinate plan editing outside the platform and allow only one author to edit a plan at a time. |
| Record-Level Copresence Model-driven Apps |
November 30, 2026 | Continue using record sharing and other available collaboration features. |
| Power Apps Ideas & Formula Generation | December 11, 2026 | Use Power Fx directly in the formula bar. Existing formulas are not affected. |
| Rename Controls with Copilot Canvas Apps |
December 11, 2026 | Rename controls manually using Tree view. |
| Unmanaged Developer Environments | December 15, 2026 | Convert environments to Managed Environments or export solutions and move them to supported environments before suspension. |
| Cross-Environment Comment Import/Export | December 31, 2026 | Use source control, DevOps pipelines, documentation or release notes to preserve collaboration context. |
| Unmanaged Developer Environments Deletion | January 15, 2027 | Export and preserve important solutions before deletion. Suspended environments will begin deletion. |
| Dataverse for Teams | September 15, 2027 | Upgrade environments that need to be retained to full Dataverse before suspension. |
| Dataverse for Teams Decommissioning | October 30, 2027 | Complete migration to full Dataverse. Unupgraded environments and their apps, flows, agents and data will be decommissioned. |
Important: Existing Managed Developer Environments are not affected by the unmanaged developer environment retirement. Similarly, the Dataverse for Teams retirement does not remove regular Microsoft Teams, channels, chats or SharePoint files.
Note: Deprecation does not always mean immediate removal. Check Microsoft's official documentation for the exact impact and migration requirements for each feature.
Introduction
Microsoft Power Platform changes continues to evolve, bringing new capabilities while gradually retiring older features and experiences. These updates can affect how organizations build applications, manage workflows, maintain environments and support business users.
For IT administrators, developers and Power Platform makers, understanding these changes early is essential. Some updates require only minor adjustments, while others involve environment migration, licensing reviews or changes to existing development practices.
Here are the important Power Platform changes to prepare for in 2026 and 2027.
Major Power Platform Changes
1. Copilot in the Power Automate Designer
Microsoft plans to retire the Copilot pane in the cloud flow and agent flow designer on November 30, 2026. Makers will no longer be able to use this built-in experience to create or edit flows through conversational instructions or troubleshoot using the designer Copilot pane.
Existing flows will remain unaffected and can still be created, edited, tested and executed using the standard designer.
Recommended action: Update internal training materials and help makers become familiar with the visual designer, expression editor, flow checker and templates.
2. Describe It to Design It in Power Automate
The Describe It to Design It capability will also retire on November 30, 2026. This feature previously allowed makers to describe an automation requirement in natural language and generate a cloud flow.
Organizations should prepare makers to create flows manually or use available templates and approved AI-assisted alternatives.
3. Power Apps Formula Generation Features
After December 11, 2026, Power Apps Ideas, Create a Formula and formula generation through code comments will no longer be available.
Existing Power Fx formulas will continue to work. Developers can still write formulas directly and use the Explain this Formula and Explain this Selection experiences.
Recommended action: Encourage developers to strengthen their Power Fx knowledge and review existing formula-building workflows.
4. Dataverse for Teams Retirement
Microsoft is transitioning organizations from Dataverse for Teams environments to full Microsoft Dataverse environments. Creating new Dataverse for Teams environments is no longer available from November 15, 2026.
Existing environments have additional retirement milestones:
| Milestone | Date | Impact |
|---|---|---|
| New environment creation ends | November 15, 2026 | New environments cannot be created. |
| Environment suspension | September 15, 2027 | Unupgraded environments become unavailable. |
| Decommissioning | October 30, 2027 | Remaining unupgraded environments are decommissioned. |
Recommended action: Identify active environments, review capacity and licensing requirements, and plan an upgrade to full Dataverse before the deadlines.
5. Unmanaged Developer Environment Changes
Microsoft is also changing how unmanaged developer environments are provisioned and maintained. From November 15, 2026, users can no longer create new unmanaged developer environments.
Existing unmanaged developer environments will be affected by the following milestones:
- December 15, 2026: Suspension of existing unmanaged developer environments begins.
- January 15, 2027: Deletion of suspended unmanaged developer environments begins.
Managed developer environments are not affected by this retirement. Organizations should review their environment strategy and preserve important solutions before suspension.
What Should Power Platform Administrators Do?
Rather than waiting for features to disappear, administrators should establish a simple review and migration plan.
- Audit environments: Identify active Dataverse for Teams and unmanaged developer environments.
- Review dependencies: Check applications, cloud flows, agents and Power Pages sites that rely on affected capabilities.
- Prepare migrations: Evaluate Managed Environments, full Dataverse and the required licensing.
- Update development practices: Prepare makers for changes to Copilot and Power Fx formula-generation features.
- Communicate deadlines: Inform developers, environment owners and business stakeholders about upcoming changes.
- Validate solutions: Test migrated applications and workflows before moving them into production.
Conclusion
The upcoming Microsoft Power Platform changes are an important reminder that application development and automation strategies need regular maintenance. While existing solutions may continue to work during certain retirement periods, delaying preparation can create avoidable operational and development challenges.
Organizations should review their environments, understand the impact of each announcement and prioritize migrations based on the published deadlines. A proactive approach will help maintain business continuity while taking advantage of the latest Power Platform capabilities.
Need help reviewing your Power Platform environment? Consider conducting an environment audit to identify affected applications, dependencies and migration requirements before the relevant deadlines.



