Forum Discussion
Store-published Word add-in can't read or write the open document
We published a Word add-in to the Microsoft Store and ran into something odd that I'm hoping someone here has seen before.
The add-in installs and opens fine. Signing in, the chat assistant, browsing our documents, moving between tabs ; all of that works.
The problem is anything that has to actually read or change the open Word document. Pulling a doc in from our Sync tab, dropping in a template, running a compliance check on the current document ; none of it does anything. No error, no message, it just doesn't happen.
So basically if a feature only shows stuff or talks to our own server it's fine, but the second it needs the actual document, nothing.
A few things I'm trying to figure out:
- Is this a known thing with Store-installed add-ins vs when you're just testing it?
- Any good way to see why those actions are failing when nothing shows up on screen?
Happy to share more detail. Thanks in advance.
1 Reply
Hi, I’d compare the Store-published manifest with the sideloaded or development manifest first. For Word add-ins that need document access, the manifest permissions and requirement sets matter a lot. Make sure the add-in declares the correct document read/write permission and that the API calls you use are supported by the Word client and platform where the issue happens. I’d also test whether the document is in Protected View, read-only mode, sensitivity-label restricted, or opened from a location that limits editing. If it works sideloaded but not from the Store, the packaged manifest or validation path is where I’d look first.
