@MdeRooij Aha! Looking through the logs made me realise there are two places where I needed to check for migration batches and endpoints - both the on-premises and the in-cloud Exchange Management Console. The wording about removing the 'existing... migration endpoint' (singular) confused me.
I removed the migration endpoint from Exchange Online and it all works now :)
Many thanks!
@KyleXu-MSFT Oh and in my original post I said I was running .NET Framework 4.6.2 - sorry that should have been at least 4.6.2 - actually running 4.8 (per the CU23 requirements)
Hi @KyleXu-MSFT,
Done this - there were no additional versions, and even if I uninstall & reinstall the current version it still doesn't work.
Done this - ran the following (still doesn't work):
Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $false
Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $true
Tried this with two new accounts with the permissions you requested - still doesn't work.
Anything else?
@tbgangav-MSFT @learner-7696
Had the same error today - I found that I needed to enable the 'Third-party application access via OAuth' in Azure DevOps / Organization Settings / Policies / Application connection policies
Apparently this policy is 'defaulted to off for all new organizations.'
https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/change-application-access-policies?view=azure-devops#application-connection-policies
It would be good if the Azure Automation documentation could be updated to reflect this necessary prerequisite.