New Environment - can create powerapps but not flows

(0) Share

Report

Posted on by pwapp_explorer

We created a new PowerApps environment - it is now "Dynamics365Instance" environment type.

Security is now administered differently - it is administered in the "Dynamics 365 user management center"

So we clicked the link, and clicked "Manage User Roles", we asigned both "Environment Maker" and "System Administrator" role to the user

The user can create a PowerApp, but cannot create flows.

In flow they get "Acces to the environment '' is denied"

Any ideas on what to do to get the security to work for flows?

Categories:

Governance & administering

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Pstork1 69,481 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

If its working in PowerApps, but not in Flow then I would verify that they have a Flow license assigned to them. The Environment Maker and System Administrator roles will apply to both PowerApps and Flow. But the actual license is assigned seperately. If you are a member of the role but don't have a license then you will be denied access.

Was this reply helpful? Yes No
pwapp_explorer 28 on at

Like (0)

Report
Copy link

Link copied!

Thanks - what doesn't make sense is in other environments can edit both flow and powerapps - its only this one environment.

Was this reply helpful? Yes No
jo Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Can you shoot me a quick email (at jamesol@microsoft.com) with the environment and user account that is reproing the behavior?

Was this reply helpful? Yes No
yashag2255 24,769 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey!

You can administer the role from the admin center -> Users -> Licenses assigned -> (check if the appropriate license has been assigned)

Also, for the new environement, you can try by assigning the System Administrator role to check if the flow can be created with that role. If Yes, you just have to re assign the "Environemnt Maker" role, log out of all windows and start a new session.

Thanks,

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No