microsoft / microsoft/Power-CAT-Copilot-Studio-Kit

Feature request: Native Power Platform Inventory API for Agent Discovery

Open
#824 1 comment 0 reactions 2 assignees View on GitHub

@purnananda is already working on this.

Since Aug 25, 2026.

enhancement
Dominant language
TypeScript
Stars
450
Forks
95
Avg merge
26m
Merged PRs (30d)
5

Description

Problem statement

User Story

As a Platform Administrator, I want to retrieve tenant-wide agent inventory through a PPAC API so that inventory solutions can operate without requiring highly privileged accounts across every environment.

##Problem
Agent discovery currently requires direct access into environments, resulting in:

  • Complex permissions
  • Elevated service accounts
  • Increased operational overhead
  • Security concerns

Justification

PPAC already possesses tenant-wide visibility of environments and assets.

A dedicated inventory API would:

  • Improve scalability
  • Reduce permissions
  • Simplify integrations
  • Improve governance tooling
Proposed solution

Proposed Approach

Introduce a PPAC-managed API capable of returning:

  • Agent metadata
  • Maker information
  • Environment information
  • Ownership metadata
  • Usage metadata
  • Compliance metadata
  • Copilot Credit usage data

New Role

Agent Governance Reader
Assigned to a Service Account and Users for PPAC UI and API access.
Assigned in M365 Admin Center similar to the Power Platform Administrator

Capabilities:

  • Read Agent Inventory
  • Read Agent Metadata
  • Read Usage Statistics
  • Read Compliance Status
  • Read Copilot Credit Usage
Additional context

You're right, it's not a Kit Feature Request (yet)

I understand the irony here that this is not for the Agent Kit. Microsoft will hopefully see this Feature Request and ask the PPAC team to implement it 😊

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.