Exchange classic Hybrid to Modern Hybrid topology upgradation

Nur Hossain 282 Reputation points
2021-03-02T07:33:39.703+00:00

In our exchange hybrid environment, we are using Exchange classic Hybrid topology but now we want to enable Exchange modern Hybrid topology.

Our Exchange Server 2016 CU18 and client is outlook is 2013/2016/2019 and Office 365 Proplus(Click2run).

Is there any risk if we enable Exchange modern Hybrid topology in existing environment.

Thank You
Nur

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,485 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,990 questions
0 comments No comments
{count} votes

Accepted answer
  1. Lucas Liu-MSFT 6,161 Reputation points
    2021-03-03T02:32:59.237+00:00

    Hi @Nur Hossain ,
    According to the Microsoft official document we could know that it is possible to switch to Modern Hybrid (Hybrid Agent) after successfully configuring Classic Hybrid. But we only recommend doing this if you are blocked from migrating to Microsoft 365 or Office 365 after this setup is complete. Because not all hybrid features or experiences are supported with the Hybrid Agent. If you are successfully migrating mailboxes your users are experiencing hybrid features and chose to revert to Modern Hybrid.

    The following are the constraints you need to consider in Exchange Modern Hybrid:

    1. Hybrid Modern Authentication is not supported with the Hybrid Agent. Customers will need to leverage the Classic Exchange Hybrid Topology and publish AutoDiscover, EWS, ActiveSync, MAPI and OAB endpoints for hybrid Modern Authentication to function with various Outlook clients.
    2. For Teams' Calendaring features that require access to on-premises mailboxes, it's recommended that you leverage the full Classic Exchange Hybrid Topology.
    3. Message Tracking and Multi-mailbox search do not traverse the Hybrid Agent. These Hybrid features require the classic connectivity model where Exchange Web Services (EWS) and Autodiscover are published on-premises and are externally available to Microsoft 365 and Office 365.
    4. The Hybrid Agent supports a single migration endpoint with the service default limits. Multiple migration endpoints utilizing your custom endpoint/URL is not supported.
    5. The Hybrid Agent supports a single Exchange organization. Multiple Exchange organizations hybrid is not supported.

    If you have weighed the pros and cons of switching from Classic to Modern and choose to proceed, you could do this by deleting your existing migration batches and migration endpoint and re-running the Hybrid Configuration wizard and selecting Modern Hybrid.
    About Exchange Modern Hybrid requirements and restrictions to be considered you could refer to: Microsoft Hybrid Agent

    In addition, we also need to meet the prerequisites for hybrid deployment: Hybrid deployment prerequisites

    ----------

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


0 additional answers

Sort by: Most helpful