Summary Authentication - Training | Microsoft Learn learn.microsoft.com
2,306 words - html page - View html page
One Line
Copilot Studio offers various authentication options, including Teams, OAuth2, and no authentication, to enable user verification, personalization, and secure conversations, as well as conditional branching with user data.
Slides
Slide Presentation (14 slides)
Key Points
- Authentication settings in Microsoft Copilot Studio allow you to verify a user's identity during a conversation, enabling further personalization, executing actions on the user's behalf, and skipping dialogs by prefilling user data
- Authentication options include no authentication, authentication only for Teams, and manual authentication using OAuth2 identity providers like Microsoft Entra ID, Microsoft account, Google, Facebook, or a custom authentication service
- With manual authentication, you can register a new app with your identity provider and get a Client ID and Client Secret, which are then used to configure the authentication settings in Microsoft Copilot Studio
- Selecting "Require users to sign in" creates a system topic that prompts the user to sign in at the beginning of the conversation, while the "Authenticate" action can be called at any point to prompt the user to sign in
- Authenticated users have access to variables such as IsLoggedIn, AuthToken, UserDisplayName, and UserID, which can be used within topics
Summaries
26 word summary
Authentication in Copilot Studio enables user verification, personalization, and secure conversations. Options include Teams, OAuth2, or no authentication. Authenticate action enables conditional branching with user data.
44 word summary
Authentication in Microsoft Copilot Studio enables user verification, personalization, and secure conversations. Options include no authentication, Microsoft Teams, or manual OAuth2. Manual authentication requires registering an app and obtaining credentials. The Authenticate action sets up conditional branching with user data, improving experience and security.
119 word summary
Authentication in Microsoft Copilot Studio allows you to verify a user's identity, enabling personalization, user-specific actions, and seamless conversations. There are three authentication options: no authentication, authentication only for Microsoft Teams, or manual authentication with an OAuth2 identity provider.
To configure manual authentication, you need to register a new app with your identity provider and obtain a Client ID and Client Secret. In the Copilot Studio settings, select the Manual option and enter the required details.
The Authenticate action in your topics automatically sets up conditional branching, with variables for the authentication token, user login status, and user information. This flexibility allows you to mark certain parts of the conversation that require sign-in, enhancing the user experience and security.
412 word summary
Authentication in Microsoft Copilot Studio
Authentication in Microsoft Copilot Studio allows you to verify a user's identity during a conversation, enabling further personalization, the ability for the copilot to execute actions on the user's behalf, and the ability to skip dialogs by prefilling user data. It also makes user variables like ID and display name available for use within topics.
The authentication settings are found under the Security section in the Copilot Studio settings. There are three options:
1. No authentication: Anyone with access to the copilot can chat with it without signing in. No authentication variables are available.
2. Only for Teams: Authentication is enabled only for Microsoft Teams, turning off other channels. Only users you share the copilot with can use it.
3. Manual (For any channel including Teams): Supports OAuth2 identity providers like Microsoft Entra ID, Microsoft account, Google, Facebook, or a custom authentication service. Users can be prompted to sign in either at the start of the conversation or through an Authenticate action.
To configure manual authentication, you need to register a new app with your identity provider and obtain a Client ID and Client Secret. For Microsoft Entra ID, this can be done in the Azure portal.
1. Create a new app registration, providing a name and specifying which accounts can access the copilot. 2. Add a new client secret in the Certificates & secrets area. 3. Note the Application (client) ID and client secret value.
In the Copilot Studio authentication settings, select the Manual option and enter the Client ID, Client Secret, and optionally the Token exchange URL and Scope.
Once the authentication settings are saved and the copilot is published, you can use the Authenticate action in your topics. This automatically sets up conditional branching, with variables for the authentication token, whether the user is logged in, and the user's ID and display name.
If multiple topics require authentication, the user is only prompted to sign in once throughout the session.
The flexibility of the authentication settings allows you to mark certain parts of the conversation that require the user to sign in, while other parts don't. This can enhance the user experience and security of your copilot.
In summary, authentication in Microsoft Copilot Studio is a powerful feature that enables personalization, user-specific actions, and seamless conversations. By configuring manual authentication with an OAuth2 identity provider, you can tailor the sign-in experience to your needs and leverage user information within your copilot's topics and flows.