I just recently saw an issue configuring new projects with Quest On Demand Migration (ODM) against Microsoft 365 tenants and running the Account Discovery Task in Quest On Demand Migration (ODM).
Quest On Demand Migration (ODM) is a Microsoft 365 tenant-to-tenant migration tool. It is a SaaS service run by Quest Software. It provides a straightforward and secure way to consolidate and migrate all your Microsoft 365 tenants. The tool can manage and migrate different workloads such as Exchange, OneDrive, SharePoint, and Teams, as well as on-premises Active Directory.
So this would be relevant for anyone using the Quest On Demand Migration (ODM) for tenant-to-tenant migrations and setting up new projects.
If you have already configured Quest On Demand Migration (ODM) and running migrations with it, it does not seem to be a problem.
The error that we see, comes when running the Account Discovery Task is
The details error description for the failed task is listed as:
Connecting to remote server outlook.office365.com failed with the following error message : For more information, see the about_Remote_Troubleshooting Help topic., Tenant : tenantname.onmicrosoft.com
First, you will need to confirm, that all the basic permissions are okay against the tenants and granted without issues:
But the root cause of this does not have to do with the permissions and the granted Quest Enterprise App registrations.
It seems to be related to the Deprecation of Remote PowerShell in Exchange Online.
You can test the status of Remote PowerShell in your tenant using this link, which links directly to your support page under your Microsoft Admin portal. Remember you will need Global Admin privileges to re-enable Remote PowerShell.
So the workaround would be to re-enable the Remote PowerShell for Exchange Online and rerun the Quest ODM Account Discovery Task, this got everything to work on our end.
Reference about Deprecation of Remote PowerShell in Exchange Online from Microsoft:
- Deprecation of Remote PowerShell in Exchange Online – Re-enabling or Extending RPS support – Microsoft Community Hub
This will be a temporary fix and a workaround to get the Quest On Demand Migration to work against your tenant. But be aware that Microsoft will continue to disable it for all tenants world-side on October 1st (2023).
Quest Software is supposed to update the Quest On Demand, so it is not using the Remote PowerShell for Exchange Online.