Forum Discussion
Memorable MemberBUG::PIPELINE::TEAMS ACTIVITY::SIGN IN
The issue went away and all Teams activity are signed in now. Another one of those magic mysteries.
Memorable MemberStrange. I had 2 pipelines from 2 different workspaces loaded in the vertical Fabric nav bar. I close all of them and re-open only one. Now the Teams Sign in works automatically and loads everything as usual.
But as soon as I open the other pipeline from another workspace, the Teams activity does not auto Sign in and when I click on the Sign in button, no effect.
What gives?
- Element115
And now it doesn't do it!!! Seriously WTF?!
v-cboorla-msftMicrosoft Employee
Hi Element115
Apologies for the issue you are facing.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.
Appreciate your patienceThank you.
- v-cboorla-msft
Hi Element115
Apologies for the inconvenience.
I tried to repro the scenario with the above mentioned steps and didn't face any difficulty after clicking the sign in button.
1st Pipeline with teams activity in one workspace
2nd Pipeline with teams activity in another workspace.
I transitioned from using 1st pipeline to 2nd pipeline, and I was able to successfully authenticate without any interruption. Could you please verify this behavior on your end for confirmation?
If the issue still persists, please do let us know.
I hope this information helps.
Thank you.
- Element115
The issue went away and all Teams activity are signed in now. Another one of those magic mysteries.