According to the official rollout timeline on this page, the phased rollout of the new Adobe‑based PDF viewer for managed devices was supposed to be completed by the end of February 2026. In our environment, the new PDF viewer is still not active over all devices, even though the NewPDFReaderEnabled policy is NOT disabled (neither via GPO, Intune...). Can Microsoft explain why the new PDF viewer is still not enabled in all managed environments despite the stated rollout completion date? Specifically:
- Are there ongoing quality holdbacks or known blocking issues?
- Are certain managed scenarios (e.g. specific Edge versions, WebView2 dependencies, tenant characteristics, or device states) intentionally excluded?
- Is the “February 2026” milestone no longer valid for all customers, and if so, what criteria determine delayed activation?