Description:

Customers using Dynamics 365 Customer Service and Power Pages have experienced issues where collapsible panels in Knowledge Articles do not render or expand correctly after platform updates. This impacted both DEV/TEST and eventually Production environments, affecting externally facing portals used by audit service providers. As a result, critical content such as procedural guidance embedded within collapsible panels became inaccessible to users, directly impacting business operations and regulated audit processes.

In this case, the issue was confirmed as a platform regression introduced in a recent release, with a fix planned for a future update. However, customers faced challenges due to lack of visibility into the change, inability to control deployment sequencing, and absence of confirmation mechanisms once the fix is applied.

Current Limitation:

• There is no visibility into the version of key components (e.g., Rich Text Editor or rendering engine) at the environment level to help correlate behavior changes with platform updates.
• Customers do not receive targeted or advance notifications for UI/editor changes that may impact rendering behavior.
• There is no built-in mechanism to confirm when a specific fix has been deployed to an environment.
• It is not possible to control or request staged rollout of fixes to lower environments (DEV/TEST) prior to Production.
• Workarounds (e.g., manual HTML/CSS adjustments) may need to be revisited after updates, with no guarantee of forward compatibility.

Potential Suggested Improvement:

• Provide environment-level visibility of component and editor versions to help customers track and diagnose behavior changes.
• Introduce targeted change notifications for updates that may affect rendering, UI behavior, or existing content.
• Offer a clear deployment confirmation mechanism (e.g., admin portal indicator, API signal, or audit log entry) to verify when fixes are applied.
• Enable more controlled rollout options, such as staging fixes to lower environments before Production where feasible.
• Improve communication on compatibility of customer-side workarounds with upcoming platform fixes to help customers plan remediation efforts.