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
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.
'Copilot Studio' 카테고리의 다른 글
Copilot Studio. Finding the Custom Connectors menu in Power Platform. (2) | 2024.10.19 |
---|---|
Copilot Studio. Setting up message delivery to Teams via Power Automate for specific input. (1) | 2024.10.15 |
Copilot Studio. Configure single sign-on with Microsoft Entra ID (2) | 2024.10.09 |
Copilot Studio. Deploying Copilot to an IIS Site. (1) | 2024.10.05 |
Copilot Studio. Create New Copilot (1) | 2024.10.05 |