Guidance changes
Observed changes to selected Microsoft guidance. Review in My radar · Timelines and exceptions
469 of 469 selected pages have a baseline. 401 pages have an observed change; the newest was seen today.
Coverage and checks
469 of 469 selected pages have a baseline · 401 with observed changes · 469 current checks
Observed changes
RSSOctober 2026 in brief
5 changes to 2 pages
4 may need admin action1 read to decide
Power Platform 5
Pick a day to list only its changes.
Week of 2 Nov 2026
- Power Platform Power Platform deprecations
May need admin actionCheck the dates against your plans.
Changed article references · 1 added · 0 removed
- Added link: start from a template
https://make.powerautomate.com/templates
6 new passages (about 140 words).
New section: Retirement of Describe it to design it in Power Automate
Also changed: Impact · Action required
NewRetirement of Describe it to design it in Power Automate [added: On November 30, 2026, Describe it to design it in Power Automate retires for all customers. This option lets makers create a cloud flow by] …
Before: No saved wording on this side.
After: On November 30, 2026, Describe it to design it in Power Automate retires for all customers. This option lets makers create a cloud flow by …
NewImpact [added: Beginning November 30, 2026, makers can no longer create new cloud flows with Describe it to design it. This retirement doesn't delete or move existing] …
Before: No saved wording on this side.
After: Beginning November 30, 2026, makers can no longer create new cloud flows with Describe it to design it. This retirement doesn't delete or move existing …
3 more changed passages · see them all
Observed 3 Nov 00:26 UTC · current page
- Added link: start from a template
Week of 26 Oct 2026
- Power Platform Power Platform deprecations
May need admin actionCheck whether new requirements apply to your setup; check the dates against your plans.
Changed article references · 0 added · 1 removed
- Removed link: start from a template
https://make.powerautomate.com/templates
33 new passages (about 520 words), 6 removed passages (about 140 words).
New sections: Deprecation of cross-environment comment import and export · Deprecation of AI-generated descriptions for model-driven apps · Deprecation of formula generation and Power Apps Ideas in canvas apps · Deprecation of proactive control rename in canvas apps and 2 more
Also changed: Impact · Action required · Retirement of Describe it to design it in Power Automate
NewDeprecation of cross-environment comment import and export [added: After December 31, 2026, the dedicated action for importing and exporting comments between environments in Power Platform component designers, including the model-driven app designer, won't] …
Before: No saved wording on this side.
After: After December 31, 2026, the dedicated action for importing and exporting comments between environments in Power Platform component designers, including the model-driven app designer, won't …
NewImpact [added: After this date, makers can't use the dedicated action to move comments between environments. Commenting within an environment remains available, and existing comments aren't removed.]
Before: No saved wording on this side.
After: After this date, makers can't use the dedicated action to move comments between environments. Commenting within an environment remains available, and existing comments aren't removed.
3 more changed passages · see them all
Observed 30 Oct 23:30 UTC · current page
- Removed link: start from a template
- Power Platform Power Platform deprecations
May need admin actionCheck the dates against your plans.
Changed article references · 1 added · 0 removed
- Added link: start from a template
https://make.powerautomate.com/templates
6 new passages (about 140 words).
New section: Retirement of Describe it to design it in Power Automate
Also changed: Impact · Action required
NewRetirement of Describe it to design it in Power Automate [added: On November 30, 2026, Describe it to design it in Power Automate retires for all customers. This option lets makers create a cloud flow by] …
Before: No saved wording on this side.
After: On November 30, 2026, Describe it to design it in Power Automate retires for all customers. This option lets makers create a cloud flow by …
NewImpact [added: Beginning November 30, 2026, makers can no longer create new cloud flows with Describe it to design it. This retirement doesn't delete or move existing] …
Before: No saved wording on this side.
After: Beginning November 30, 2026, makers can no longer create new cloud flows with Describe it to design it. This retirement doesn't delete or move existing …
3 more changed passages · see them all
Observed 29 Oct 23:08 UTC · current page
- Added link: start from a template
Week of 19 Oct 2026
- Power Platform Power Platform deprecations
May need admin actionCheck the dates against your plans.
9 edited passages (81 words changed).
New sections: Low-density headers in model-driven apps aren't supported as of the October 2021 release · Form footers in model-driven apps aren't supported as of the October 2021 release · Model-driven app controls deprecation (April 2021)
Also changed: The legacy read-only grid in model-driven apps is deprecated · Impact · Action required by you · Low-density headers in model-driven apps won't be supported with the 2021 release wave 2 and 2 more
EditedThe legacy read-only grid in model-driven apps is deprecated The legacy read-only grid control
[removed: has been][added: was] deprecated in model-driven apps with the [added: April] 2022 release[removed: wave 1]. This control is being replaced by … default read-only grid experience for all[removed: environments for]model-driven[removed: apps][added: app environments] with the [added: April] 2022 release[removed: wave 1].Before: The legacy read-only grid control has been deprecated in model-driven apps with the 2022 release wave 1. This control is being replaced by … default read-only grid experience for all environments for model-driven apps with the 2022 release wave 1.
After: The legacy read-only grid control was deprecated in model-driven apps with the April 2022 release. This control is being replaced by … default read-only grid experience for all model-driven app environments with the April 2022 release.
EditedImpact … subgrids. This change started with the [added: April] 2022 release
[removed: wave 1].Before: … subgrids. This change started with the 2022 release wave 1.
After: … subgrids. This change started with the April 2022 release.
3 more changed passages · see them all
Observed 22 Oct 02:22 UTC · current page
- Power Platform Power Platform deprecations
May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices; check the roles and permissions you grant.
86 new passages (about 1980 words).
New sections: Deprecation of Microsoft Dataverse for Teams environments · Timeline · What's the recommended migration path for Dataverse for Teams environments? · Who can upgrade a Dataverse for Teams environment? and 8 more
Also changed: Why is this change needed? · Impact · What isn't affected · Action required and 1 more
NewDeprecation of Microsoft Dataverse for Teams environments [added: Microsoft Dataverse for Teams environments are deprecated. The deprecation happens in three phases. You can't create new Dataverse for Teams environments starting November 15, 2026.] …
Before: No saved wording on this side.
After: Microsoft Dataverse for Teams environments are deprecated. The deprecation happens in three phases. You can't create new Dataverse for Teams environments starting November 15, 2026. …
NewWhy is this change needed? [added: Dataverse for Teams provides a subset of Microsoft Dataverse capabilities. For example, it limits each environment to 2 GB of storage, doesn't provide direct API] …
Before: No saved wording on this side.
After: Dataverse for Teams provides a subset of Microsoft Dataverse capabilities. For example, it limits each environment to 2 GB of storage, doesn't provide direct API …
3 more changed passages · see them all
Observed 19 Oct 00:22 UTC · current page
- Power Platform Power Platform data policies
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
2 edited passages (17 words changed).
EditedVirtual connectors … to turn off various features of
[removed: Copilots and chatbots.][added: agents.]Before: … to turn off various features of Copilots and chatbots.
After: … to turn off various features of agents.
EditedVirtual connectors … (ACP) don't support virtual connectors and
[removed: won't][added: there are no plans to] add support in the future. ACP's … from both data policies and ACP. [added: See Configure skills in the Power Platform admin center.] Desktop Flow virtual connectors are transitioning …Before: … (ACP) don't support virtual connectors and won't add support in the future. ACP's … from both data policies and ACP. Desktop Flow virtual connectors are transitioning …
After: … (ACP) don't support virtual connectors and there are no plans to add support in the future. ACP's … from both data policies and ACP. See Configure skills in the Power Platform admin center. Desktop Flow virtual connectors are transitioning …
Observed 19 Oct 00:22 UTC · current page
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.