Word Similarity Checker fails in desktop and web: “Something went wrong”

Hello,

I am having an issue with Microsoft Word Similarity Checker. The Similarity Checker consistently fails with the message:

“Something went wrong. Try again.”

This happens in both:

- Microsoft Word desktop

- Word for the web / Microsoft 365 web version

Product/account details:

- Microsoft 365 subscription is active

- Word shows activated under File > Account

- Connected experiences are enabled

- Word desktop version: Microsoft 365 Apps, Version 2606, Build 20131.20112 Click-to-Run Current Channel

Troubleshooting already completed:

1. Confirmed Word is activated under File > Account.

2. Confirmed connected experiences are enabled:

- Experiences that analyze your content: ON

- Experiences that download online content: ON

- All connected experiences: ON

3. Ran Office Update Now.

4. Restarted Windows.

5. Ran Quick Repair.

6. Ran Online Repair.

7. Tested in a brand-new blank Word document.

8. Tested on mobile hotspot instead of normal network.

9. Confirmed ProtonVPN was turned off.

10. Cleared Office Wef cache contents at:

%LOCALAPPDATA%\Microsoft\Office\16.0\Wef\

11. Checked Microsoft Edge WebView2 Runtime. The installer says it is already installed for the system.

12. Signed out of Word/Microsoft 365, restarted Windows, and signed back in.

13. Tested again in Word desktop.

14. Tested again in Word for the web.

15. The same “Something went wrong. Try again” Similarity Checker error still occurs.

I also previously saw a script error when clicking Update License in Word:

URL shown included:

https://oc.officeapps.live.com/odc/v2.1/hrd

Error:

'Hrd' is undefined

Because the issue occurs in both desktop Word and Word for the web after these troubleshooting steps, this seems like a Microsoft 365/Word Similarity Checker service-side or account-side issue rather than a local installation problem.

Can someone from Microsoft confirm whether there is a known issue with Similarity Checker right now, or whether this needs to be escalated as an account/service-side problem?