Answered

Sign in topic doesn't work

(0) Share

Report

Posted on by MarkShark

Hello !

I successfully set up working deployment of Copilot Studio copilot with Manual authentication. I got 'Login' option, was redirected to webpage where I received code, pasted code to bot and it worked. I even added the app to MS Teams(with .zip) and it worked:

Suddenly I receive this message:

---------------------------------------------------------------------------------------------------------------------------------------

Sorry, something went wrong. Error code: SystemError. Conversation ID: 642bc33e-a49c-468c-981d-30854e7c4021. Time (UTC): 4/8/2024 8:05:28 PM.

I suppose something is wrong with Authenticate node in Sign in Topic.

Any suggestions ?

Categories:

Topic creation & management

I have the same question (0)

All responses (12)

Answers (1)

Verified answer

adilei on at

Like (1)

Report

When setting up SSO with Teams correctly, you should not be getting the sign in card. Signing-in should be seamless. Did you follow the instructions here?

Configure single sign-on for the Microsoft Copilot Studio app in Teams - Microsoft Copilot Studio | Microsoft Learn

Was this reply helpful? Yes No
MarkShark 39 on at

Like (1)

Report

Thank you @adilei. I missed provided instructions. Now I thoroughly followed it but same error still immediately when I open the copilot in Copilot Studio:
Regards, Marko

Was this reply helpful? Yes No
adilei on at

Like (0)

Report

Is there any logic in your conversation start or greeting topics that may fail?

Was this reply helpful? Yes No
MarkShark 39 on at

Like (0)

Report

@adilei thank you very much for your help. Your general answer is a way to go but I really miss comprehensive user guide it's kind of tricky combining different parts. I imagine that very common use case will be: 1. Create a bot, 2. Connect it to Teams, 3. Give it Sharepoint resource(s). To set correct permissions you really have to crawl around the documentation.

In my case, I didn't have to do manual app registration in Entra ID - it's been already created when you create Copilot. This for example, I didn't see written anywhere. When I used this automatically created app registration (named "ChatBot Test(Power Virtual Agent)") and configured it according to the documentation it worked 😁 !

Little reminder - the official documentation has wrong image here: https://learn.microsoft.com/en-us/microsoft-copilot-studio/configure-sso-teams#add-sso-to-your-bots-microsoft-teams-channel

Was this reply helpful? Yes No
adilei on at

Like (0)

Report

Why is it wrong?

Was this reply helpful? Yes No
MarkShark 39 on at

Like (0)

Report

Image in red mark is wrong, it's the same like image in green mark. Text is about Application Client ID, image shows Resources URI.

Was this reply helpful? Yes No
adilei on at

Like (0)

Report

So it's Client ID that needs to be highlighted in the first image and not Resource URI? Got it - let's see if we can fix it.

Otherwise, I would not use the App Registration that is created by default. That app registration has a different purpose.

Was this reply helpful? Yes No
MarkShark 39 on at

Like (0)

Report

OK, but is written "For AAD application's client ID, enter the Application (client) ID from your app registration." but on the image Resource URI is marked instead of AAD application's client ID.

Was this reply helpful? Yes No
adilei on at

Like (0)

Report

And I already agreed this should be fixed 🙂

Was this reply helpful? Yes No
johnnnn 6 on at

Like (0)

Report

Hi MarkShark, were you able to find a solution to this? I'm having the same problem where I set up auth manually, input the correct Client ID and Client Secret from App Registrations on Azure and everything worked. Now all of a sudden, I'm getting:

"Hello! To be able to help you, I'll need you to sign in."

"Sorry, something went wrong. Error code: SystemError."

If you can help me out, that'd be great, thanks!

John

Was this reply helpful? Yes No