Share
ReportHello to the community, I hope someone may be able to advise how to resolve an issue I have.
My PP tenant has 5 environments, all connected to Dataverse databases, 3 of which are Production with 2 as Sandbox. The logic is the 3 production environments have been created in 3 separate global regions and will be for production apps whilst the sandbox environments can be used for development.
Each of the 3 production environments has been secured with a security group from AD. This group was originally created on-premise and synchronised to AAD and is visible from AAD. I have deployed a Centre of Excellence and the identity that is being used to run the Flows used by the CoE is a member of all 3 security groups for the production environments however can only "see" 1 of them when looking at admin.powerplatform.microsoft.com/environments from the PP admin centre. This user also holds the PP admin role. When initially setup, this user was only in 1 of the 3 groups and so was added into the 2 additional groups but the view from the environments screen above will not refresh correctly to show the 2 missing environments. The knock-on effect of this is that the Flows that run to interrogate these environments that populate the dataverse tables, is not able to read these 2 extra environments so our PowerBI dashboard is only showing a single environment.
From running the user diagnostics for this user account against the 2 missing environments, shows green ticks across the board so PP does not seem to indicate an issue with any of the typical blockers to this access but it still fails. Can anyone please advise if there is a part of the process I have missed to give access to these missing two environments?
This same user cannot see the default environment which is a surprise as all users should have maker role to this environment and I was not aware this could be locked down.
All responses (
Answers (
345
