Office.js has no changelog. Microsoft ships new builds to its CDN edge by edge, and the first sign of a change is usually an add-in that behaves differently. I run silentship, which samples the Office.js CDN every 10 minutes and compares the public API surface of each new build with the previous one. This week there were two things worth writing up: a new build, and a quiet change to the advice about which CDN URL to use.
1. Office.js 16.0.20710: what changed
Build 16.0.20710.15050 finished rolling out on 20 November on both the production and beta tracks. No documented API was removed and no signature changed. Two changes matter to add-in developers.
allowTextToOverflow on Excel chart data labels, ahead of the docs
All six Excel host files (Windows, Mac, web, iOS, Android, WinRT) now have allowTextToOverflow on both Excel.ChartDataLabel and Excel.ChartDataLabels. It is a regular scalar property: getter, setter, loadable, included in set() and toJSON().
It is not documented yet, and neither @types/office-js (1.0.617) nor @types/office-js-preview (1.0.738) knows about it, so TypeScript won't either. In the code it sits behind a requirement check for version 1.20, the same way the data-label properties from ExcelApi 1.19 (such as geometricShapeType) sit behind "1.19". So it most likely belongs to ExcelApi 1.20.
From the name, it probably controls whether label text may run outside its shape. That's a guess until Microsoft documents it. Until then, don't ship code that depends on it. If you want to experiment, check for it first:
const canTry =
Office.context.requirements.isSetSupported("ExcelApi", "1.20") &&
"allowTextToOverflow" in Excel.ChartDataLabel.prototype;
Office.ribbon.requestUpdate got a new body
This one is easy to miss. Office.ribbon.requestUpdate (RibbonApi 1.1) is how add-ins show and update contextual tabs and enable or disable ribbon buttons. In this build its implementation changed while its signature stayed the same.
Same signature means your code still compiles and calls it the same way. A new body means the behaviour may differ. If your add-in uses contextual tabs or toggles button states, test them on this build.
(A side note on tooling: my own classifier first labelled this method "undocumented". The type definitions describe it on the Office.Ribbon interface, but at runtime it lives on the Office.ribbon object, and the catalogue didn't connect the two. It does now, for Office.ribbon, Office.context.* and other APIs you reach through an object rather than a class.)
Noise you can ignore
set() and toJSON() on both data-label classes also changed. I compared the old and new versions of those methods, and the only difference is one more name in the list of properties they handle. These methods are generated and list every property of their class, so they change whenever a property is added or removed. They don't do anything new. silentship now treats this kind of change as a side effect of the new member and rates it low.
Everything else was in undocumented internals that add-ins shouldn't touch:
| Change | Member |
|---|---|
| added |
Office.api, OfficeCore.ApiVersionService, OfficeExtension.MarkOfAi
|
| removed |
launchAgent from Office.ExtensionLifeCycle and OfficeCore.ExtensionLifeCycle, Excel.ActionCellValueType
|
| new body |
OfficeCore.DimeApi.launch, Excel.CustomFunctionProxy
|
How the rollout went
| Production | Beta | |
|---|---|---|
| First seen | 16 Nov, 22:30 UTC | 16 Nov, 22:30 UTC |
Complete on appsforoffice
|
20 Nov, 10:10 UTC | 20 Nov, 06:50 UTC |
| Complete on OneCDN | 20 Nov, 10:50 UTC | 20 Nov, 11:40 UTC |
It took about three and a half days from the first sighting to every sampled edge. It also overlapped with the previous build: 16.0.20710 appeared before 16.0.20702 had finished rolling out, and some edges went straight from 16.0.20626 to 16.0.20710. For a few days, the same add-in could load any of three builds, depending on which edge answered. If a user reports a bug you can't reproduce during a week like this, that may be why.
2. Microsoft quietly went back to appsforoffice.microsoft.com
From September to November 2026, Microsoft's docs called appsforoffice.microsoft.com a legacy endpoint and recommended a new one:
appsforoffice |
OneCDN | |
|---|---|---|
| Release | appsforoffice.microsoft.com/lib/1/hosted/office.js |
officeapis.public.onecdn.static.microsoft/1/office.js |
| Preview | appsforoffice.microsoft.com/lib/beta/hosted/office.js |
officeapis.public.onecdn.static.microsoft/beta/office.js |
On 19 November Microsoft reverted its docs. They now point at appsforoffice.microsoft.com everywhere again. The new endpoint and the migration steps are gone, and no reason was given.
What the new endpoint actually changed
The docs said the new endpoint "enables additional secure defaults" but never said which. When I compared the two endpoints (first on 16.0.20606, again on 16.0.20710):
- Same build on both.
-
Host files are byte-identical.
excel-win32-16.01.js,word-win32-16.01.jsand the rest have the same SHA-256. Every Office API you call comes from the same code. -
Only the loader
office.jsdiffers, by two lines at the top:
isOsfSecurityDefaultsEnabled = true;
osfLoadMsAjax = false;
With these set, the loader doesn't load MicrosoftAjax and creates a Trusted Types policy named officejs. The host files also look up function commands (ExecuteFunction in the manifest) only among handlers registered with Office.actions.associate(...), with no fallback to a global function of the same name on window.
What it means for you now
-
You never moved: nothing to do.
appsforoffice.microsoft.comis the documented URL again. - You moved to OneCDN: your add-in keeps working. The endpoint hasn't changed and still serves the same files. It's just on a URL the docs no longer mention. Moving back is a one-line change, and since the API code is identical, the only difference you'd notice is the two loader defaults above.
-
Everyone: the defaults the new endpoint turned on are still worth testing against, because nothing stops them from appearing in the
appsforofficeloader one day. The things that break are:- code (yours or a dependency's) that relies on MicrosoftAjax globals without knowing it:
Sys.*,Type.registerNamespace,Function.createDelegate,$create. Search your bundle, not just your source:
grep -rnE '\bSys\.|Type\.registerNamespace|Function\.createDelegate|\$create\(' dist/- function commands defined only as plain globals. Register them with
Office.actions.associate("onAction", onAction). - a strict CSP with Trusted Types, which needs to allow the
officejspolicy.
- code (yours or a dependency's) that relies on MicrosoftAjax globals without knowing it:
You can try the same defaults on the documented URL in a test build by setting the globals yourself before the loader:
<script>
var isOsfSecurityDefaultsEnabled = true;
var osfLoadMsAjax = false;
</script>
<script src="https://appsforoffice.microsoft.com/lib/1/hosted/office.js"></script>
I read this from the code and haven't tested it in every host, so use it to find hidden dependencies in a test build, not as a production setting. The full write-up covers the data-enable-trusted-types and data-use-associated-actions-only attributes, which have a gotcha: "true" turns the feature off, and only "1" turns it on.
Why I keep watching this
Both of this week's stories have the same shape: something changed on the CDN, or in what the docs say about it, and nothing announced it. An undocumented property showed up in production before the types knew about it. A documented ribbon method changed inside. A recommended endpoint stopped being recommended two months after it was introduced.
silentship watches both endpoints and both tracks and alerts by email or Slack when a build changes an API you use. You can set a watchlist and a minimum severity, so you only hear about what affects your add-in. A change to either loader flag on either endpoint counts as high.
Full data for this build: production rollout · beta rollout · Excel.ChartDataLabel · RSS
Checked on 20–21 Nov 2026 against build 16.0.20710.15050.
Top comments (0)