Showing results for 
Search instead for 
Did you mean: 
Not applicable

Power Platform Checker: is it possible to use for Power Apps Portals downloaded with Power Platform CLI

Hello all,


I am trying to integrate Power Platform Checker for PowerApps Portal using Power Platform CLI and Azure DevOps.


The portal is downloaded and placed into Git using the Power Platform CLI. I can deploy PowerApps Portal into any environment using the same Power Platform CLI tool and Azure DevOps.


The 1st question, is this supported to use the Power Platform Checker for PowerApps Portals? Checker works perfectly for Dataverse solutions which are packed (managed or unmanaged) with Microsoft Power Platform Build tools.


If it's supported, what I am doing wrong?


Build (YAML) pipeline looks like as per example below:



  vmImage: "Windows-latest"

- stage: Build
  displayName: Build stage
    - job: Build
      displayName: Portal Solution
          - task: ScreenResolutionUtility@1
            displayName: 'Set Screen Resolution'
          - task: PowerPlatformToolInstaller@0
            displayName: Power Platform Tool Installer
              DefaultVersion: True
          - task: ArchiveFiles@2
            displayName: 'Archive Files'
              rootFolderOrFile: '$(Build.SourcesDirectory)/$(SolutionXPortal)/$(SolutionXPortalFolder)'
              includeRootFolder: false
              archiveType: 'zip'
              archiveFile: '$(Build.ArtifactStagingDirectory)/$(SolutionXPortalFolder).zip'
              replaceExistingArchive: true
          - task: PowerPlatformChecker@0
            displayName: Power Platform Checker
              PowerPlatformSPN: $(BuildEnvSvcConnTest)
              FilesToAnalyze: '$(Build.ArtifactStagingDirectory)\$(SolutionXPortalFolder).zip'
              RuleSet: '0ad12346-e108-40b8-a956-9a8f95ea18c9'
              ErrorLevel: LowIssueCount
            continueOnError: false
          - task: PublishBuildArtifacts@1
            displayName: Publish Artifact - Drop
              PathtoPublish: '$(Build.ArtifactStagingDirectory)'
              ArtifactName: 'drop'
              publishLocation: 'Container'
          - task: AddBranchToBuildNumber@1
            displayName: Add branch name to build number
              samplestring: 'dev'



 Error getting in Azure DevOps:



Starting: Power Platform Checker
Task         : Power Platform Checker
Description  : Analyze solutions using Power Apps Checker endpoint
Version      : 0.0.40
Author       : Microsoft
Help         : [More Info](
VERBOSE: InProcBindingRedirect: 2 - looking to resolve assembly: Microsoft.PowerShell.ConsoleHost.resources, 
Version=, Culture=en-US, PublicKeyToken=31bf3856ad364e35
VERBOSE: InProcBindingRedirect: 1 - looking to resolve assembly: Microsoft.PowerApps.Checker.PowerShell
VERBOSE: InProcBindingRedirect: 3 - looking to resolve assembly: Microsoft.PowerApps.Checker.Client
VERBOSE: InProcBindingRedirect: 4 - looking to resolve assembly: Microsoft.IdentityModel.Clients.ActiveDirectory
Starting PowerApps Checker Analysis...
	RuleSet: Solution Checker
	Error Level: Low
	Error Threshold: 0
VERBOSE: InProcBindingRedirect: 5 - looking to resolve assembly: System.Management.Automation.resources, 
Version=, Culture=en-US, PublicKeyToken=31bf3856ad364e35
##[error]Value cannot be null.
Parameter name: source
Finishing: Power Platform Checker





Helpful resources

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Top Solution Authors
Users online (1,826)