ANAVEM
Reference
Languagefr
How to Migrate Exchange to Microsoft 365 Using Minimal Hybrid Configuration

How to Migrate Exchange to Microsoft 365 Using Minimal Hybrid Configuration

Migrate your on-premises Exchange Server to Microsoft 365 using minimal hybrid setup. Complete mailbox migration in weeks without ongoing directory sync or complex infrastructure.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
March 17, 2026 15 min 6
mediumexchange 10 steps 15 min

Why Choose Minimal Hybrid Configuration for Exchange Migration?

Migrating from on-premises Exchange to Microsoft 365 doesn't always require a complex, ongoing hybrid deployment. The Minimal Hybrid Configuration (also called Express Migration) offers a streamlined approach perfect for organizations planning to complete their migration within weeks rather than maintaining long-term coexistence.

Unlike full hybrid deployments that maintain ongoing integration between on-premises and cloud environments, minimal hybrid provides just enough connectivity to facilitate mailbox migration. You get one-time directory synchronization, basic mail routing during migration, and the ability to move mailboxes without disrupting user access. Once migration completes, you can decommission your on-premises Exchange infrastructure entirely.

What Makes Minimal Hybrid Different from Full Hybrid?

The key distinction lies in scope and duration. Full hybrid deployments include features like cross-premises Free/Busy calendar sharing, ActiveSync redirection, and secured mail flow between environments. These features require ongoing maintenance and infrastructure.

Minimal hybrid strips away these advanced features, focusing solely on migration capabilities. You won't get seamless calendar sharing during migration, but you also won't need to maintain complex connectors and certificates long-term. This approach significantly reduces complexity while providing a clean migration path to the cloud.

Related: How to Delegate Exchange Distribution List Management to

Related: How to Configure Outlook Auto-Login using Microsoft Intune

Related: Configure OneDrive Auto Sign-in Using Microsoft Intune

What Are the Technical Requirements for This Migration?

This migration method supports Exchange Server 2010, 2013, and 2016 environments. You'll need a verified Microsoft 365 tenant, domain ownership confirmation, and a domain-joined computer to run the migration tools. The process uses Microsoft's Exchange Hybrid Configuration Wizard and Microsoft Entra Connect for one-time directory synchronization.

The entire process typically completes within 2-4 weeks for most organizations, making it ideal for businesses ready to fully embrace cloud email without maintaining hybrid infrastructure indefinitely.

Implementation Guide

Full Procedure

01

Verify Domain Ownership in Microsoft 365

Before starting the migration, you need to verify that you own the domain in Microsoft 365. This establishes trust between your on-premises environment and the cloud.

Navigate to the Microsoft 365 Admin Center at admin.microsoft.com and sign in with your Global Administrator account. Go to Settings > Domains and click Add domain.

Enter your on-premises domain name (e.g., contoso.com) and follow the verification wizard. You'll need to add a TXT record to your DNS provider:

TXT record: MS=ms12345678
Host: @ (or leave blank)
TTL: 3600

After adding the DNS record, return to the Admin Center and click Verify. The verification process typically takes 5-15 minutes.

Pro tip: Don't configure MX records yet. We'll update mail routing after the migration is complete to avoid mail flow disruption.

Verification: The domain status should show as "Verified" in the Domains list. You'll see a green checkmark next to your domain name.

02

Download and Launch Exchange Hybrid Configuration Wizard

The Exchange Hybrid Configuration Wizard (HCW) is the primary tool for setting up minimal hybrid configuration. Microsoft updates this tool regularly, so always download the latest version.

In the Microsoft 365 Admin Center, navigate to Setup > Data migration. Select Exchange as your migration source, then click Download application to get the latest HCW.

Run the downloaded installer on your domain-joined computer. The installer will download and launch the wizard automatically. Make sure you're running as an administrator:

Right-click on HybridConfigurationWizard.exe
Select "Run as administrator"

On the welcome screen, click Next to begin the configuration process.

Warning: If you've previously configured a full hybrid deployment, the minimal hybrid option won't be available. You'll need to use the full hybrid migration path instead.

Verification: The HCW welcome screen should display without errors, and you should see options for hybrid configuration types in the next steps.

03

Configure On-Premises Exchange Connection

The wizard needs to connect to your on-premises Exchange server to prepare it for migration. It will automatically detect your Exchange organization settings.

On the On-premises Exchange Organization page, the wizard will auto-populate your Exchange server details. It connects to the latest version Exchange server in your organization by default. Review the detected settings:

  • Exchange Server: Should show your CAS server
  • Organization Name: Your Exchange organization identifier
  • Version: Should display Exchange 2010, 2013, or 2016

If the auto-detection fails, manually specify your Exchange server FQDN:

Server FQDN: exchange01.contoso.local
Port: 443 (default for HTTPS)

Click Next to proceed to credential configuration.

Pro tip: Ensure your Exchange server has the latest cumulative updates installed before migration. This prevents compatibility issues during the hybrid setup.

Verification: The connection test should complete successfully, showing your Exchange organization details without errors.

04

Provide Authentication Credentials

The wizard requires administrative credentials for both your on-premises Exchange and Microsoft 365 environments to establish the hybrid connection.

On the Credentials page, configure the following:

On-premises credentials: The wizard will use your current Windows credentials by default. Ensure your account has:

  • Exchange Organization Management permissions
  • Local administrator rights on the Exchange server
  • Domain administrator privileges

Exchange Online credentials: Enter your Microsoft 365 Global Administrator credentials:

Username: admin@contoso.onmicrosoft.com
Password: [Your secure password]

Click Next to validate both credential sets. The wizard will test connectivity to both environments.

Warning: Don't use a service account that might have password expiration policies. Use a dedicated admin account with a strong, non-expiring password for the migration process.

Verification: Both credential validations should show green checkmarks. Any red X indicates permission or connectivity issues that need resolution.

05

Select Minimal Hybrid Configuration

This step configures the type of hybrid deployment. For quick migrations without ongoing integration, minimal hybrid is the optimal choice.

On the Hybrid Features page, select Minimal Hybrid Configuration. This option provides:

  • One-time directory synchronization
  • Mailbox migration capabilities
  • Basic mail routing during migration
  • No ongoing hybrid features (Free/Busy, etc.)

The wizard will display what features are included and excluded:

Included:
- Mailbox migration
- Directory sync (one-time)
- Basic mail routing

Excluded:
- Cross-premises Free/Busy
- ActiveSync redirection
- Secured mail flow
- Ongoing directory synchronization

Click Next to proceed to the configuration summary.

Pro tip: Minimal hybrid is perfect for organizations planning to complete their migration within a few weeks and don't need ongoing integration between on-premises and cloud environments.

Verification: The feature selection should clearly show "Minimal Hybrid Configuration" as selected, with appropriate feature inclusions/exclusions listed.

06

Execute Hybrid Configuration Update

This step applies the hybrid configuration to your on-premises Exchange server, preparing it for mailbox migration to Microsoft 365.

On the Ready for Update page, review the configuration summary. The wizard will show all changes it will make to your environment:

  • Create hybrid management objects
  • Configure mail routing connectors
  • Set up migration endpoints
  • Prepare mailboxes for migration

Click Update to begin the configuration process. The wizard will display real-time progress:

Configuring hybrid deployment...
✓ Creating organization relationship
✓ Configuring send connectors
✓ Setting up migration endpoints
✓ Validating configuration

This process typically takes 10-20 minutes depending on your Exchange environment size and network connectivity.

Warning: Don't close the wizard or interrupt the process once it starts. Interruption can leave your environment in an inconsistent state requiring manual cleanup.

Verification: The wizard should complete with "Configuration Successful" message. All configuration steps should show green checkmarks without errors.

07

Perform One-Time Directory Synchronization

After hybrid configuration, you need to sync your on-premises users to Microsoft 365. This is a one-time sync that won't continue running after migration.

On the User Provisioning page, select Synchronize my users and passwords one time. Click Download to get Microsoft Entra Connect (formerly Azure AD Connect).

Run the Entra Connect installer and select Express Settings:

# Express Settings Configuration
Directory to synchronize: [Auto-detected AD domain]
Azure AD sign-in: admin@contoso.onmicrosoft.com
Enterprise Admin: [Your domain admin account]
Password synchronization: Enabled

The sync process will start automatically. Monitor the progress in the Entra Connect interface:

Synchronization Status:
- Users discovered: 150
- Users synchronized: 150
- Errors: 0
- Sync duration: 5 minutes

After completion, directory sync automatically turns off, and users appear in the Microsoft 365 Admin Center.

Pro tip: The initial sync can take several minutes for large directories. Users will appear in Microsoft 365 with "Unlicensed" status until you assign licenses in the next step.

Verification: Check Microsoft 365 Admin Center > Users > Active users. Your on-premises users should appear with cloud UPNs matching their on-premises addresses.

08

Assign Microsoft 365 Licenses to Users

Before migrating mailboxes, users need appropriate Microsoft 365 licenses. You can assign licenses individually or in bulk depending on your organization size.

In the Microsoft 365 Admin Center, go to Users > Active users. Select users who need Exchange Online licenses.

For bulk license assignment:

  1. Select multiple users using checkboxes
  2. Click Manage product licenses
  3. Choose Assign licenses
  4. Select appropriate license (e.g., Microsoft 365 Business Standard)
  5. Configure Exchange Online settings

