Add user authentication to topics

Add user authentication to a topic to allow your customers to sign in right in the conversation. You can then personalize the conversation with user variables and access back-end systems on the user's behalf.

You need to configure user authentication with Microsoft Entra ID before you can use authentication in your topics.

Follow the instructions in Configure user authentication with Microsoft Entra ID.

When you create an agent, Copilot Studio automatically adds a system topic called Sign in. To use it, you must set your agent's authentication to manual and require users to sign in. When a customer starts a conversation with the agent, the Sign in topic triggers and prompts the user to sign in. You can customize the Sign in topic as appropriate for your agent.

1. Open your agent in Copilot Studio, select Settings at the top of the page, and then select Security.

2. Select Authentication.

3. Select Authenticate manually, and then select Require users to sign in.

4. Configure all manual authentication fields, as required.

5. Select Save.

The Sign in topic authenticates the user at the beginning of the conversation. To allow the user to sign in later, you can add an Authenticate node to any custom topic.

When customers enter their user name and password, they might be prompted to enter a validation code. After they sign in, they're not prompted again, even if they reach another Authenticate node.

1. Select Settings at the top of the page, and then select Security.

2. Select the Authentication tile.

   Note

   You must select Authenticate manually to add user authentication to a custom topic.

3. Clear the Require users to sign in checkbox.

4. Configure all manual authentication fields, as required.

5. Select Save.

6. Select Topics at the top of the page.

7. Select Add node ( ) > Advanced > Authenticate.

8. Test your topic with a user configured with your identity provider.

When you configure user authentication for your agent, you can use authentication variables in your topics. The following table compares the availability of these variables based on the authentication option you chose.

For more information about variables, see Variables overview.

The User.DisplayName variable contains the display name stored in the identity provider. Use this variable to greet or refer to the user without their having to explicitly give their name to the agent, making the conversation more personalized.

Copilot Studio automatically sets the value of User.DisplayName from the name claim provided by the identity provider, as long as the profile scope was defined when manual authentication was configured. For more information about scope, see Configure user authentication with Microsoft Entra ID.

The User.Id variable contains the user ID stored in the identity provider. Use this variable in Power Automate flows to call APIs that take the UserID as a value.

Copilot Studio automatically sets the value of User.DisplayName from the sub claim provided by the identity provider.

User.IsLoggedIn is a Boolean variable that stores the user's sign-in status. A value of true indicates the user is signed in. You can use this variable to create branching logic in your topics that checks for a successful sign-in, or to fetch user information only if the user is signed in.

The User.AccessToken variable contains the user's token, obtained after the user is signed in. You can pass this variable to Power Automate flows so they can connect to back-end APIs and fetch user information, or to take actions on the user's behalf.

Don't use User.AccessToken in Message nodes or in flows that you don't trust.

SignInReason is a choice-type variable that indicates when the user must sign in. It has two possible values:

• SignInRequired indicates the user must sign in at the beginning of the conversation using the Sign in system topic. Require users to sign in must be turned on.

• Initializer indicates that when a user isn't signed in, and they reach a point in the conversation that uses authentication variables, they're prompted to sign in.

If your agent is configured with either Authenticate with Microsoft or Manual authentication options, you have a set of authentication variables available in your topics. For more information on how to configure authentication in your agent, see Configure user authentication in Copilot Studio.

The following table compares authentication variable availability by authentication configuration option:

The User.DisplayName variable contains the user's display name stored in the identity provider. You can use this variable to greet or refer to the customer without them having to explicitly tell it to the agent, making it more personalized.

This field value is obtained from the Microsoft Entra ID name claim. For OAuth providers, this value is stored in the name claim. Copilot Studio automatically extracts this field into the variable, so ensure you have profile as part of your authentication scope setup.

The User.Id variable contains the user's ID stored in the identity provider. Power Automate flows can use this value to call APIs that take the UserID as a value. This field value is obtained from the Microsoft Entra ID sub claim. For OAuth providers, this value is stored in the sub claim. Copilot Studio automatically extracts this field into the variable.

