Microsoft Power Apps
Discover the low-code apps across your Power Platform environments and bring them into your Airia inventory.
Airia connects to your Microsoft Power Platform tenant and discovers the Power Apps across your environments. It enumerates every environment in the tenant, then lists the apps in each one.
This connector complements Microsoft Copilot Studio discovery, which covers the bots, with visibility into the app estate those bots and AI features live in.
At a glance
| Surface | Cloud AI |
| What it does | Agent Discovery — inventories the Power Apps across your Power Platform environments |
| How Airia connects | A Microsoft Entra ID service principal with a client secret |
| Who sets it up | An admin who can register apps in Entra ID, plus a Power Platform administrator |
| Time | ~15 min |
Authentication model
A Microsoft Entra ID service principal with a client secret. Airia acquires tokens for two Microsoft APIs:
| API | Purpose |
|---|---|
Power Platform API (api.powerplatform.com) | List apps per environment |
Business Application Platform admin API (api.bap.microsoft.com) | Enumerate the tenant's environments (admin scope) |
Because the environment enumeration uses the admin scope, the service principal must be registered as a Power Platform administration application for your tenant. That's Microsoft's mechanism for granting a service principal tenant-wide Power Platform admin API access. A Power Platform administrator performs this registration once for the app.
Setup
Register the application in Entra ID
- In the Azure portal, open Microsoft Entra ID → App registrations → New registration. Name
it something recognizable, for example
airia-powerapps-discovery. - Create a client secret and copy it.
- Note the Application (client) ID and the Directory (tenant) ID.
Register it as a Power Platform administration application
Have a Power Platform administrator register the app as a Power Platform administration application for the tenant. Microsoft's Power Platform admin center documentation covers this registration.
Without it, authentication succeeds but environment enumeration fails.
Create the connection in Airia
Go to Discover → Connect, click the Microsoft Power Apps tile, and create a new connection.
| Field | Required | Notes |
|---|---|---|
| Tenant ID | Yes | Entra tenant GUID |
| Client ID | Yes | The app registration's client ID |
| Client secret | Yes | Stored encrypted, masked on edit |
Verify it worked
The connection test validates configuration, authentication, environment enumeration access, and app listing access, in that order. Discovered apps then appear in your Airia inventory.
Troubleshooting
| Symptom | Fix |
|---|---|
| Authentication succeeds, environment enumeration fails | The admin-application registration is missing. Have a Power Platform administrator register the service principal as a Power Platform administration application. |
| Connection test fails at authentication | Re-check the tenant ID, client ID, and client secret. A secret that has expired in Entra ID is a common cause. |
| No apps discovered | Confirm the environments actually contain Power Apps, and that the admin registration covers the whole tenant. |
Multiple environments
Multiple Microsoft Power Apps connections per tenant are supported: one per Entra tenant. Use the per-connection Name field to label them.
What you can do
Discover — see the low-code app estate across every Power Platform environment in the tenant.
Govern — discovered apps are inventoried, so you can classify them, assign owners, score risk, and track them in governance use cases.
| Capability | Supported |
|---|---|
| Discover | Yes |
| Govern | Yes |
| Secure | — |
Related
- Microsoft Copilot Studio — the bots and flows built on the same Power Platform.