… 23 unchanged lines …
  - What the default environment is *for*, and whether you rename it to something that says so.
  
  ## Gotchas
+ - **Deprecated 15 November 2026:** Dataverse for Teams environments are deprecated. New ones can't be created after 15 November 2026, and environments not upgraded to full Dataverse are decommissioned on 30 October 2027. Microsoft's page also lists a suspension date of 15 September 2026, which sits before the creation cut-off, so check it before you quote it to a client. See [deprecation page](https://learn.microsoft.com/en-us/power-platform/important-changes-coming#deprecation-of-microsoft-dataverse-for-teams-environments).
+ - **Deprecated 15 November 2026:** Unmanaged developer environments, including the ones the Developer Plan creates, can't be created after 15 November 2026, are suspended from 15 December 2026 and deleted from 15 January 2027. Developer environments that are managed aren't affected, but managed use needs premium licensing, and each user gets one. See [deprecation page](https://learn.microsoft.com/en-us/power-platform/important-changes-coming#deprecation-of-unmanaged-developer-environments-and-the-power-apps-developer-plan).
  - Converting production to sandbox can't be blocked, even when production creation is. Anyone with the right role can flip the type and then reset the environment.
  - Switching a production environment to sandbox to perform a restore limits you to backups from the last seven days. Switch it back immediately afterwards or you lose the older ones.
  - Environment history disappears when the environment is hard deleted, so "who deleted this?" often has no answer.