The Autodiscover service couldn't be located

[rajayashwanth411]

Hi Team,

We were using Mail2Bug tool since long time and having an error The Autodiscover service couldn't be located after password change. we had to change the password and since then we couldn't use mail2Bug code due to autodiscover service.
I am able to use same credentials to test the connectivity without issues using the new password. When I run through the code we are getting error as "The Autodiscover service couldn't be located".

I tried to avoid autodiscover call and pass the service URL instead but getting error as UnAuthorized user with 401 code where I am able to login to the service using the same credentials.

Can some one help...!

[v-chneth]

I'm also having the same issue on a new service. Everything works but I keep getting the auto discover error
Microsoft.Exchange.WebServices.Data.AutodiscoverLocalException: The Autodiscover service couldn't be located.
at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetLegacyUserSettings[TSettings](String emailAddress, List`1 redirectionEmailAddresses, Int32& currentHop)

[favandemeer]

We are also facing this issue. Did you find a solution for this?

[davisjr]

If you are getting 401 after specifying the autod url, it's likely a bad password or your exchange server might have limited EWS access for the account you are using. Try:

1. Confirm your password is correctly updated in mail2bug.
   • if you used the dpapi tool to encode the password, try reading it using the same to make sure it's correct.
   • make sure the tool is run using the same credentials used to run the service.
   • unless the service is run elevated, make sure dpapi is all also run without elevation.
   • if your password has a $ in it, make sure it's escaped properly when running the tool.
2. Try a different account to run the service.

[holzerseb]

We are having the same issue - after testing with https://testconnectivity.microsoft.com/tests/exo the issue appears to due to Basic Auth being deprecated and disabled in our EWS environment. No option to use OAuth as it looks like: #129