Pepuri Server world Eng Version

This time, let's create a flow where a specific message entered into the chatbot is sent as a Teams notification to the person in charge.

With some modifications, you can create automated flows from the chatbot, such as sending emails.

In the existing Copilot, you can see that topics have default settings to trigger actions based on specific conditions.

Here, we will create a flow that sends a Teams notification to the person in charge when Escalate is triggered.

https://youtu.be/NyJqE8SJZ7Q

First, click Settings.

Security -> Authentication

Ensure that the authentication settings are configured as shown on the screen.

(If they are not set up, refer to the SSO setup video and complete the configuration.)

Topics -> Escalate -> Add Node

Call an action -> Create a flow

Add an action

Runtime -> Standard -> Microsoft Teams

Post message in a chat or channel

Select and enter the information as shown on the screen.

Change the flow name

Save draft

Test

Manually -> Publish & Test

Receive messages from Workflows.

Return to the Copilot Studio page -> Click Done.

Add Node -> Call an action -> Escalation Case

Publish

Enter Escalate to run the test.

The permission configuration process is required. -> Connect

Connect

Submit

Confirm the status

Retry

The configured message is delivered, and

You can confirm that it has been delivered to Teams.

With this pattern, you can create various connection flows between M365 and other services using Power Automate.

When troubleshooting in M365, it's common for administrators to use PowerShell for the process.

However, it raises the question of whether this really needs to be done within Copilot Studio. Nonetheless, I decided to write about it since there are tasks that occasionally require PowerShell.

This was carried out with reference to the technical documentation below.

PowerShell support for Power Apps and Power Automate - Power Platform | Microsoft Learn

https://youtu.be/q3fEnEcXH0k

The steps were carried out on Windows 11.

Click the Start button -> Right-click -> Select Terminal (Admin).

Execute the following command:

Install-Module -Name Microsoft.PowerApps.Administration.PowerShell
Install-Module -Name Microsoft.PowerApps.PowerShell -AllowClobber
Set-ExecutionPolicy -ExecutionPolicy Unrestricted

If the following message appears, enter Y or A.

Since Power Apps and Power Automate are different areas, each requires a separate login.

Unlike Exchange Online, there is no need to enter separate connection commands. Simply enter the command you wish to use, and it will prompt you to provide your credentials.

Enter the following command to connect to Power Apps:

Get-AdminPowerAppEnvironment

Enter the following command to connect to Power Automate:

Get-AdminFlow

In the future, if a PowerShell connection is needed for Copilot Studio, you can access and utilize it as required.

In the previous post, a new Copilot was published on the site.

2024.10.05 - [Copilot Studio] - Copilot Studio. Deploying Copilot to an IIS Site.

This time, I have written about how to configure Entra ID and SSO in cases where the organization requires that only authenticated users have access.

The following technical documentation was used as a reference.

Configure user authentication with Microsoft Entra ID - Microsoft Copilot Studio | Microsoft Learn

Configure single sign-on with Microsoft Entra ID - Microsoft Copilot Studio | Microsoft Learn

Entra Admin Center -> Applications -> App registrations -> New registration

After entering the App name, click Register (At this stage, the Redirect URI is optional. The URL below was created based on my test page.).

Navigate to Authentication.

Add the following URL mentioned in the technical documentation.

https://token.botframework.com/.auth/web/redirect

https://europe.token.botframework.com/.auth/web/redirect

Check Access tokens and ID Tokens -> Click Save.

Certificates & secrets -> Client secrets -> New client secret

Input Description  -> Add

Save the Value in advance.

Go to Overview and save the Application ID information.

API permissions -> Add a permission -> Delegated permissions

Add the permissions offline_access, openid, and profile. -> Grant admin consent for Contoso

Go to Copilot Studio and navigate to the Settings menu of the Custom Copilot you want to modify the authentication for.

Security -> Authentication -> Authenticate manually

Select Require users to sign in -> Enter Client ID (App ID) and Client secret (Value) -> Click Save -> Click Publish.

A message indicating that a login is required will appear as shown below.

Access the Copilot web page in a separate browser -> Click Login -> Complete the Login process.

Copy the Validation Code provided after logging in.

Enter a message in the chat window to confirm that the authentication was successful.

Since login cannot be implemented directly in the chat, it seems that the authentication process is carried out using a separate validation code.

By configuring it this way, you can set up security so that only users with an account can access the Custom Copilot.