Power Platform Community Forum Thread Details

Hello Community,

I am using the Microsoft.PowerApps.Checker.PowerShell module to understand Solution Checker rulesets and rules so that I can apply rule-level overrides correctly when running static analysis.

My goal is to:

Discover available rulesets
Inspect which rules belong to a given ruleset
Override specific rules using New-PowerAppsCheckerRuleLevelOverride
Execute Solution Checker via Invoke-PowerAppsChecker

However, I am facing consistent runtime issues with the discovery cmdlets.

Observed Issues

Ruleset discovery fails

Results in:

This occurs for all geographies (Asia, Europe, US, etc.).

Rule discovery is unusable

Results in:

Parameter set cannot be resolved

AmbiguousParameterSet

Environment Details

Windows PowerShell 5.1
Module: Microsoft.PowerApps.Checker.PowerShell v1.0.52
Newtonsoft.Json v10.x resolved
Authentication successful via Add-PowerAppsAccount
Invoke-PowerAppsChecker works correctly and generates reports

Understanding So Far

The module documentation states these cmdlets are pre-release
It appears the Power Platform backend API has changed
The PowerShell module may no longer align with the current service contract
Checker execution still works, but metadata discovery does not

Questions

Should developers rely instead on:

Checker output inspection (JSON/SARIF)?
PAC CLI?
Documentation only?

I am able to run Solution Checker and apply rule overrides, but the lack of a working discovery mechanism makes it difficult to manage rules programmatically.

Any guidance on the current supported approach would be greatly appreciated.

Thank you.

Are Get-PowerAppsCheckerRulesets and Get-PowerAppsCheckerRules still supported and expected to work?
Is this a known issue caused by backend changes?
What is the official/recommended way to:
- Identify which rules are applied by a ruleset?
- Determine valid Rule IDs for use with New-PowerAppsCheckerRuleLevelOverride?