AI Disclaimer I love exploring new technology, and that includes using AI to help with research and editing! My digital “team” includes tools like Google Gemini, Notebook LM, Microsoft Copilot, Perplexity.ai, Claude.ai, and others as needed. They help me gather insights and polish content—so you get the best, most up-to-date information possible.

Standardizing on New Outlook for Windows (and Removing Outlook Classic)

As organizations modernize their Windows 11 environments, Outlook often becomes a source of confusion. Much of that confusion comes from assuming Outlook is part of Windows itself. In reality, Outlook behavior on Windows 11 depends heavily on what is installed after the operating system—particularly Microsoft 365 Apps—and when those changes occur in the device lifecycle.

This post explains what Windows 11 includes, how Outlook Classic typically gets installed, and how to safely standardize on New Outlook for Windows. It also covers an important operational requirement: removal actions should occur only after Intune enrollment and/or Microsoft 365 Apps activation.

Windows 11 does not come with Outlook Classic by default

The latest versions of Windows 11, including current releases from 2025–2026, do not include Outlook Classic by default.

Here is the clear breakdown.

What does come with Windows 11

• New Outlook for Windows (the web‑based “new Outlook”) is preinstalled
• It replaces the legacy Mail & Calendar apps
• It is free to use and integrated with Outlook on the web, but feature‑limited compared to Outlook Classic

What does NOT come with Windows 11

• Outlook Classic (the full desktop Win32 client) is not included by default

This distinction is important. Installing or upgrading to Windows 11 alone does not install Outlook Classic. When Outlook Classic appears on a Windows 11 system, it is almost always introduced later through Microsoft 365 Apps or an Office deployment.

How Outlook Classic typically gets installed

Outlook Classic is commonly installed as part of Microsoft 365 Apps when Outlook is included in the app configuration. This means many organizations unintentionally end up with two Outlook experiences side by side:

• New Outlook for Windows from the OS or Microsoft Store
• Outlook Classic from Microsoft 365 Apps

Without intentional governance, users may switch between them, reinstall Classic, or encounter support inconsistencies.

Why some organizations standardize on New Outlook only

Organizations choose a New Outlook‑only posture for several reasons:

• Reduced client complexity and support overhead
• Alignment with Microsoft’s direction for Windows inbox mail experiences
• Avoidance of legacy add‑ins and local data dependencies
• Consistent experience across managed and unmanaged devices

Achieving this outcome requires proper sequencing. Removing Outlook Classic too early can disrupt provisioning and licensing workflows.

Timing requirement: after Intune enrollment and/or Microsoft 365 Apps activation

Outlook Classic should not be removed during early provisioning stages such as:

• Windows Autopilot pre‑provisioning
• Initial Intune device enrollment
• Before Microsoft 365 Apps has completed user activation

Removal should occur only after at least one of the following conditions is met:

• The device is fully enrolled in Intune and baseline apps and policies have applied
• The user has signed in and successfully activated Microsoft 365 Apps (for example, Word or Excel launches without activation prompts)

Removing Outlook Classic before these checkpoints can result in Office repair loops, failed app detection, or incomplete activation states.

Recommended removal approach

The preferred approach is not to uninstall Microsoft 365 Apps entirely, but to remove only Outlook Classic while leaving the rest of the Office apps intact. This preserves licensing, update channels, and application health while enforcing a New Outlook‑only experience.

This approach works well when executed as a post‑enrollment or post‑activation task in Intune.

PowerShell example: remove Outlook Classic after enrollment

The following example demonstrates how Outlook Classic can be removed using the Microsoft Office Deployment Tool configuration model. This script should be executed after Intune enrollment and Microsoft 365 Apps activation.

Example steps

1. Download the Office Deployment Tool
2. Create a configuration file that excludes Outlook
3. Run the modification command

Sample configuration file (remove‑outlook.xml)

<Configuration>

  <Remove>

    <Product ID="O365ProPlusRetail">

      <Language ID="en-us" />

      <ExcludeApp ID="Outlook" />

    </Product>

  </Remove>

  <Display Level="None" AcceptEULA="TRUE" />

</Configuration>

PowerShell execution example

ODTPath = "C:\ODT"
Start-Process -FilePath "$ODTPath\setup.exe" `
  -ArgumentList "/configure remove-outlook.xml" `
  -Wait -NoNewWindow$ODTPath = "C:\ODT"
Start-Process -FilePath "$ODTPath\setup.exe" `
  -ArgumentList "/configure remove-outlook.xml" `
  -Wait -NoNewWindow

This approach:

• Removes Outlook Classic only
• Preserves Word, Excel, PowerPoint, and licensing state
• Aligns with enterprise deployment best practices when run post‑enrollment

Ensuring users remain on New Outlook

After removing Outlook Classic, organizations should ensure that New Outlook for Windows is:

• Set as the default email application
• Not overridden by user‑initiated Office reinstalls
• Reinforced through Intune policy and app governance where appropriate

This prevents regression and ensures consistency across all managed devices.

Recommended end‑state

A clean, supportable end‑state for New Outlook standardization looks like this:

• Windows 11 deployed and fully updated
• Device enrolled in Intune
• Microsoft 365 Apps installed and activated
• Outlook Classic removed after activation
• New Outlook enforced as the default mail experience

Final takeaway

Windows 11 does not include Outlook Classic by default. Outlook Classic typically appears only when Microsoft 365 Apps is installed with Outlook selected. Because of this, Outlook Classic should be treated as a managed application component, not an OS feature.

If your goal is New Outlook only, the strategy is straightforward:

• Let the device enroll
• Let Microsoft 365 Apps activate
• Remove Outlook Classic afterward in a controlled, supported way

If you want next steps, I can also:

• Add an Intune remediation script version
• Provide detection logic for Outlook Classic
• Convert this into a Word or Markdown‑ready publishable version
• Tailor it for customer‑facing or internal IT documentation

Just tell me how you want to use it.

References

• Install or reinstall classic Outlook on a Windows PC
• Getting started with the new Outlook for Windows – Microsoft Support
  Run new Outlook and classic Outlook side-by-side
• Windows release health | Microsoft Learn
• Overview of the Office Deployment Tool – Microsoft 365 Apps | Microsoft Learn