How to Remove Exchange Without Breaking Hybrid Mail Management

  • Post author:
  • Post category:Exchange Online
  • Post last modified:
  • Reading time:7 mins read
  • Post published:

One question I get from my customers is often along the lines of: “We’ve moved everything to Exchange Online, but how do we manage mail users going forward?”. A common problem where my customers teams are only familiar with the EAC interface for mail user management. This concern reflects a common challenge that many organisations face, having completed their migration to Microsoft 365 but remaining compelled to retain legacy infrastructure through necessity rather than choice.

Even never having Exchange Server, going back almost 10 years I remember working on a support desk for a local MSP, still having to manually update users via attribute editor in Active Directory, so the user can be correctly synced to Exchange Online.

Microsoft’s hybrid model deliberately created a dependency on on-premises Exchange servers for managing mail-enabled objects, even after mailboxes migrated to the cloud. However, this dependency doesn’t have to be permanent. Understanding your options for managing mail attributes post-decommission can free your organisation from maintaining unnecessary infrastructure while preserving the ability to efficiently manage mail-enabled objects.

*This is a sponsored post

The Traditional Exchange Management Model

On-premises Exchange Server historically served as the authoritative source for mail attributes within hybrid environments, whereby users are synchronised from on-premises to Microsoft 365. When you created a user account, Exchange stamped essential attributes like proxyAddresses, mail, mailNickname, and msExchRecipientTypeDetails onto the Active Directory user object. These attributes formed the foundation of mail routing, address list membership and recipient recognition within your environment.

Exchange Management Shell (EMS) and Exchange Admin Center (EAC) provided the interface for modifying these essential attributes, but in reality, the work happens at the Active Directory level. Exchange essentially just acted as a convenient wrapper around LDAP operations, ensuring that changes to the mail-related schema remained consistent and valid. Microsoft of course designed this approach for convenience, simplicity and to prevent administrators from accidentally corrupting mail attributes manually.

Exchange Hybrid extended this model into Exchange Online. Entra Connect (then Azure AD Connect) synchronised these attributes to Microsoft Entra, where Exchange Online utilises them to understand recipient types, routing preferences and directory visibility. This sync created (and still does create) a seamless experience where on-premises management decisions reflected shortly after in the cloud environment.

The Post-Decommission Challenge

Removing Exchange Server from your environment doesn’t eliminate the need for mail attribute management where you have your directory synced from Active Directory to Microsoft Entra, especially while Active Directory remains as the source of authority. It simply just removes the tool that made such management straightforward, users still require address list visibility changes and proxy address modifications etc…

Microsoft’s official documentation acknowledges this challenge whilst simultaneously recommending against direct Active Directory attribute manipulation. The Exchange Server Decommissioning Guide warns that improper attribute modification can break mail flow and cause synchronisation errors. However, the documentation provides limited guidance on practical alternatives.

The root problem doesn’t just lie in Exchange’s integration with the Active Directory schema. A core challenge is simply because users are synced from Active Directory, highlighted in the documentation linked above, or image blow.

Exchange Server Attributes reasoning
Exchange Server Attributes reasoning

So this problem leaves administrators in a small predicament… do they keep Exchange server, train their staff to use PowerShell, accept the risk of modifying Active Directory manually, develop a new solution or procure a tool from a vendor?

Available Management Solutions

Several approaches exist for managing mail attributes in ex-Exchange environments, each with their own advantages and limitations. The choice between these solutions depends on your organisation’s technical capabilities, tolerance to risk and long-term strategy, below are a few of them options.

Cloud-only management

This solution offers the most straightforward transition path. In an ideal world, you should accelerate your cloud strategy where possible, removing Entra Connect and ensuring your users are managed solely in the cloud. Similar to Exchange on-premise, when your users are cloud only, relevant properties are either automatically created in the cloud or can be managed from the cloud.

Manual Active Directory manipulation