For PowerShell bulk assignment:

# Connect to Microsoft 365
Connect-MsolService

# Assign licenses to all unlicensed users
Get-MsolUser -UnlicensedUsersOnly | Set-MsolUserLicense -AddLicenses "contoso:EXCHANGESTANDARD"

# Verify license assignment
Get-MsolUser | Select DisplayName,Licenses
Pro tip: Assign licenses in batches of 50-100 users to avoid throttling. Monitor the process and ensure all users receive their licenses before starting mailbox migration.

Verification: Users should show "Licensed" status in the Admin Center. Run Get-MsolUser -UserPrincipalName user@contoso.com | Select Licenses to verify specific user licensing.

09

Migrate Mailboxes to Exchange Online

With users licensed and hybrid configured, you can now migrate mailboxes from on-premises Exchange to Exchange Online. Plan your migration in batches to minimize impact.

In the Microsoft 365 Admin Center, navigate to the Data migration page. Your synchronized users should appear in the migration list.

Create migration batches:

  1. Select users for migration (start with 10-20 for testing)
  2. Click Start migration
  3. Choose migration options:
Migration settings:
- Batch name: Pilot_Batch_1
- Migration type: Remote move
- Target delivery domain: contoso.mail.onmicrosoft.com
- Bad item limit: 50
- Large item limit: 10

Monitor migration progress in real-time. Each mailbox shows status:

  • Queued: Waiting to start
  • In Progress: Data copying
  • Completed: Successfully migrated
  • Failed: Requires attention
Warning: Don't migrate all users simultaneously. Start with pilot groups and gradually increase batch sizes based on network capacity and migration performance.

Verification: Test migrated users can access their mailboxes via Outlook Web App at outlook.office365.com. Verify mail, calendar, and contacts are accessible.

10

Update DNS Records and Complete Migration

After successfully migrating all mailboxes, update your DNS records to route mail directly to Microsoft 365 and complete the migration process.

In the Microsoft 365 Admin Center, go to Settings > Domains > select your domain > DNS records. Update the following records at your DNS provider:

MX Record (highest priority):

Priority: 0
Host: @ (or leave blank)
Points to: contoso-com.mail.protection.outlook.com
TTL: 3600

Additional required records:

# Autodiscover CNAME
Host: autodiscover
Points to: autodiscover.outlook.com
TTL: 3600

# SPF TXT Record
Host: @
Value: v=spf1 include:spf.protection.outlook.com -all
TTL: 3600

After DNS propagation (typically 1-4 hours), test mail flow by sending external emails to migrated users.

Decommission on-premises Exchange:

  1. Verify all mailboxes migrated successfully
  2. Confirm mail routing to Microsoft 365
  3. Remove Exchange server from load balancer
  4. Uninstall Exchange Server software
Pro tip: Keep your on-premises Exchange server running for 1-2 weeks after DNS changes to ensure no mail delivery issues before final decommissioning.

Verification: Send test emails from external sources to migrated users. Check that mail delivers to Exchange Online mailboxes, not on-premises. Use nslookup -type=mx yourdomain.com to verify MX record changes.

Frequently Asked Questions

Can I use minimal hybrid configuration with Exchange Server 2019 or newer?+
Current Microsoft documentation supports minimal hybrid configuration for Exchange 2010, 2013, and 2016 only. For Exchange 2019 and newer versions, you may need to use full hybrid deployment or alternative migration methods. Microsoft hasn't confirmed minimal hybrid support for newer Exchange versions as of 2026.
What happens to user Outlook profiles after minimal hybrid migration?+
User Outlook profiles may require reconfiguration after migration since minimal hybrid doesn't provide automatic redirection features. Users typically need to create new Outlook profiles pointing to Exchange Online, or you can use tools like the Microsoft Support and Recovery Assistant to help with profile updates.
How long does the minimal hybrid migration process take to complete?+
The entire migration typically takes 2-4 weeks for most organizations. Initial hybrid setup takes 1-2 hours, directory sync completes within minutes to hours depending on user count, and mailbox migration speed depends on data volume and network bandwidth. Plan for 1-5 GB per hour per mailbox migration.
Can I migrate mailboxes in batches during minimal hybrid configuration?+
Yes, batch migration is recommended and supported. Start with pilot groups of 10-20 users to test the process, then gradually increase batch sizes based on network capacity and performance. You can monitor migration progress in the Microsoft 365 Admin Center and pause or resume batches as needed.
What happens if I already have a full hybrid deployment configured?+
If you've previously configured a full hybrid deployment, the Exchange Hybrid Configuration Wizard won't offer the minimal hybrid option. You'll need to either use the existing full hybrid infrastructure for migration or remove the full hybrid configuration first, though this may disrupt existing services and isn't recommended.
Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...