Claude (Anthropic) Office add-ins won't deploy via Integrated Apps — Business Standard tenant, stuck on "Deployment failed"
Hoping someone here has run into this before, because I've been going in circles for a while. Setup: Microsoft 365 Business Standard tenant. I'm Global Admin (permanent assignment, not PIM — we don't have Entra ID P2/Governance so PIM isn't even in play).…
Hoping someone here has run into this before, because I've been going in circles for a while. Setup: Microsoft 365 Business Standard tenant. I'm Global Admin (permanent assignment, not PIM — we don't have Entra ID P2/Governance so PIM isn't even in play). Trying to centrally deploy the "Claude for Microsoft 365" AppSource listing (bundles Word/Excel/PowerPoint) and separately "Claude for Outlook" (beta) via Microsoft 365 Admin Center > Settings > Integrated Apps. What happens: Deployment fails every time with "Deployment failed." Digging into the network trace, the backend response is: FailedWriteToExchange, with ResponseResultDetails.Code = AddInStoreUnavailable On a separate attempt I got a different, more generic error: "This operation was unsuccessful" pointing vaguely at permission/eligibility requirements, different correlation ID. What I've already ruled out: Global Admin role — confirmed, permanent assignment, not PIM-eligible Exchange RBAC "Org Marketplace Apps" role — already active on my account License eligibility — Business Standard is on Microsoft's own supported list for centralized deployment Tried both the "Get apps" flow and the "Deploy Add-in" flow in Integrated Apps — identical failure Tried assigning to "Entire organization" vs. "Just yourself" — identical failure both times, so it's not a bad user/group in a bulk assignment No admin consent / permissions popup ever even appears before the failure, so it's not stuck in a consent handshake Anthropic also provides a manifest XML file per app (Word/Excel/PowerPoint/Outlook) as an alternate upload-based deployment method, bypassing the AppSource catalog entirely — I haven't tried that route yet and would rather avoid it for now if there's a proper fix for the standard flow. At this point it really looks like something backend-side (Microsoft's AppSource/Exchange write path, or possibly something specific to how this app is categorized/registered in AppSource), rather than anything fixable from the tenant admin side. About to open a Microsoft support ticket, but figured I'd ask here first since it's usually faster. Has anyone successfully deployed the Claude Office add-ins (Word/Excel/PowerPoint/Outlook) on a Business Standard tenant? Or seen AddInStoreUnavailable before with a different app? Any known fix appreciated. (Note: I used AI to help translate and polish this post — English isn't my first language.)
已收录讨论
That's not very helpfull.
No specifically to the Claude add-ins, i've seen deployments not work where I had to use the provided manifest from the vendor. I know that's not super helpful, but see if even the manifest works on a few people.
Divide and conquer! Always the best way to work the problem :)
That error smells more like the Exchange/AppSource write path choking than anything tenant-side, especially if RBAC and licensing already check out. I would try deploying one boring known-good add-in from AppSource and also test the centralized deployment PowerShell path; if both fail, it is a Microsoft backend/catalog issue, not Anthropic specifically. If only Claude fails while another AppSource add-in works, that points to the listing or how its metadata is being handed off to Exchange. The vendor manifest is a fine workaround, but it does not prove the store path is healthy, so I would open a Microsoft ticket and hand them the correlation IDs.
On the one hand I agree with your take. On the other, this guy likely got the order from corporate and doesn't have an option.
Did you try do this through powershell? https://learn.microsoft.com/en-us/microsoft-365/enterprise/use-the-centralized-deployment-powershell-cmdlets-to-manage-add-ins?view=o365-worldwide
We have it on E5, P2 but I wouldn't see standard vs premium vs E5 tenants as different.
Oh no! Anyway..