Centralized deployment officeJS add-in unsuccessful

Question

Centralized deployment officeJS add-in unsuccessful

Yvo Heijltjes 20

After uploading an manifest (xml) we get an error saying:

This operation was unsuccessful - reasons may include:

learn more about eligibility requirements

The manifest does work when sideloading but not when trying to use centralized deployment.
We are using an SPA hosted on a azure static web app.

The add-in is of type "Document" (Word)

Deployment is done by a global admin with rights to custom apps and app marketplace through an admin role.

Things i have done to validate:

Checked application ID URI
Checked application scopes
Checked api permissions
Checked expose an api settings
Checked everything specified here
Checked everything specified here

Unfortunately no luck on any of the above.

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Flora-T 6,895 Microsoft External Staff Moderator

Hi Yvo Heijltjes

Thank you for reaching out to Microsoft Q&A Forum and sharing your issue with the centralized deployment of your OfficeJS add-in.

Based on what you've shared, you've already thoroughly checked key areas like eligibility requirements, application ID URI, scopes, API permissions, expose an API settings, and the guidelines.

Even as a global admin, confirm you have explicit rights to deploy custom apps and access the marketplace. You can check in the Microsoft 365 Admin Center under Settings > Org Settings > Services > Office Add-ins to ensure centralized deployment is enabled. Look out for any conditional access policies or group restrictions in Azure AD that might be interfering.

I also tried to look for related articles, but you’ve already provided them.

Meanwhile, I've done some research on similar error codes, I found a user's suggestion that resolved the issue for them by using another Global Administrator account to deploy the add-in. You may consider trying this to see if it resolves your issue.

I truly appreciate your effort in troubleshooting this, and I hope it helps resolve your situation.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Flora-T 6,895 Reputation points Microsoft External Staff Moderator

2025-10-20T07:00:34.64+00:00

Hi Yvo Heijltjes

I hope you're doing well.

I just wanted to check in and see if you had a chance to review my previous reply.

If you have any other questions, please feel free to reach out again.
Yvo Heijltjes 20 Reputation points

2025-10-20T15:51:33.8966667+00:00
Hi Flora-T,

We have checked the following things and unfortunately no luck:

Logged in through another global admin account - same error (eligibility requirements)

Also in the org settings the following:

We also tried to use centralized deployment to add an add-in from the marketplace to 1 (the same as before) user. This did work.
Flora-T 6,895 Reputation points Microsoft External Staff Moderator

2025-10-21T06:52:14.4333333+00:00
Hi Yvo Heijltjes
Thanks for the update.

Based on what you've shared, you’ve already tried another global admin account and successfully deployed a marketplace add-in to a user.

From the screenshots you provided of your Org settings, please double-check "User owned apps and services" to see if the “Let users access the Office Store” option is checked. This setting controls whether users and admins can access the Office Store and deploy custom add-ins.

Centralized Deployment enforces requirements:

HTTPS endpoints for all resources.

Valid AppSource or custom app IDs.

Correct <SourceLocation> and <Id> values in the manifest (ensure the <Id> matches your Azure AD app's client ID exactly).

If the setting is enabled and the issue persists, the next step is to:

Re-validate your manifest thoroughly using the official tool at Validate your manifest with office-addin-manifest. - Test with a simplified manifest by temporarily removing SSO elements to isolate if that's causing the eligibility failure.
Yvo Heijltjes 20 Reputation points

2025-10-21T12:47:20.1+00:00

Hi @Flora-T ,

thanks for your time, we have fixxed the issue by some more checks along with the documentation on mslearn.

Another question related to OfficeJS itself:
When loading in a document through the createDocument() function i try to retrieve the contentControls.

All contentControls show up as long as they are not in the footer, how can i retrieve those? The header's contentControls do load.
Yvo Heijltjes 20 Reputation points

2025-10-21T14:18:30.11+00:00

After some further investigation i concluded the following:

The contentControl is inside a textbox which is inside a footer, however they do not show up in document.contentControls.

When i try to target the individual shape.body the contentControls is empty and the "text" is my placeholder text.

Structure is as following:
Document >> section >> footer >> shapes.items[0] >> body: text = placeholder, contentControls is empty

Is there any way to target and modify this contentControl through officejs?
Flora-T 6,895 Reputation points Microsoft External Staff Moderator

2025-10-22T10:26:18.8866667+00:00
Hi Yvo Heijltjes

Thank you for the detailed explanation and investigation.

What you’re seeing is expected behavior with the current Word JavaScript API (Office.js). Content controls inside shapes (such as text boxes in headers or footers) are not surfaced when you call context.document.contentControls. This is a known limitation because the API treats text boxes as shapes, and their internal content is not part of the main document body or the header/footer content control collection.

document.contentControls only enumerates controls in the main body, headers, and footers, not inside shapes.

A text box in a footer is represented as a Word.Shape object, and its text resides in shape.body, which is a separate Word.Body object.

The shape.body.contentControls collection does not currently return nested content controls.

For your reference, you can review the API details here:

Word.Shape class

Word.ContentControl class

If this scenario is important for your solution, the best way to influence future improvements is to submit feedback directly through the official Feedback Portal. This helps the product team prioritize features based on customer demand.

If you found this discussion useful and feel it addresses your concern, even in part, you could consider accepting my initial answer. Doing so helps others in the community who may be facing similar issues find it more easily and brings visibility to this discussion.

I truly appreciate your time and contribution.

Share via

Centralized deployment officeJS add-in unsuccessful

0 additional answers

Your answer