Accessing dev.azure.com environments fails

I am trying to sync work items between an project running as “environment.visualstudio.com” to “dev.azure.com/environment”. Unfortunately, I cannot login, the system rejects access to the dev.azure.com environment. I don’t even get an login prompt whatsoever.

Accessing said environment via Visual Studio 2017 works fine with my credentials.

If I try to sync to another environment.visualstudio.com-style site within the same AAD environment, things work like a breeze.

Broken config

{
	"TelemetryEnableTrace": true,
	"workaroundForQuerySOAPBugEnabled": false,
	"Source": {
		"Collection": "https://oldsite.visualstudio.com/",
		"Name": "someproject"
	},
	"Target": {
		"Collection": "https://dev.azure.com/newsite/",
		"Name": "Test"
	},

Working config

{
	"TelemetryEnableTrace": true,
	"workaroundForQuerySOAPBugEnabled": false,
	"Source": {
		"Collection": "https://oldsite.visualstudio.com/",
		"Name": "someproject"
	},
	"Target": {
		"Collection": "https://othersite.visualstudio.com//",
		"Name": "Test"
	},

I am a Project Collection Administrator level user in both target environments.

In the source environment I am a more limited user, but using it works fine in the second case, where the authentication constellation is the same. Note, however, that source belongs to another AAD domain.

Any insights would be helpful.

[MrHinsh]

The account that you use needs to have access to both Source and Target organisations. Make sure that the account is:

1. Added as a B2B Guest in the other Tennant (the one it’s not natively from)
2. Has been added to Collection Admins group on both Azure DevOps organisations.

[MichelZ]

Indeed interesting. I’m not really sure if the tool (and the client libraries that it uses) is designed for this scenario (2 different authentications for Azure DevOps).

My suggestion:

• Temporarily allow the user from one Org into the other Org, and just one set of Credentials for both temporarily for the Migration.

Worth a shot…