Troubleshooting FailedWriteToExchange error

Issue

• IT admins encounter "ResponseResult":"FailedWriteToExchange" errors when attempting to centrally deploy an XML Office add‑in.

Most common causes

• The user (or admin) attempting the deployment does not have the required RBAC permissions to deploy or view:
  • Organizational apps
  • Private catalog apps
• Stale or missing app‑related directory roles for the deploying admin.
• PIM-activated roles are not supported. Deployment should be re-attempted using a standard permanent active role.

Troubleshooting steps

1. Install Centralized Deployment PowerShell cmdlets

2. Run command to list out the exact roles needed:

Get-ManagementRole -Cmdlet Get-App  -CmdletParameters OrganizationApp,PrivateCatalog

3. Compare against current role assignments.

Check whether any of the required roles or permissions are missing for the affected user. Assign any missing roles identified during verification to the affected user or admin account.

Get-ManagementRoleAssignment -RoleAssignee <user> 
| ft Name, Role, AssignmentMethod

4. Check for delegation scenarios

In some cases, roles may be delegated rather than directly assigned, which can lead to unexpected permission gaps during deployment. Ensure the roles are correctly applied (direct vs. delegated) and visible in role assignment checks.

Get-ManagementRoleAssignment -RoleAssignee "Organization Management" -Role "Org Marketplace Apps" -Organization <tenant id> -Delegating $true 
| fl

5. Retry add-in deployment

Once permissions are corrected, retry the add-in deployment from the appropriate admin or user experience. Successful deployment confirms the issue was permission-related.