Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 274/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 17:22 UTC Customize Public modeDiscuss ChangeIntel on Discord

Power Apps: Control information density in model-driven apps

Microsoft 365 Message Center Archive by Merill Fernando

Changes ChangeIntel observed

last 90 days

Observed refresh times show when ChangeIntel detected a change. Source creation and modification times appear in Overview. Targets retain month precision.

No status or target changes observed in the last 90 days.

What changed

  1. Clouds: GCC, GCC High, Worldwide (Standard Multi-Tenant) → Worldwide (Standard Multi-Tenant), GCC, GCC High · Preview target: Not stated → September CY2026 · Availability target: Not stated → November CY2026
  2. Clouds: Worldwide (Standard Multi-Tenant), GCC, GCC High → GCC, GCC High, Worldwide (Standard Multi-Tenant) · Preview target: September CY2026 → Not stated · Availability target: November CY2026 → Not stated
  3. Clouds: GCC, GCC High, Worldwide (Standard Multi-Tenant) → Worldwide (Standard Multi-Tenant), GCC, GCC High · Preview target: Not stated → September CY2026 · Availability target: Not stated → November CY2026
  4. Clouds: Worldwide (Standard Multi-Tenant), GCC, GCC High → GCC, GCC High, Worldwide (Standard Multi-Tenant) · Preview target: September CY2026 → Not stated · Availability target: November CY2026 → Not stated
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (65)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 5 Nov 2026 · 18:04:05 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  2. 5 Nov 2026 · 17:01:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  3. 4 Nov 2026 · 15:02:25 UTC Last changed23 Sep 2026 22:59 UTC → 13 Oct 2026 23:01 UTC
  4. 4 Nov 2026 · 15:02:25 UTC CloudsGCC, GCC High, Worldwide (Standard Multi-Tenant) → Worldwide (Standard Multi-Tenant), GCC, GCC High
  5. 4 Nov 2026 · 15:02:25 UTC Preview targetNot stated → September CY2026
  6. 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → November CY2026
  7. 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  8. 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
  9. 4 Nov 2026 · 15:02:25 UTC Link: Supporting referencehttps://learn.microsoft.com/en-us/power-apps/user/appearance-settings
  10. 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=572682
  11. 4 Nov 2026 · 15:02:25 UTC SummaryModel-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: → Model-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: Comfortable (default) Cozy Compact ​ Each density setting adjusts layout spacing while maintaining accessibility target-size requirements. Administrators and makers can configure default density settings at the environment and app level, while individual users can personalize the experience by selecting their preferred density. User preferences take precedence over administrator-configured defaults. ​ Display density requires the Header and Navigation Refresh experience to be enabled, and will be enabled by default for apps that have Header and Navigation Refresh enabled. Makers can disable display density for their apps using the app setting if needed. ​ Some controls and components may not yet support display density. These controls will continue to render using their standard spacing regardless of the selected density setting. Custom component developers can add support for display density by adopting Fluent design spacing tokens. Learn more in the documentation. ​ Availability Field: Value A…
  12. 4 Nov 2026 · 13:26:53 UTC Last changed13 Oct 2026 23:01 UTC → 23 Sep 2026 22:59 UTC
  13. 4 Nov 2026 · 13:26:53 UTC CloudsWorldwide (Standard Multi-Tenant), GCC, GCC High → GCC, GCC High, Worldwide (Standard Multi-Tenant)
  14. 4 Nov 2026 · 13:26:53 UTC Preview targetSeptember CY2026 → Not stated
  15. 4 Nov 2026 · 13:26:53 UTC General availability targetNovember CY2026 → Not stated
  16. 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  17. 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
  18. 4 Nov 2026 · 13:26:53 UTC Link: Supporting referencehttps://learn.microsoft.com/en-us/power-apps/user/appearance-settings → No longer listed in this observation
  19. 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=572682 → No longer listed in this observation
  20. 4 Nov 2026 · 13:26:53 UTC SummaryModel-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: Comfortable (default) Cozy Compact ​ Each density setting adjusts layout spacing while maintaining accessibility target-size requirements. Administrators and makers can configure default density settings at the environment and app level, while individual users can personalize the experience by selecting their preferred density. User preferences take precedence over administrator-configured defaults. ​ Display density requires the Header and Navigation Refresh experience to be enabled, and will be enabled by default for apps that have Header and Navigation Refresh enabled. Makers can disable display density for their apps using the app setting if needed. ​ Some controls and components may not yet support display density. These controls will continue to render using their standard spacing regardless of the selected density setting. Custom component developers can add support for display density by adopting Fluent design spacing tokens. Learn more in the documentation. ​ Availability Field: Value A… → Model-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options:
  21. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  22. 4 Nov 2026 · 11:04:04 UTC Last changed23 Sep 2026 22:59 UTC → 13 Oct 2026 23:01 UTC
  23. 4 Nov 2026 · 11:04:04 UTC CloudsGCC, GCC High, Worldwide (Standard Multi-Tenant) → Worldwide (Standard Multi-Tenant), GCC, GCC High
  24. 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → September CY2026
  25. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → November CY2026
  26. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  27. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  28. 4 Nov 2026 · 11:04:04 UTC Link: Supporting referencehttps://learn.microsoft.com/en-us/power-apps/user/appearance-settings
  29. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=572682
  30. 4 Nov 2026 · 11:04:04 UTC SummaryModel-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: → Model-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: Comfortable (default) Cozy Compact ​ Each density setting adjusts layout spacing while maintaining accessibility target-size requirements. Administrators and makers can configure default density settings at the environment and app level, while individual users can personalize the experience by selecting their preferred density. User preferences take precedence over administrator-configured defaults. ​ Display density requires the Header and Navigation Refresh experience to be enabled, and will be enabled by default for apps that have Header and Navigation Refresh enabled. Makers can disable display density for their apps using the app setting if needed. ​ Some controls and components may not yet support display density. These controls will continue to render using their standard spacing regardless of the selected density setting. Custom component developers can add support for display density by adopting Fluent design spacing tokens. Learn more in the documentation. ​ Availability Field: Value A…
  31. 4 Nov 2026 · 10:01:18 UTC Last changed13 Oct 2026 23:01 UTC → 23 Sep 2026 22:59 UTC
  32. 4 Nov 2026 · 10:01:18 UTC CloudsWorldwide (Standard Multi-Tenant), GCC, GCC High → GCC, GCC High, Worldwide (Standard Multi-Tenant)
  33. 4 Nov 2026 · 10:01:18 UTC Preview targetSeptember CY2026 → Not stated
  34. 4 Nov 2026 · 10:01:18 UTC General availability targetNovember CY2026 → Not stated
  35. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  36. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  37. 4 Nov 2026 · 10:01:18 UTC Link: Supporting referencehttps://learn.microsoft.com/en-us/power-apps/user/appearance-settings → No longer listed in this observation
  38. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=572682 → No longer listed in this observation
  39. 4 Nov 2026 · 10:01:18 UTC SummaryModel-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: Comfortable (default) Cozy Compact ​ Each density setting adjusts layout spacing while maintaining accessibility target-size requirements. Administrators and makers can configure default density settings at the environment and app level, while individual users can personalize the experience by selecting their preferred density. User preferences take precedence over administrator-configured defaults. ​ Display density requires the Header and Navigation Refresh experience to be enabled, and will be enabled by default for apps that have Header and Navigation Refresh enabled. Makers can disable display density for their apps using the app setting if needed. ​ Some controls and components may not yet support display density. These controls will continue to render using their standard spacing regardless of the selected density setting. Custom component developers can add support for display density by adopting Fluent design spacing tokens. Learn more in the documentation. ​ Availability Field: Value A… → Model-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options:
  40. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  41. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  42. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  43. 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=572682 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=572682
  44. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  45. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  46. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM572682
  47. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  48. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  49. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  50. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  51. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  52. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  53. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  54. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  55. 22 Oct 2026 · 13:46:28 UTC Link: Supporting referencehttps://learn.microsoft.com/en-us/power-apps/user/appearance-settings
  56. 22 Oct 2026 · 13:46:28 UTC SummaryModel-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: Comfortable (default) Cozy Compact ​ Each density setting adjusts layout spacing while maintaining accessibility target-size requirements. Administrators and makers can configure default density settings at the environment and app level, while individual users can personalize the experience by selecting their preferred density. User preferences take precedence over administrator-configured defaults. ​ Display density requires the Header and Navigation Refresh experience to be enabled, and will be enabled by default for apps that have Header and Navigation Refresh enabled. Makers can disable display density for their apps using the app setting if needed. ​ Some controls and components may not yet support display density. These controls will continue to render using their standard spacing regardless of the selected density setting. Custom component developers can add support for display density by adopting Fluent design spacing tokens. Learn more in the documentation. ​ Availability Field Value Ap… → Model-driven apps now support configurable display density settings that let users choose how information is spaced throughout the application. Users can select from three density options: Comfortable (default) Cozy Compact ​ Each density setting adjusts layout spacing while maintaining accessibility target-size requirements. Administrators and makers can configure default density settings at the environment and app level, while individual users can personalize the experience by selecting their preferred density. User preferences take precedence over administrator-configured defaults. ​ Display density requires the Header and Navigation Refresh experience to be enabled, and will be enabled by default for apps that have Header and Navigation Refresh enabled. Makers can disable display density for their apps using the app setting if needed. ​ Some controls and components may not yet support display density. These controls will continue to render using their standard spacing regardless of the selected density setting. Custom component developers can add support for display density by adopting Fluent design spacing tokens. Learn more in the documentation. ​ Availability Field: Value A…
  57. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  58. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  59. 18 Oct 2026 · 14:54:30 UTC Link: Power Apps/roadmap?topic=Power%20Apps&period=all#items
  60. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  61. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  62. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  63. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  64. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  65. 14 Oct 2026 · 11:22:42 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 11 Nov 17:22 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current