Share via

Microsoft Office 365 Version 26.03.19725.20152 breaks Exchange SE add-ins

Robert Loglisci 5 Reputation points
2026-03-25T16:48:29.7133333+00:00

We have confirmed that Microsoft Office 365 version 26.03.19725.20152 is breaking the Exchange on-prem add-ins, specifically Phish Alert and Zoom button in Outlook Classic.

Reverting Office 365 to 26.02.16.0.19725.20152 and then updating to 26.02.19725.20190 is working as intended.

We can reproduce if Microsoft is monitoring this thread.

Outlook | Windows | Classic Outlook for Windows | For business
0 comments

Answer recommended by moderator

Robert Loglisci 5 Reputation points
2026-04-01T20:41:30.1233333+00:00

Version 2603 (Build 19822.20142), released on 3/31/2026 does not fix the Exchange on-premesis add-in issue with Microsoft Outlook.

We have been rolling workstations back to Version 2602 (Build 19725.20126) by updating the registry keys at HKEY Local Machine -> Software -> Microsoft -> Office -> ClickToRun -> Configuration.

Add key UpdateToVersion and updating the keys for ClientVersionToReport and VersionToReport to string 16.0.1.19725.20126.

Once the registry keys are updated, without a reboot, you can run the Office Update and the version will revert.

Be sure to turn off Automatic Updates in Office 365 when completed.

Was this answer helpful?

0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dora-T 13,745 Reputation points Microsoft External Staff Moderator
    2026-03-26T00:14:51.23+00:00

    Hi Robert Loglisci

    Thank you for reaching out to the Microsoft Q&A Forum and for sharing your findings.

    I really appreciate the time and effort you’ve taken to test and identify the behavior across different Office versions. 

    I’ve checked available information, and at the moment I haven’t found any official confirmation or known issue matching what you described. However, based on your testing, this may be related to that specific Office version. 

    As a temporary workaround, you may continue using the stable version (such as 26.02) and try updating again once a newer build becomes available. 

    May I know if you have an active Microsoft 365 subscription and access to the Admin Center? If so, you can raise a support ticket directly from there with the Microsoft Support team so the issue can be looked into further.

    For further instructions, you can follow this guide: Get support - Microsoft 365 admin | Microsoft Learn.      

    Please note that this is a public peer-to-peer community forum. While moderators and community members can share guidance and experiences, we do not have access to internal systems and are not able to directly escalate issues to the product team.

    Thank you for your understanding. 

    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.

    Was this answer helpful?

    1 person found this answer helpful.

  2. AI answer

    2026-03-25T16:48:46.2633333+00:00

    The described behavior matches a class of known Outlook/Office add-in regressions introduced by specific Microsoft 365 Apps builds, where changes in authentication or add-in plumbing temporarily break Exchange-based add-ins (including third‑party solutions like Zoom and security/phishing add-ins).

    From the available information, there is no documented, customer-side permanent fix for a specific build such as 26.03.19725.20152 beyond:

    1. Reverting to a prior working build.
    2. Updating to a newer build that contains a fix or mitigation.

    The pattern documented for other add-in regressions is:

    1. A specific build introduces an authentication or add-in loading regression (often related to Exchange Web Services (EWS) or REST changes) that causes add-ins to fail to load, appear missing, or misbehave.
    2. Microsoft rolls out a mitigation or fix in a subsequent build; customers either:
      • Wait for the fixed build to reach their update channel, or
      • Manually revert to a prior known-good build and then update to a fixed build.

    For example:

    • Office add-ins have intermittently failed to load or deploy due to Exchange authentication changes, with Microsoft applying targeted mitigations and advising customers to contact Support if issues persist.
    • Outlook add-in regressions (including event-based and signature add-ins) have been fixed by specific later builds or configuration rollbacks, sometimes requiring Outlook restarts to pick up corrected settings.
    • Excel add-in regressions (RichApi.Error 0x8002802B) were explicitly resolved by updating to a specific or later build.

    Given that reverting from 26.03.19725.20152 to 26.02.16.0.19725.20152 and then updating to 26.02.19725.20190 restores functionality in this environment, the actionable guidance consistent with documented patterns is:

    1. Keep affected clients on a known-good build (in this case, 26.02.19725.20190) until Microsoft publishes a fix in a later 26.03 or newer build.
    2. Monitor the Microsoft 365 Apps update history and Office/Outlook add-ins known issues pages for a note that a specific build resolves an add-in regression affecting Exchange on-prem add-ins.
    3. If the issue persists or if remaining on 26.02.19725.20190 is not acceptable, open a support ticket with Microsoft, referencing:
      • The affected build (26.03.19725.20152),
      • The working build (26.02.19725.20190),
      • The impacted add-ins (Phish Alert, Zoom),
      • That this is an Exchange on-premises add-in scenario.

    This aligns with existing guidance for similar add-in regressions, where Microsoft confirms the issue, rolls out a fix, and customers either revert to a prior build or update to the fixed build once available.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.