Share via

Issues with new outlook

David Burland 5 Reputation points
2026-03-09T04:03:27.58+00:00

I’ve attempted to transition to the new Outlook, but several missing or reduced features are creating real barriers to daily use. These aren’t edge‑case scenarios — they are core workflows that Classic Outlook supports and that many professionals rely on.

Based on the feature comparison page (Feature comparison between new Outlook and classic Outlook – Microsoft Support), a number of essential capabilities are still unavailable or only partially implemented. The most impactful gaps for me are:

  • Inability to accept meeting invitations in a way that automatically updates my calendar and notifies the organiser. This is a fundamental expectation of any modern email/calendar client, and its absence creates unnecessary manual work and risks missed communication.

No ability to pre‑draft emails and schedule them to send later. Delayed send is a critical tool for managing workload, coordinating across time zones, and maintaining professional communication patterns.

Inability to remove attachments from emails before filing or archiving them. Classic Outlook allows detaching or removing large files to reduce mailbox size while retaining the message. The new Outlook’s lack of this feature makes mailbox management significantly harder.

Limited offline functionality. Classic Outlook’s full offline mode is essential for travel, remote work, and unreliable connectivity. The new Outlook’s reduced caching and dependency on constant internet access is a major regression.

Reduced rules and automation. The simplified rules engine removes the ability to manage complex workflows that Classic Outlook handled easily.

Missing customisation options. The inability to tailor views, panes, and the ribbon reduces efficiency for power users.

Add‑in limitations and weaker support for large mailboxes. Several add‑ins no longer function, and performance degrades noticeably with large archives.

I understand and support the long‑term goal of unifying Outlook across platforms, but the current feature gap makes the new Outlook feel like a step backward rather than an evolution. To make the transition viable, I would strongly encourage Microsoft to prioritise:

Restoring full meeting invitation handling

Reintroducing delayed send

Allowing attachment removal/detachment

Delivering full offline capability

Achieving parity in rules, customisation, and mailbox management

Providing clear timelines for when missing features will be delivered

Until these gaps are addressed, it’s difficult to adopt the new Outlook for daily professional use.

Thank you for continuing to develop the product — I hope this feedback helps shape the roadmap. I’ve attempted to transition to the new Outlook, but several missing or reduced features are creating real barriers to daily use. These aren’t edge‑case scenarios — they are core workflows that Classic Outlook supports and that many professionals rely on.

Based on the feature comparison page (Feature comparison between new Outlook and classic Outlook – Microsoft Support), a number of essential capabilities are still unavailable or only partially implemented. The most impactful gaps for me are:

Inability to accept meeting invitations in a way that automatically updates my calendar and notifies the organiser. This is a fundamental expectation of any modern email/calendar client, and its absence creates unnecessary manual work and risks missed communication.

No ability to pre‑draft emails and schedule them to send later. Delayed send is a critical tool for managing workload, coordinating across time zones, and maintaining professional communication patterns.

Inability to remove attachments from emails before filing or archiving them. Classic Outlook allows detaching or removing large files to reduce mailbox size while retaining the message. The new Outlook’s lack of this feature makes mailbox management significantly harder.

Limited offline functionality. Classic Outlook’s full offline mode is essential for travel, remote work, and unreliable connectivity. The new Outlook’s reduced caching and dependency on constant internet access is a major regression.

Reduced rules and automation. The simplified rules engine removes the ability to manage complex workflows that Classic Outlook handled easily.

Missing customisation options. The inability to tailor views, panes, and the ribbon reduces efficiency for power users.

Add‑in limitations and weaker support for large mailboxes. Several add‑ins no longer function, and performance degrades noticeably with large archives.

I understand and support the long‑term goal of unifying Outlook across platforms, but the current feature gap makes the new Outlook feel like a step backward rather than an evolution. To make the transition viable, I would strongly encourage Microsoft to prioritise:

Restoring full meeting invitation handling

Reintroducing delayed send

Allowing attachment removal/detachment

Delivering full offline capability

Achieving parity in rules, customisation, and mailbox management

Providing clear timelines for when missing features will be delivered

Until these gaps are addressed, it’s difficult to adopt the new Outlook for daily professional use.

Thank you for continuing to develop the product — I hope this feedback helps shape the roadmap.

