web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Power Apps for Makers ...
Power Apps
Suggested Answer

Power Apps for Makers connector - Get Environments action does not return permissions data

(0) ShareShare
ReportReport
Posted on by 2,254 Super User 2026 Season 1
Hi everyone,
I am using the Power Apps for Makers connector's Get Environments action in Power Automate and Canvas Apps to retrieve environments available to the logged-in user.
The response returns environment properties like displayName, createdTime, and environmentType, but the properties.permissions object is always null or missing from the response.
 
I verified this behavior in three places:
  • Power Automate cloud flow using the Get Environments action
  • Canvas App using the Power Apps for Makers connector
  • Power Apps (PowerFx) formula bar - like accessing the properties.permissions directly.
In all three cases, permissions are not returned.
 
However, when I use the Power Apps PowerShell module with the same user account, permissions are returned correctly: (The power shell module name is "Microsoft.PowerApps.PowerShell")
Get-PowerAppEnvironment | ForEach-Object {
    [PSCustomObject]@{
        EnvironmentName = $_.EnvironmentName
        DisplayName     = $_.DisplayName
        Permissions     = ($_.Internal.properties.permissions | ConvertTo-Json -Depth 10)
    }
}
This script returns the full permissions block for each environment, including CreatePowerApp, CreateFlow, CreateCustomConnector, CreateDLPPolicy, and other permission fields. The same user, the same environments, but the connector does not return what the PowerShell module returns.

The inconsistency:
The connector's own documented response schema at  https://learn.microsoft.com/en-us/connectors/powerappsforappmakers/#get-environments lists permission fields like CreatePowerApp, CreateFlow, etc. in the response definition. This means the connector is designed to return these fields, but they are never populated in the actual response.


Did anyone face this issue? if yes, how did you resolve it. any suggestions, advice !!!!
I have the same question (0)
  • Suggested answer
    11manish Profile Picture
    3,333 on at
    Based on your testing, the issue does not appear to be user permissions, licensing, or environment configuration. Since the PowerShell module returns the
     
    permissions block correctly while the Power Apps for Makers connector does not, the most likely explanation is a connector implementation gap or
     
    documentation mismatch. If those permission values are business-critical, I would recommend using the Power Platform Admin APIs or PowerShell as the
     
    authoritative source and opening a Microsoft support ticket referencing the connector documentation that still lists the permission fields in the response
     
    schema.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 424

#2
WarrenBelz Profile Picture

WarrenBelz 355 Most Valuable Professional

#3
11manish Profile Picture

11manish 290

Last 30 days Overall leaderboard