Power Platform CoE issue & Magic of PowerShell

While working for Power Platform CoE set up another team, I ran into into weird error.

Background

The Power Platform Center of Excellence (CoE) serves as a centralized body within organizations, managing and optimizing Microsoft's Power Platform, which encompasses Power BI, Power Apps, Power Automate, and Power Virtual Agents. This CoE orchestrates the platform's deployment, adoption, and governance, ensuring it aligns with the organization's strategic goals and standards.

Benefits:

1. Governance & Compliance: The CoE establishes and enforces best practices, ensuring that data usage, application development, and automation adhere to regulatory standards and internal policies.

2. Efficient Development & Deployment: By offering standardized tools, templates, and guidance, the CoE streamlines the creation and deployment of applications and workflows, reducing redundancy and saving time.

3. Enhanced Efficiency & Productivity: Through automation facilitated by the Power Platform, the CoE enables teams to automate repetitive tasks, freeing up time for more value-adding activities and boosting overall productivity.

4. Cost Savings & Reduced External Dependency: With in-house expertise and guidance from the CoE, organizations can rely less on expensive external solutions, thereby reducing costs associated with third-party services.

5. Culture of Innovation & Agility: The CoE encourages innovation by empowering teams to rapidly develop applications and analyze data. This fosters a culture of experimentation, adaptability, and data-driven decision-making within the organization.

Problem

I need to ensure I can look for all premium and standard connectors within an organization that has been used. I was told that users are not able to environment requests is not working, and checked the Maker - Environment Request canvas app which is part of CoE as follows:

When I played the app I got this error.

I had no absolutely what is quarantined app and why it its quarantined.

Solution

A lot of blogs and solutions were around and I wasted nearly half a day troubleshooting.

But one of the articles truly helped me and I want to share how I resolved it.

1. Install Power Apps for PowerShell
2. Copy the PowerShell into your Windows 11 PC and run PowerShell as admin

winget search Microsoft.PowerShell        

3. if you are not an administrator of your PC, you still can install and configure the modules quickly and easily

Install-PackageProvider -Name NuGet  -Force -scope CurrentUser
Install-Module -Name Microsoft.PowerApps.Administration.PowerShell -Scope CurrentUser –Force
Install-Module -Name Microsoft.PowerApps.PowerShell -Scope CurrentUser -AllowClobber –Force
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned –Force        

Should you desire a somewhat more comprehensive explanation BELOW

4. The PowerShell PowerApps commands are acquired through a NuGet server that is managed by Microsoft.

Get-PackageProvider        

5. Install the NuGet Package Provider.

Install-PackageProvider -Name NuGet  -Force -scope CurrentUser
        

6. PowerApps Administration PowerShell cmdlets AND PowerApps Maker PowerShell cmdlets

Install-Module -Name Microsoft.PowerApps.Administration.PowerShell -Scope CurrentUser -Force        

Install-Module -Name Microsoft.PowerApps.PowerShell -Scope CurrentUser -AllowClobber -Force        

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned –Force        

7. Now comes with the LITMUS TEST. Connect to your PowerApps environment(s).

Add-PowerAppsAccount

8. When prompted, enter your credentials!

9. Final Result