Outlook | Windows | New Outlook for Windows | For home
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-09T04:03:56.4833333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The described limitations and regressions align with the current state of the new Outlook for Windows compared to Classic Outlook.

    Key points from current documentation and Q&A context:

    1. Architecture and feature gaps are expected at this stage
      The new Outlook for Windows is built on a different, web‑based architecture (WebView2) and is still under active development. Microsoft explicitly positions it as a re‑imagined client with a different extensibility and profile model, and provides a feature comparison matrix to show which capabilities are:
      • Available
      • Partially available
      • Not supported
      • Under investigation
      • Upcoming
      The feature comparison article is the authoritative place to track which classic features are present or missing in the new Outlook and their status.
    2. Mail/automation limitations (including Mail Merge and MAPI‑based workflows)
      Several core workflows that depend on classic Outlook’s MAPI/automation stack are not fully supported in the new Outlook:
      • New Outlook is not MAPI‑compliant in the same way as Classic Outlook. As a result, automation scenarios such as Word Mail Merge to email and “Share to email” from Office apps either do not work or are only partially available.
      • Multiple Q&A threads confirm that:
        • Mail Merge to email works reliably only with Classic Outlook.
        • New Outlook is described as effectively a re‑platformed client that “does not support automation” for these scenarios.
      • Moderator guidance consistently recommends switching back to Classic Outlook when Mail Merge or automated sending from Word/Excel/PowerPoint is required.
      This same architectural shift underlies several of the issues raised: reduced rules/automation, add‑in limitations, and weaker support for complex workflows that depended on COM add‑ins or deep client automation.
    3. Add‑ins: COM add‑ins not supported
      • In the new Outlook for Windows, COM add‑ins are not supported. Only web add‑ins are supported.
      • Classic Outlook’s COM add‑ins could deeply manipulate Outlook but also caused instability; the new model intentionally removes that layer.
      • Any workflows or third‑party tools that rely on COM add‑ins will not function in the new Outlook, which directly contributes to the “add‑in limitations” and some automation gaps described.
    4. Safe mode, profiles, and large‑mailbox behavior
      • The new Outlook uses a single‑profile model and removes the traditional profile picker. This is part of a broader architectural change to simplify configuration and improve stability.
      • Safe mode still exists but is different and more limited; it is intended mainly for troubleshooting with Microsoft Support and excludes PST, S/MIME, offline usage, and web add‑ins.
      • These changes affect how large mailboxes and complex configurations are handled and reduce some of the classic “power user” levers (multiple profiles, PST‑heavy workflows, etc.).
    5. Mail feature status (including Mail Merge)
      The feature comparison matrix explicitly lists Mail merge as:
      • Classic Outlook: Available
      • New Outlook: Partially Available
      This matches the reported behavior where:
      • Word Mail Merge appears to complete, but no messages are sent or appear in Sent Items when using new Outlook.
      • Switching back to Classic Outlook restores expected Mail Merge behavior.
    6. Meeting handling, delayed send, offline, rules, customization
      The provided context does not enumerate each of the specific items raised (meeting invitation handling, delayed send, attachment detachment, full offline mode, advanced rules, deep UI customization) one by one, but it does establish that:
      • New Outlook is still in feature‑parity catch‑up mode relative to Classic Outlook.
      • Some features are “partially available,” “under investigation,” or “upcoming,” and not all classic capabilities are present yet.
      • Users encountering missing or degraded behaviors are explicitly encouraged to:
        • Use Classic Outlook when a required feature is not yet available in new Outlook.
        • Submit feedback from within the app via Help → Give Feedback so it reaches the product team and can influence the roadmap.
    7. Recommended practical approach
      Based on current guidance:
      • For any workflow that depends on:
        • Reliable meeting/calendar behaviors not yet working as expected,
        • Mail Merge or other MAPI/automation scenarios,
        • COM add‑ins,
        • Advanced rules and automation that are not yet matched in new Outlook,
        • Or other missing parity features,
      • The recommended workaround is to continue using Classic Outlook as the primary client until the required features are marked as Available (not just “Partially available” or “Upcoming”) in the feature comparison.
      Feedback on missing capabilities should be submitted directly from new Outlook using Help → Give Feedback, which is fully supported in the new client and called out in the feature comparison under “Help and support.”

    In summary, the issues described are consistent with the documented state of the new Outlook: it is a new architecture with incomplete parity, no COM add‑ins, limited automation/MAPI support, and some features only partially available. The supported path today is to:

    • Use Classic Outlook where these gaps block daily work.
    • Track the official feature comparison and roadmap for updates.
    • Use in‑app feedback to prioritize meeting handling, delayed send, offline capabilities, rules/customization, and mailbox‑management parity.

    References:

    1 person found 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.