The User.IsLoggedIn variable indicates whether the user is signed in (either as a result of signing in or already being signed in, also known as the log-in success path) or not signed in (which would result in the log-in failure path).

User.IsLoggedIn is a Boolean variable containing the signed-in status of the user. You can use this variable to create branching logic in your topics that checks for a successful sign-in (for example, in the template already provided as part of adding the Authenticate node), or to opportunistically fetch user information only if the user is signed in.

The User.AccessToken variable contains the user's token, obtained after the user is signed in. You can pass this variable to Power Automate flows so they can connect to back-end APIs and fetch the user's information, or to take actions on the user's behalf.

Don't use User.AccessToken inside Message nodes, or on flows that you don't trust.

By default, the Test bot pane uses the account of the currently signed-in user to populate the User.DisplayName and User.Id variables. However, when testing topics that use authentication, you might want to use other values for these variables (or even a blank value).

For example, you might want to test how special characters are used, or what happens if the variable is empty.

The following table lists the commands to populate these variables. These commands only apply to the Test bot pane; you can't use them in a published agent deployed to a channel.

Enter the desired command into the Test bot pane just as you would if you were normally chatting with the agent. You'll receive a confirmation message from the agent if you're successful. If your agent doesn't use authentication, you'll receive an error.

If you reset the Test bot pane (or you make changes to a topic that cause the Test bot to reset automatically), you'll need to send the commands again.

If your authentication option is set to Authenticate with Microsoft, you don't need to explicitly add authentication to your topics. In this configuration, any user in Microsoft Teams is automatically signed in via their Teams credentials and they don't need to explicitly sign in with an authentication card. If your authentication option is set to Manual, then you must add an Authenticate node (even for the Teams channel).

The Authenticate node prompts a user to sign in with a sign-in card. Once a user is signed in, they aren't prompted again, even if they reach another Authenticate node.

Once the user enters their user name and password in the prompt (hosted by the identity provider), they might be prompted to enter a validation code, depending on the channel. Some channels, such as Microsoft Teams, don't require a validation code from the user.

When your agent has SSO configured, the user won't be prompted to sign in.

To add an Authenticate node to your topic:

1. Go to the Topics page for the agent you want to edit.

2. Open the topic to which you want to add the authentication template.

   Note

   If your agent is connected to Dynamics 365 Customer Service, the Authentication node can't be part of the conversation path the agent follows when initially greeting users; otherwise, the sign-in card will be shown twice. Instead you should add the Authenticate node to another topic that is triggered by a user response.

3. Select Add node (+) to add a message node. Enter what the agent should say to indicate that a sign-on experience is about to occur.

   

4. Underneath the message node, select Add node (+), select Call an action, and then select Authenticate.

   

   Note

   The Authenticate node is only available in the action picker at the end of a dialog tree (as a leaf node). It cannot be added in the middle of a dialog. Once added, other nodes can be added below it.

   New nodes appear automatically: a parent Authenticate node, followed by nodes for a success path and a failure path.

The User.IsLoggedIn and User.AccessToken variables are available even if you don't use the template provided by the Call an action menu entry. If you pass the User.AccessToken variable without first having the user go through the Authenticate node, the user will be prompted to sign in at that step.

Passing the User.AccessToken variable can be useful if you always expect the user to be signed in, or if your user is being redirected from a different topic. We suggest you use the template provided by the Call an action entry to treat cases where the user fails to sign in.

The success path equates to where User.IsLoggedIn = True and accounts for when the user has successfully signed in (or was already signed in).

If you have logic that uses the User.AccessToken variable (for example, to connect to a back-end system using a flow to retrieve a user's information), it should go under this path.

The failure path equates to any condition other than IsLoggedIn = True. In most cases, the failure path occurs because the user failed to sign in, used the wrong password, or canceled the sign-in experience.

Add any logic you might want to treat this case. As an example, we have provided options for retrying or to escalate to a live agent. Customize the failure path's actions for your particular scenario and usage.

Make sure to test your topic using a real user configured in your identity provider. Ensure both the sign-in success and failure paths are exercised, so there are no surprises if your user fails to sign in or there's an error with the identity provider's sign-in experience.