Purpose
Use this when Outlook add-in installation appears to be blocked broadly, but testing shows different behavior between Classic Outlook and New Outlook.
Diagnostic pattern
- Classic Outlook can open and browse the add-in catalog, but selecting Add fails with
Sorry, we can't complete this operation right now. Please try again later. - The same failure reproduces across more than one workstation and more than one user.
- New Outlook can still acquire an app from Manage your apps / Get more apps, and the app is usable there.
- An app installed successfully in New Outlook may still be absent from Classic Outlook.
What this proves, and what it does not
A successful installation in New Outlook is strong evidence against a simple organization-wide rule that blocks all Outlook app acquisition. The account can acquire at least that app through the New Outlook app experience.
It does not prove that Classic Outlook must be able to consume the same app. New Outlook and Classic Outlook do not expose the integration experience identically. An app under New Outlook's Manage your apps does not guarantee Classic Outlook compatibility, discovery, or synchronization.
The generic Classic Outlook error is also not enough, by itself, to conclude that an administrator policy is blocking add-ins.
Diagnostic procedure
- In Classic Outlook, verify whether the failure occurs while browsing the catalog or only when selecting Add. Being able to browse but not install narrows the failure to acquisition or registration, not basic catalog reachability.
- Reproduce with a second user and a second workstation. If the same behavior follows multiple users and hosts, deprioritize local profile corruption or one-machine configuration issues.
- In New Outlook, open Manage your apps and use Get more apps to install a known official app. Confirm that it appears in the installed-app list and can be used.
- Return to Classic Outlook and check whether the same app appears there. Do not assume that installing it through New Outlook will automatically make it visible in Classic Outlook.
- Verify the actual Classic Outlook build from File > Office Account > About Outlook. Do not use the New Outlook
1.xclient version or WebView2 version as the Classic Outlook version. - If New Outlook acquisition works but Classic Outlook consistently fails across users and machines, focus next on Classic Outlook-specific add-in handling, policy, compatibility, or synchronization. Do not treat the issue as a blanket Microsoft 365 app-store block.
Version-identification catch
New Outlook reports version information in a format such as 1.2026.x together with a WebView2 version. That is not the Classic Outlook build.
Classic Outlook reports a Microsoft 365 Apps build from About Outlook, for example Version 2605 Build 16.0.20026.20168 64-bit.
A failure reproduced on a current Classic Outlook build should not be dismissed as an obsolete-client issue without additional evidence.
Useful control test
An official marketplace app can be used as a control. If it installs, appears under New Outlook's Manage your apps, and works there while Classic Outlook still cannot install or discover it, the useful conclusion is that the two Outlook clients are taking different integration paths.
Catches / gotchas
- New Outlook primarily presents these integrations as Apps. Classic Outlook commonly presents them as Add-ins. Searching only for an Add-ins menu in New Outlook can be misleading.
- Do not interpret a generic Classic Outlook installation dialog as proof of tenant policy without a comparative test.
- Do not assume successful New Outlook acquisition guarantees Classic Outlook support.
- Do not use New Outlook's WebView2 or client version when documenting the Classic Outlook build.
Current limitation
This pattern narrows the fault domain. It does not establish a final root cause for Classic Outlook installation failure. Do not document a specific policy, registry value, Exchange setting, or compatibility limitation as the cause until further investigation proves it.
Key lesson
If Classic Outlook cannot add catalog items but New Outlook can acquire and use apps, treat that as two different client paths rather than a tenant-wide app-store block. Confirm it on more than one user and host, and record the Classic Outlook build from About Outlook.