If MigrationWiz cannot connect to your source Exchange environment, AutoDiscover may be the real cause even when the error looks like a credential issue. By default, MigrationWiz uses AutoDiscover to locate the Exchange Web Services endpoint for the source tenant.

For standard Exchange Online sources, that usually works. Problems show up in hybrid environments, on-premises Exchange targets with non-standard AutoDiscover DNS records, or Exchange Online tenants where the AutoDiscover CNAME routes through a third-party mail filtering service. In those cases, AutoDiscover can return an outdated, incorrect, or unreachable EWS endpoint.

When that happens, MigrationWiz fails to bind to EWS and reports a connectivity error that often gets mistaken for bad credentials. The credentials are fine. The resolved EWS URL is not.

The fix is to disable AutoDiscover in the source endpoint configuration and enter the EWS URL manually. In Exchange Online, that URL is always the standard Microsoft EWS endpoint. For on-premises Exchange, use the CAS server external FQDN with the standard EWS path.

When MigrationWiz reports source endpoint connectivity errors, have you manually validated the EWS endpoint URL it should be using?

#BitTitan #MigrationWiz