Migration not working in exchange server

Hi Parsian02, 

Thank you so much for your follow-up and for clarifying the migration process you're using. I'm sorry to hear that the previous suggestions didn’t resolve the issue. Since I'm just a Q&A forum moderator, I don’t have access to the tools or environment needed to simulate and test this scenario directly. However, I’ve done some additional research and would like to share a few more suggestions that may help: 

1. Verify Basic Prerequisites and Connectivity 

Before diving deeper into configuration, it's important to rule out the fundamentals: 

• Ensure MRS Proxy is Enabled 
  Run the following in Exchange Management Shell: 

    Get-WebServicesVirtualDirectory | Select Name, MRSProxyEnabled 
  

  If MRSProxyEnabled is $false, enable it: 

    Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $true 
  

  Then restart IIS: iisreset /noforce. 
• Test External Accessibility 
  From an external machine, browse to: 
  https://mail.abcd.com/EWS/mrsproxy.svc 
  You should see a prompt for credentials or a WSDL-like response. If it times out, check: 
  • DNS resolution for mail.abcd.com 
  • Port 443 inbound through your firewall/load balancer 
  • Ports 80 and 8080 if using proxies 
• Check Certificate Validity 
  Ensure the SSL certificate for mail.abcd.com is valid and correctly bound in IIS. You can also test with: 

    Test-MigrationServerAvailability -ExchangeRemoteMove:$true -RemoteServer "mail.abcd.com" -Credentials (Get-Credential) 
  

• Review Network and Firewall 
  Confirm outbound access from your Exchange server to Exchange Online endpoints (e.g., outlook.office.com on port 443). Use Test-NetConnection or telnet. Reference Microsoft's hybrid ports guide for full details: Test-NetConnection (NetTCPIP) | Microsoft Learn  

2. Adjust Timeouts Properly 

You mentioned modifying files in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\EWS, but the changes may not have targeted the correct settings. 

• Open web.config (as Administrator) and locate: 

    <system.serviceModel> 
      <bindings> 
       <basicHttpsBinding> 
          <binding name="MrsProxyClientHttpsBinding" sendTimeout="00:05:00" receiveTimeout="00:05:00" /> 
        </basicHttpsBinding> 
      </bindings> 
    </system.serviceModel>
  

• Also check: 

    <appSettings> 
     <add key="DataImportTimeout" value="00:30:00" /> 
    </appSettings>
  

• Save changes and run iisreset /noforce. 

3. Authentication and Security Configurations 

• Check EWS Authentication 
  Run: 

    Get-WebServicesVirtualDirectory | FL *Authentication* 
  

  Ensure ExternalAuthenticationMethods includes NTLM or Negotiate. In IISManager, under Sites > Default Web Site > EWS > Authentication, enable Anonymous and Windows Authentication, with Negotiate above NTLM. 
• TLS Settings 
  Ensure only TLS 1.2 is enabled. Disable TLS 1.0, 1.1, and 1.3 via registry or PowerShell, then restart the server. 
• Disable Extended Protection (Temporarily) 
  Recent CUs may enable this by default, causing MRS issues.
  Run: 

    .\ExchangeExtendedProtectionManagement.ps1 -DisableExtendedProtection
  

  You can download the script from there: https://microsoft.github.io/CSS-Exchange/Security/ExchangeExtendedProtectionManagement/
  Then iisreset. Re-enable after testing if needed. 

4. Cycle MRS Proxy and Retest 

Try disabling and re-enabling MRS Proxy: 

Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $false 
Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $true 
iisreset /noforce 

Then test again from Exchange Online PowerShell: 

Test-MigrationServerAvailability -ExchangeRemoteMove:$true -RemoteServer "mail.abcd.com" -Credentials (Get-Credential) 

If none of the above steps resolve the issue, I recommend opening a support ticket with Microsoft: Get support - Microsoft 365 admin | Microsoft Learn 

Their support agents can assist more deeply with configuration and migration diagnostics. 

I hope these additional suggestions are helpful. Please feel free to reach out if you have any further questions! 

Hi Parsian02, 

Just checking in to see if the above information was helpful. 

Have you had a chance to check the replies provided?  

Any update would be appreciated. 

None of them worked

I was going through the articles of Microsoft and found that autodiscoveruri has been removed from exchange server. How to configure it in hybrid environment? For migration