Exchange Connection Problems

How to Manage Exchange Online Users in a Hybrid Environment

Steve KSteve K Oct 29, 2026 868 views

Question details

Users created in on-premises Active Directory and synced to Microsoft 365 do not appear in the on-premises Exchange Control Panel.

How to Manage Exchange Online Users in a Hybrid Environment
Product
Microsoft Exchange
Device & OS
not provided
Scenario
Managing user mailboxes in a hybrid Exchange environment where users were created on-premises but never had an on-premises mailbox.
Observed behavior
Required Exchange attributes are missing, causing active Exchange Online users to be invisible in the on-premises Exchange Control Panel.
Before you start

Ensure you have administrative access to both Exchange Online PowerShell and the on-premises Exchange Management Shell, and that Azure AD Connect synchronization is functioning properly.

Solution 1Recommended

Enable Remote Mailbox and Sync ExchangeGuid

Use PowerShell to retrieve the ExchangeGuid from Exchange Online and apply it to the on-premises remote mailbox to sync attributes correctly.

When users are created in on-premises AD and synced to Microsoft 365 without an on-premises mailbox, they lack necessary Exchange attributes. Enabling a remote mailbox and matching the ExchangeGuid resolves this visibility issue.

1
Retrieve ExchangeGuid

Connect to Exchange Online PowerShell and run the command 'Get-Mailbox -Identity <UserPrincipalName> | Format-List ExchangeGuid' to get the user's GUID.

2
Enable Remote Mailbox

Open the on-premises Exchange Management Shell and run 'Enable-RemoteMailbox -Identity <UserPrincipalName> -RemoteRoutingAddress <UserAlias>@<Tenant>.mail.onmicrosoft.com'.

3
Apply ExchangeGuid

In the on-premises shell, run 'Set-RemoteMailbox -Identity <UserPrincipalName> -ExchangeGuid <GuidFromStep1>' to match the online mailbox.

4
Force Directory Sync

Run Azure AD synchronization using 'Start-ADSyncSyncCycle -PolicyType Delta' to push the updated attributes to Microsoft 365.

5
Verify User Visibility

Log in to the on-premises Exchange Control Panel (ECP) and verify that the user now appears correctly as an Office 365 mailbox.

Enable Remote Mailbox and Sync ExchangeGuid
Synchronization Complete: The user should now be fully manageable from the on-premises Exchange Control Panel.
Free Microsoft Office alternative

Looking for a Lightweight Office Suite for Your Organization?

While managing complex Exchange hybrid environments requires Microsoft admin tools, your users' daily document needs might not require expensive Microsoft 365 licenses. WPS Office provides a free, lightweight, and highly compatible alternative for word processing, spreadsheets, and presentations.

  1. 1. Download the Installer: Visit the official WPS website and download the free installation package.
  2. 2. Install WPS Office: Run the installer and follow the on-screen instructions to set up the suite on your device.
  3. 3. Open and Edit Documents: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office files.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight installation that runs smoothly on older or lower-spec hardware.Familiar tabbed user interface minimizes training time for employees.Cost-effective solution for users who only need core document editing features.
microsoft office alternative - wps office

Frequently Asked Questions

Why are my synced AD users missing from the on-premises Exchange Control Panel?

If users were created in on-premises Active Directory and synced to Microsoft 365 without ever having an on-premises Exchange mailbox, they lack the required Exchange attributes to be visible in the on-premises ECP.

What is a remote routing address in Exchange?

A remote routing address (usually formatted as alias@tenant.mail.onmicrosoft.com) is used by the on-premises Exchange server to correctly route emails to a user's mailbox hosted in Exchange Online.

Do I need to match the ExchangeGuid for every synced user?

Yes, if the user has an active mailbox in Exchange Online but was originally created on-premises, matching the ExchangeGuid ensures that the on-premises environment correctly identifies and links to the cloud mailbox without generating conflicts.

How long does it take for Azure AD sync to reflect the attribute changes?

A delta sync typically takes about 30 minutes to run automatically. However, you can force a sync immediately using the Start-ADSyncSyncCycle PowerShell command on your AD Connect server.