IT Support Portal

ServiceNow-style demo portal

Affiliate Disclosure

Some recommendations may include affiliate links. If you purchase through these links, the site may earn a commission at no additional cost to you. Recommendations are still selected for fit, safety, and support relevance.

Office Add-in Disabled After Crash or Slow Startup

Estimated time

10-20 min

Severity: MediumAdmin RequiredEnv: WindowsMicrosoftMicrosoft Office

Author & Verification

Tamem J

IT Solutions Engineer

Last verified: March 3, 2026

Runbooks and troubleshooting guides are reviewed for enterprise-safe usage and avoid security bypass patterns.

Tested on Windows 11 23H2Tested on Windows 10 22H2

Trust Signals

No ratings yet

0 total helpfulness votes

  • Enterprise Microsoft 365 Administration
  • Endpoint Management (Intune, Jamf, Kandji)
  • Identity & Access (Entra ID, Okta)

Symptoms of there was a problem reaching this app azure enterprise app

  • An Office add-in is missing or shown as disabled after app restart.
  • Office reports add-in performance impact and disables it automatically.
  • Business workflow relying on the add-in is interrupted.

Likely Causes of there was a problem reaching this app azure enterprise app

  • Office startup resiliency disabled the add-in after crash/timeout.
  • Add-in version conflict after Office update.
  • Policy blocks loading unmanaged or deprecated add-in versions.

Interactive Decision Tree

ITIL-style triage path powered by state machine logic.

How to Fix: there was a problem reaching this app azure enterprise app

Accordion runbook sections

  1. 1

    Confirm scope, user impact, and reproduction

    Info
    v

    Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.

  2. 2

    Validate prerequisites and application/session state

    Info
    v

    Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.

  3. 3

    Run safe diagnostics from the Commands section

    Command
    v

    Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.

  4. 4

    Apply safe remediation steps

    Info
    v
    • Confirm the add-in is approved and required for the user/business process.
    • Review Office add-in state (Disabled Items / COM Add-ins / Web add-ins depending on product).
    • Restart the Office app and test with a clean launch before re-enabling.
    • Coordinate with desktop engineering for packaged add-in reinstall/repair if needed.
  5. 5

    Escalate when access, policy, or security controls are involved

    WarningAdmin required
    v
    • The add-in fails repeatedly across multiple devices after re-enable.
    • Security/governance policy blocks the add-in version in use.
    • Registry or Office repair changes are required on managed devices.

Commands

Copyable diagnostic or remediation commands (1 snippet).

Windows process/service quick check

PowerShell

Get-Process | Where-Object { $_.ProcessName -match "Microsoft Office" } | Select-Object ProcessName, Id, CPU

When to Contact IT / Security

  • The add-in fails repeatedly across multiple devices after re-enable.
  • Security/governance policy blocks the add-in version in use.
  • Registry or Office repair changes are required on managed devices.

Recommended Partners for This Topic

Selected from your affiliate registry based on this article's category, product family, and tags.

Disclosure: Active partner links may generate commission with no additional user cost.

Was this helpful?

Your response is stored locally in this browser for demo analytics.