This solution is arguably the most risky. Asking your IT staff to make direct changes to objects via the Active Directory attributes editor may lead to inconsistencies and errors. It can also be more complex and time-consuming, especially while managing an environment with high turnover or growth.

Third-party management tools

Third-party management tools can provide an easy to use interface for consistent and convenient management of user accounts and mail attributes. Some tools are also free, like the EasyEntra free tier, which allows you to manage any number of hybrid users from Active Directory, while allowing you to easily manage attributes that would otherwise only be manageable from the AD Attributes editor, like:

  • Proxy addresses/mail alias
  • Hide from address list
  • Extension attributes

PowerShell directory manipulation

PowerShell could be the right way to go for organisations that need full control and have a broad and deep level of expertise in PowerShell. You could build scripts that handle all aspects of your user management from start to finish. You could even use AI to write the script for you, but you would be on the hook for maintaining it and your organisation could be stuck if you left.

Implementing Your Chosen Strategy

Personally, I am interested in free third-party options, so for this article, I will walk through my experience with EasyEntra’s solution!

From their website, you can download the trial installer to get going, simply navigate here and click Download trial (don’t worry, once the trial run’s out, the free tier will remain). Now you can install it on any member server, although for ease, I installed it on my one of my domain controllers. I don’t think I need to show you that process, as thankfully it was only a couple of clicks through a standard wizard. 

Now for the configuration… I was initially impressed at how intuitive it was to setup. To my delight, I didn’t even need to refer to the knowledge base! In the Connection Manager window, just click Active Directory Connection Manager and connect via SSO to your Active Directory for convenience. Once this step is complete, your Active Directory should be connected like so: 

Easy Entra AD Setup
Easy Entra AD Setup

Then you can connect your Entra environment. This step isn’t needed if you plan to remain on the free tier, but it is convenient, so worth testing out during the trial period. Now head back into the connection manager, click Entra ID > Add and walk through the wizard until you get to this page:

Easy Entra EntraID setup
Easy Entra EntraID setup

One by one, click the Right arrow and provide consent to Microsoft Graph and sign-in to Exchange Online. As a Microsoft Graph aficionado, I notice the app utilises the built-in Microsoft Graph Command Line Tools application, perfect for simplicity, although I did recommend to the EasyEntra team that support for your own App registration would be a welcome addition for organisations that require more control. Never-the-less, setup is now complete!

Now connected, all I had to do to create a user was select Active Directory and simply right-click my way through to the new user creation wizard (you can also create, synchronised distribution groups, contacts and mail-enabled users). Some convenient options stood out which benefitted me from using the tool, like the adaptive password generator, dynamic search results as you type and advanced LDAP query engine, but my favourite are the following:

  • The ability to update Proxy addresses from a single page and without having to type out the address:
Adding email aliases with Easy Entra
Adding email aliases with Easy Entra
  • The second was the ability to immediately launch an Entra Connect delta sync via the button at the top left of the window:
Launch an Entra Connect sync with Easy Entra
Launch an Entra Connect sync with Easy Entra

Summary

Decommissioning Exchange Server while maintaining hybrid Active Directory environments creates a significant management challenge for organisations. Although mailboxes have migrated to Exchange Online, administrators still need to manage critical mail attributes like proxy addresses and mail nicknames. Microsoft’s hybrid model deliberately created this dependency, leaving organisations in a predicament where they must choose between maintaining unnecessary infrastructure, accepting the risks of manual Active Directory manipulation, developing custom PowerShell solutions, or potentially investing in third-party management tools, although we covered one that is free!

Daniel Bradley

Daniel Bradley is a UK-based technical architect and Microsoft MVP in Security. He specialises in Microsoft Entra, Intune, and Microsoft Graph PowerShell and is the author of Microsoft Graph PowerShell for Administrators. He writes and edits Our Cloud Network using experience gained from working with Microsoft cloud environments.

This Post Has 2 Comments

  1. Phil

    Great article Daniel! Interesting take on the EasyEntra tool and I’m looking forward to trying it out.

Leave a Reply