Error Message

You may encounter the following error during migration or connection attempts:

The request failed. Unable to connect to the remote server.

Problem Description

This error is a network-level failure that occurs before Exchange Online or EWS processes the request. The connection to the remote Exchange service cannot be established at that moment.

This is a temporary issue, not a permanent failure.

Root Cause

The connection request is blocked or interrupted at the network or service level, typically due to Exchange Online service protection mechanisms or temporary service unavailability.

Common Causes

1. Exchange Online Temporary Blocking (Throttling)

Exchange Online may temporarily block incoming connections due to:

  • Network-level connection failures
  • Too many EWS requests in a short time
  • Continuous requests without sufficient delay
  • Mailbox database failover or failback events

2. Server Services Not Active

The required server or background services may be:

  • Stopped
  • Not responding
  • Temporarily unavailable due to restart or maintenance

This can prevent the migration tool from establishing a connection.

Important Notes

  • This error does not indicate mailbox or data corruption.
  • Exchange Online automatically restores connectivity once the temporary condition clears.
  • No permanent configuration changes are required.

Resolution

Check Server Services and Retry

  1. Verify that all required server and migration services are running.
  2. Pause the migration or connection attempt.
  3. Wait a few minutes.
  4. Retry the operation.

In most cases, the connection is restored automatically.

Best Practices

  • Avoid sending continuous EWS requests without delay
  • Reduce parallel connections when retrying
  • Allow time between retries to prevent repeated throttling

Summary

The “Unable to connect to the remote server” error is a temporary network or service-level issue caused by throttling, service interruptions, or inactive services. Checking server services and retrying after a short wait usually resolves the issue.