Microsoft has adjusted the schedule for making the Adobe Acrobat PDF engine the standard, built-in PDF handler within its Edge browser for business clientele. Initially discussed when the Microsoft and Adobe partnership on PDF handling was unveiled in early 2023, the updated plan now designates September 2025 as the point when this Adobe technology becomes the default for organizations using managed devices (defined as domain-joined or MDM-enrolled).
This change initiates an opt-out phase, moving from the previous opt-in system. Microsoft states this revised timing is “[t]o ensure a quality-driven deployment.” The complete phase-out of the original Microsoft-built PDF engine is now targeted for early 2026, a delay from the previously mentioned early 2025 timeframe.
User Experience Adjustments and Feature Tiers
Edge users utilizing the Adobe engine for PDFs will notice a few subtle differences. A small Adobe brand mark is visible in the bottom-right corner, confirming the engine’s origin (it disappears when zooming and isn’t added to saved/printed files).
Functionally, an “Edit with Acrobat” button appears in the PDF toolbar. Clicking this button without an active, compatible Adobe Acrobat subscription opens an informational pane outlining premium features like text/image editing, file conversion, and document merging, usually alongside a trial offer. Accessing these advanced tools requires a separate paid subscription (Pro or Standard), to cost around $15.59 monthly when paid annually.
However, the core PDF viewing, benefiting from Adobe’s improved rendering accuracy, performance gains, stronger security, and accessibility features, remains free. Existing Acrobat subscribers can use the extension in Edge at no extra cost. Users preferring the legacy interface can temporarily revert via edge://flags/#edge-new-pdf-viewer until the old engine is removed in early 2026.
Managing the Transition in Organizations
The rollout for businesses managing their device fleet is phased. Since March 2023, IT administrators could optionally activate the Adobe engine for testing using the NewPDFReaderEnabled policy via tools like Intune, Group Policy, or SCCM. Beginning September 2025, the Adobe engine becomes standard. Organizations needing more time must then use the same policy to actively opt-out and retain the legacy reader temporarily.
This opt-out is time-limited and will expire before the legacy engine’s final removal in early 2026. To manage user prompts for paid features, Microsoft provides the ShowAcrobatSubscriptionButton policy, allowing admins to hide these upgrade options.
Engine Integration and Technical Scope
Microsoft stresses this integration involves Adobe’s PDF engine, enhancing Edge’s existing built-in PDF reader, not replacing it with the full Acrobat application. They assure feature parity, stating “No functionality will be lost,” and plan further free feature additions. Data privacy is maintained; using the free engine doesn’t store organizational documents on Adobe servers.
The integration applies to Edge on Windows 10 and 11, with macOS support planned. IE mode is unaffected. For WebView2 applications, the PDF experience mirrors the legacy reader, without Adobe branding or upsells. WebView2 behavior can be controlled via the NewPDFReaderWebView2List policy or a developer flag (`msPDFSharedLibrary`). Neither the engine integration nor the optional extension installation changes the system’s default PDF viewer.
Source: Winbuzzer / Digpu NewsTex