Advanced Find ribbon disappears in Dynamics 365 on-premises when Edge disables native XSLT

Ludek Hrebicek 0 Reputation points
2026-10-27T12:51:57.62+00:00

We run Dynamics 365 Customer Engagement on-premises 9.1

(server version 9.1.0048.0004; client version 1.4.11684-v91onpremise).

In the Advanced Find page, the ribbon is displayed in Microsoft Edge 156 when the XSLTEnabled policy is not configured.

When we set the Edge policy XSLTEnabled to Disabled, the ribbon disappears.

The ribbon returns when the policy is set to Enabled.

We also observed the issue in Microsoft Edge 157 Beta, where browser-native XSLT is disabled by default.

Is this a known issue or dependency in Dynamics 365 Customer Engagement on-premises 9.1?

Is there a supported Dynamics update, fix, or workaround that will keep the standard Advanced Find experience working when Edge disables and later removes browser-native XSLT?

Microsoft Edge | Other | Windows 11
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ludek Hrebicek 0 Reputation points
    2026-10-27T14:03:29.28+00:00

    Thanks, but this answer does not resolve the issue - XSLTEnabled policy stops working in Edge version 176 (currently planned for summer 2027).

    But Dynymics 365 9.1 is may be supported to 2029 or 2031, so how we can solve this issue officialy.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-27T12:52:59.5766667+00:00

    Temporarily enable the Edge XSLTEnabled policy for Dynamics 365 users, but open a Dynamics 365 support case because no published Dynamics 365 Customer Engagement on-premises 9.1 update currently documents a permanent XSLT-independent fix for the Advanced Find ribbon.

    Your A/B test establishes that this Advanced Find rendering path depends on browser-native XSLT: disabling XSLT removes the ribbon, and enabling it restores the ribbon. Edge defines the policy exactly this way—Disabled makes XSLT unavailable, Enabled makes it available regardless of browser defaults, and Not configured follows the browser default or field trials.^1^

    Temporary operational workaround

    On managed Windows devices:

    1. Open Group Policy Management.
    2. Go to Administrative Templates → Microsoft Edge.
    3. Set Control the availability of the XSLT feature to Enabled.
    4. Refresh policy on affected clients.
    5. Open edge://policy and verify:
      • XSLTEnabled
      • Value: true
      • Status: no policy error
    6. Reload Advanced Find and verify that its standard ribbon appears.

    The equivalent mandatory registry setting is:

    Path:  HKLM\SOFTWARE\Policies\Microsoft\Edge
Name:  XSLTEnabled
Type:  REG_DWORD
Value: 1

    The policy supports dynamic refresh and is available in Edge 147 and later.^1^

    This is only a bridge. Edge 157 disables native XSLT by default in Canary, Dev, and Beta; Edge 159 does so in Stable. Microsoft plans to stop both the policy mitigation and the XSLT deprecation origin trial in Edge 176.^2^

    Dynamics update status

    Your server build 9.1.0048.0004 is Update 1.48. Its published repair list contains accessibility, security, and security-hardening fixes, but no XSLT or Advanced Find ribbon correction.^3^

    Update 1.49 (9.1.0049.0012) is available, but its public repair list contains only accessibility, security, and reporting fixes; it does not document this compatibility fix.^4^ Microsoft recommends applying the latest 9.1 cumulative update, so plan and test 1.49 for normal servicing, but do not treat it as an established resolution for this symptom.^5^

    Advanced Find in the cited documentation is specifically the legacy web-client experience for Customer Engagement on-premises 9.1.^6^ Although current Edge is listed as supported for on-premises model-driven apps, the published browser-support page does not document an exception or remedy for the XSLT removal.^7^

    Permanent-resolution path

    Open a break-fix case for Dynamics 365 on-premises Customer Engagement and provide:

    • Server and client versions.
    • Edge versions and channels tested.
    • Screenshots with the policy Enabled and Disabled.
    • An edge://policy export.
    • A browser trace or DevTools console/network capture from loading Advanced Find with XSLT disabled.
    • Confirmation that the standard, uncustomized Advanced Find ribbon is affected.
    • The Edge 176 removal deadline.
    • A request for a supported hotfix or product statement covering the legacy Advanced Find dependency.

    Dynamics 365 Customer Engagement 9.x on-premises remains in Mainstream Support until January 12, 2027, during which customers can request non-security updates and incident support.^8^ Dynamics on-premises cases are submitted through Support for Business or the applicable Premier/Unified support route.^9^

    Do not deploy an unverified browser extension or modify Dynamics application files to polyfill XSLT; neither is documented here as a supported Dynamics correction. If Microsoft does not release a product fix before Edge 176, maintaining the standard legacy Advanced Find experience will require a Microsoft-provided remediation or migration away from that XSLT-dependent client path.

    References

    1. Microsoft Edge Browser Policy Documentation XSLTEnabled
    2. Microsoft Edge release notes for Stable and Extended Stable Channels
    3. Service Update 1.48 for Microsoft Dynamics CRM (on-premises) 9.1 | Microsoft Support
    4. Service Update 1.49 for Microsoft Dynamics CRM (on-premises) 9.1 | Microsoft Support
    5. Microsoft Dynamics 365 On-Premises Cumulative Updates | Microsoft Support
    6. Create, edit, or save an Advanced Find search
    7. Supported web browsers and mobile devices
    8. Support extended for Dynamics 365 for Customer Engagement Apps, v9 (on-premises)
    9. Support and billing overview
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.