💡 Our Technical Review in summary
Summary
- Starting in October 2025 with Microsoft Edge version 141, the Adobe-powered PDF viewer will become the default PDF experience for enterprise users on Windows.
- This update replaces the legacy Microsoft Edge PDF engine to provide enhanced performance, improved accessibility, and better document compatibility.
- The transition follows a phased rollout schedule, beginning in October 2025 and reaching completion by March 2026.
Impact
- User Experience: While the underlying engine changes, the user interface and primary controls will remain familiar to users to minimize workflow disruption.
- Enterprise Features: The new viewer introduces exclusive enterprise-grade features and better alignment with modern PDF standards.
- WebView2 Applications: The change also extends to WebView2 apps, which can be managed via dedicated administrative policies.
- Policy Changes: The default value for PDF rendering will switch from the legacy viewer to the Adobe-powered viewer unless explicitly overridden by group policy.
- Sunset Timeline: Organizations can opt-out of this change until June 2026. After this date, the legacy engine will be deprecated, and the Adobe-powered viewer will become mandatory.
Action Required
- Early Adoption: To ensure compatibility with internal workflows, admins are encouraged to enable the
NewPDFReaderEnabledpolicy for a pilot group before the October 2025 rollout. - Policy Configuration:
- To opt-in early: Set
NewPDFReaderEnabledto Enabled. - To opt-out (temporary): Set
NewPDFReaderEnabledto Disabled (supported until June 2026). - For WebView2 control: Configure the
NewPDFReaderWebView2Listpolicy as needed for specific applications.
- To opt-in early: Set
- Support Readiness: Update internal IT documentation and notify helpdesk personnel about the change in the PDF rendering engine to handle potential user inquiries.
- Compatibility Review: Test critical PDF-based business processes (such as forms or digital signatures) to ensure they function correctly within the new Adobe-powered environment.
Microsoft Official Update
Service: N/A
Category: planForChange
Severity: normal
[Introduction]
Starting in October 2025, Microsoft Edge version 141 will introduce the Adobe-powered PDF viewer as the default experience for enterprise users on Windows. This change enhances performance, accessibility, and compatibility, and introduces exclusive enterprise features. It follows our earlier public announcement and aligns with Roadmap ID 489231 and MC post MC1072406.
General Availability: Migration will occur on a phased rollout. Rollout will begin October 2025 and will complete March 2026.
[How this affects your organization:]
Who is affected:
- All enterprise users on Windows using Microsoft Edge.
What will happen:
- The Adobe-powered PDF viewer will replace the legacy viewer as the default experience.
- User interface and controls will remain unchanged.
- The new viewer offers improved performance, accessibility, compatibility, and exclusive enterprise features.
Admins can manage the experience using two policies:
NewPDFReaderEnabled: Controls the default viewer in Edge for Windows.
NewPDFReaderWebView2List: Controls viewer behavior in WebView2 apps.
Policy behavior:
| Policy State | Before Enablement by Default | After Enablement by Default |
|---|---|---|
| Default | Old PDF Viewer | New PDF Viewer |
| Enabled | New PDF Viewer | New PDF Viewer |
| Disabled | Old PDF Viewer | Old PDF Viewer |
[What you can do to prepare:]
No action is required if your organization is ready to adopt the new viewer.
If you wish to manage the experience:
- Enable the new viewer early using the NewPDFReaderEnabled policy.
- Opt-out by disabling the same policy. Opt-out will be supported until June 2026, at which time the policy will be deprecated and any remaining organizations will be moved to the new viewer.
- Review and update internal documentation if needed.
- Communicate this change to helpdesk or support teams.
Learn more: Microsoft Edge and Adobe partner to improve the PDF experience.
For support, contact your Microsoft CSAM or CSS representative.
