OneDrive EmbedView blank white screen – odsp.react.lib-8e01e1f0.js returns 404

Question

OneDrive EmbedView blank white screen – odsp.react.lib-8e01e1f0.js returns 404

Expertus 20

Hello,

It looks like the OneDrive / Office EmbedView issue with odsp.react.lib has returned.

Today, November 2, 2026, our embedded OneDrive document started showing only a blank white screen.

We verified that this is not caused by our website or iframe implementation. The same issue occurs when the OneDrive embed URL is opened directly in a new browser tab:

https://1drv.ms/w/c/0d94d008cde7a10b/IQRSu1_kfuibQJq1S5um47KqAblxtb70uWsBNJI1eWtSfqY?em=2

The URL redirects to onedrive.live.com, but the viewer remains blank.

In browser DevTools → Network, OneDrive tries to load this Microsoft resource:

https://res-1.cdn.office.net/files/sp-client/odsp.react.lib-8e01e1f0.js

The request returns:

404 Not Found

Details:

Host: res-1.cdn.office.net

Resource: odsp.react.lib-8e01e1f0.js

Status: 404 Not Found

Origin: https://onedrive.live.com

Referrer: https://onedrive.live.com/

CDN provider: Akamai

Result: blank white OneDrive / Office Viewer page

This looks very similar to the OneDrive EmbedView incident from August 2026, when another version of the same odsp.react.lib dependency was missing from the Microsoft CDN and EmbedView failed to initialize.

The important point is that the issue reproduces even when the OneDrive URL is opened directly, outside our website.

Could Microsoft please check whether odsp.react.lib-8e01e1f0.js is currently missing or incorrectly deployed on the Office CDN?

Is anyone else seeing the same issue today?

I can provide screenshots from DevTools showing the 404 response and request headers.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hello,

Just to clear things up right away since you asked Microsoft to check this out, this is a public forum staffed by users just like you, not Microsoft employees. We cannot poke around their servers or redeploy files to the CDN.

Your devtools trace is spot on and proves the issue is completely on their end. Since you are seeing a literal 404 from the Akamai edge on that react script even when bypassing your iframe, there is zero you can do to fix this locally. You are just going to have to wait for the server side fix like the last time this happened.

The fastest way to get their engineers to notice the missing file is to send those exact headers and network logs through the feedback option inside the OneDrive web portal or open a support ticket in your Microsoft 365 Admin Center if this is a business tenant.