Oct 05 2018 04:21 PM
We are going through a merger, and as part of that must migrate our users from TenantA to TenantB. Currently we have separate AD domains and SSO platforms, though there is some federation (I'm not 100% clear on the details). We have a fair number of users who have not yet gotten on board with OneDrive, so rather than get them setup in TenantA, we'd like to push them over to TenantB right off the bat. If I go to tenantb-my.sharepoint.com and sign-in with my user@domainA.com credentials, I am able to view my OneDrive in TenantB (this was setup on our independent authentication SSO system and works fine).
The problem we're facing however is to force the user to connect to TenantB via the OneDrive client. If they use user@domainB.com on the "Sign in to OneDrive" window, we get an authentication error that we need to sign in with domainA credentials. If I use user@domainA.com, then it tries (and fails) to setup the OneDrive in TenantA (which is blocked by the "only allow certain tenants" GPO, mentioned below).
I've tried using the various GPO settings to force the OD client to only connect to TenantB. I've tried onedrive.exe /configure_business:tenantB-GUID, set EnableADAL (why isn't this a GPO option yet, btw!), Silent AutoConfig (with the requisite max OD size configured), but no matter what I do, OD always pops up with the "Enter your email address". Is there some other way to call onedrive.exe so that it suppresses the sign-in dialog, something like:
onedrive.exe /configure_business:tenantGBuid /useremail:user@domainA.com /silent /URL:https://tenantb-my.sharepoint.com
Am I maybe just coming up against a limitation of the OD client and how it can be manipulated to login to a specific tenant? I'm even tried pre-creating a Business1 account entry at HKCU\Software\Microsoft\OneDrive\Accounts\Business1\ with various fields pre-configured, like UserEmail = user@domainA.com or something (though that didn't work either; OD trashed the Business1 key and created it fresh when it tried to sign in).
Oct 06 2018 12:12 AM
I think the best person that can help here is @Stephen Rice. For sure he will point out to the right people that can support you
Oct 08 2018 07:21 AM
Oct 08 2018 06:38 PM
Hi all,
I don't have the key but let me pass this along to some of our area experts and see what we have. Thanks,
Stephen Rice
OneDrive Program Manager II
Oct 16 2018 01:26 PM
@Stephen Rice have you heard back from the tech team? I have a support case open on this as well, 118101519225226, though it seems to be more of a feature change than anything that is due to a "broken" client.
Oct 18 2018 10:27 AM
SolutionHi @KYLE SCHROEDER,
Sorry for the delay! The team is taking a look and may need additional details. It looks like the support case is still active as well so let's use that to engage & discuss. Thanks!
Stephen Rice
OneDrive Program Manager II
Jul 23 2019 12:26 PM
@Stephen Rice at this point our best option is to launch OD as follows (i.e. from a Batch file):
start odopen://sync/?userEmail=firstname.lastname@domain.com
There are some other parameters to odopen:// URLs, but for now, this is sufficient.
Oct 28 2022 04:07 PM
@Kyle Schroeder Hey, you got the answer for the same? I ran into the same issue. If yes, please provide the solution so that it will be helpful for all of us :)
Oct 29 2022 07:17 AM
@poojanair yes we went with the above parameters for odopen://and it worked fine for our purpose