Visual Studio Team Services Connector: Can´t connect with different Account

[Anonymous]

Hi,

we are trying to synchronize jira & vsts with flow. When I connect to visual studio team services the connector takes the current login of flow (businessaccount@flow.de). But this is actually not the one which has accecs to team project in vsts (msdnuseraccount@outlook.de). Single Sign on is sometimes a good thing but not in this case.

My question is: Is there any way to use the vsts connector with a different account (msdnuseraccount@outlook.de) ?

What i tried so far is using differnt browsers (Firefox 55.0.3, Edge 38.14393.1066.0) and also started them in private mode.

[v-micsh-msft]

Hi @Anonymous,

You should be able to switch the credentials by clicking top right of the VSTS action added in Flow:

Besides, you may also first create the VSTS connection under the Connections portal, then switch the credentials instead of adding it under Flow configuration.

For more information about manage connections, check:

Manage connections in Microsoft Flow

Regards,

Michael

[Anonymous]

Hi,

thanks for the reply.

No, you are not able to switch the credentials when you click on "add new connection". After clicking on it you are forwarded to an login-popup where you only can accept or decline to grant flow the permission to access vsts with the current account logon to flow.

Thanks for feedback

BG

 Stefan

[nannari]

As Stefan notes, you are not able to switch credentials, creating a connection via the /manage/environments/-page also results in the same behaviour. It connects you to visual studio using your currently logged in account.

In my case, this renders the connector completely useless.

[Ramazan_BIYIK]

I think you can do it with VSTS settings. Go to manager account main page on VSTS. Click user. Add an account with a Basic Access. Add  that user to your project. After that you can see that account on your flow when you choose the manager account.

As you can see ı can see both account. But ı can't access all the project inside manager account as expected. I hope it could help