Dataverse retirements set 2026 and 2027 deadlines

Key insights

• New Dataverse for Teams environments and unmanaged developer environments stop being created on November 15, 2026.
• Unupgraded Dataverse for Teams environments are scheduled for suspension on September 15, 2027, and decommissioning on October 30, 2027.
• Existing unmanaged developer environments are scheduled for suspension on December 15, 2026, and deletion on January 15, 2027.
• The video identifies a full Dataverse environment, such as sandbox or production, as the alternative for Dataverse for Teams.
• Admins are advised to filter for Type = Developer and Managed = No, then enable Managed Environments or move solutions.

Dhruvin Shah [MVP] recently published a video about the retirement of Dataverse for Teams environments and unmanaged developer environments. The key takeaway is that makers and administrators should identify which environments they use and plan for the dates the video lists, rather than assume these development and Teams-based environments will remain available. The video also points to different next steps for the two changes.

What's new

The video describes two separate retirements. First, new Dataverse for Teams environments will no longer be created beginning November 15, 2026. Existing environments have a later timeline: suspension is scheduled for September 15, 2027, followed by decommissioning on October 30, 2027.

Second, creation of new unmanaged developer environments ends on November 15, 2026. The video says existing unmanaged developer environments are scheduled for suspension on December 15, 2026, and deletion on January 15, 2027. These dates are distinct from the Dataverse for Teams milestones, so organizations should inventory the two environment types separately.

For Dataverse for Teams, the video identifies an upgrade to a full Dataverse environment as the alternative, naming sandbox and production as environment types. For developer environments, it discusses enabling Managed Environments or moving solutions. It also says managed developer environments are not affected by this retirement, while noting a new limit of one managed developer environment per user.

Why it matters

These changes concern makers who use Dataverse for Teams or an unmanaged developer environment to learn, build, or test. The video specifically calls out apps, flows, agents, and data as items associated with the environments. That makes an environment inventory a practical first step: identify where those assets sit and whether they depend on an environment with a retirement date.

Admins have a direct task in the video: filter environments by Type = Developer and Managed = No. They can then consider enabling Managed Environments or moving solutions. The description does not explain the detailed steps for either action, but it makes clear that unmanaged developer environments should be found before the stated suspension date.

Learners and individual makers should also note the licensing distinction described. The video says a managed developer environment needs a Power Apps Premium or Power Automate Premium license, and presents the Power Platform trial as a free option for learners. It does not specify further terms or eligibility details, so readers should not treat the description as a complete licensing guide.

For teams that use Dataverse for Teams, the relevant decision is whether to upgrade to full Dataverse ahead of the later suspension and decommissioning milestones. The video says the upgrade is the alternative, but does not provide detailed migration steps or establish which environment type is right for a particular workload. Organizations will need to assess their own apps, flows, agents, data, and operational needs.

How it works

Shah’s video combines a review of the retirement announcements with a demonstration in the Power Platform admin center. Its practical guidance for admins can be summarized as an inventory and decision process:

1. In the admin center, filter for environments where the type is Developer and Managed is No.
2. Review which unmanaged developer environments are in use and what solutions they contain.
3. Decide whether to enable Managed Environments or move the solutions, taking account of the licensing point described in the video.
4. Separately identify Dataverse for Teams environments and plan whether to upgrade them to a full Dataverse environment.

The dates matter to this process. November 15, 2026 is the creation cutoff for both categories. The subsequent dates differ: unmanaged developer environments are scheduled for suspension on December 15, 2026 and deletion on January 15, 2027; Dataverse for Teams environments are scheduled for suspension on September 15, 2027 and decommissioning on October 30, 2027.

Limitations and open questions

The available video description gives key dates, an admin filter, and broad alternatives, but it is not a full migration procedure. It does not describe the detailed upgrade process, how to assess individual workloads, or the consequences of suspension beyond listing the milestone. It also does not provide a detailed licensing explanation for managed developer environments or trials.

The description says managed developer environments, production, sandbox, trial, and default environments are not affected by the developer-environment retirement, and that exported solutions are not affected. Those statements concern the retirement described in the video; they should not be read as a guarantee about every service, tenant, or future policy. The video description does not establish that the timelines or options apply uniformly to every organization.

Shah notes that licensing announcements can be complex. Readers should check the underlying Microsoft announcements and current licensing guidance before making a migration or purchasing decision; those underlying announcement URLs are not included in the material provided here. The video is useful as a checklist of dates and areas to investigate, not as confirmation of a specific organization’s environment status.

Sources

• Dhruvin Shah’s video on Dataverse and developer environment retirements
• Dhruvin Shah’s website

Frequently asked questions

When do unmanaged developer environments stop being created?

The video lists November 15, 2026 as the cutoff for creating new unmanaged developer environments.

What should admins check first?

The video recommends filtering in the Power Platform admin center for Type = Developer and Managed = No, then considering Managed Environments or moving solutions.

What alternative does the video give for Dataverse for Teams?

It identifies upgrading to a full Dataverse environment, such as sandbox or production. The video description does not provide the detailed upgrade steps.

Are managed developer environments included in this retirement?

The description says managed developer environments are not affected by this retirement. It also says one managed developer environment per user is the new limit and that a Power Apps Premium or Power Automate Premium license is needed.