Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No environments or Flows after May 13, 2024 showing up in the Environment or Flow table in Dataverse #8645

Closed
1 task done
dcurt1977 opened this issue Jul 12, 2024 · 6 comments
Assignees
Labels
bug Something isn't working coe-starter-kit CoE Starter Kit issues

Comments

@dcurt1977
Copy link

dcurt1977 commented Jul 12, 2024

Does this bug already exist in our backlog?

  • I have checked and confirm this is a new bug.

Describe the issue

About a month ago the latest version 4.31 was deployed to a production environment. Noticed today that environments and flows created after May 13, 2024 not showing up in the Power Platform Admin View Model Driven App.

Expected Behavior

When new environments and flows get created in our tenant, new objects show up in the Power Platform Admin View Model Driven App.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.13

What app or flow are you having the issue with?

None

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

  1. New environment or flow created in tenant
  2. Check environment and flow table

Anything else?

No response

AB#3845

@dcurt1977 dcurt1977 added bug Something isn't working coe-starter-kit CoE Starter Kit issues labels Jul 12, 2024
@Jenefer-Monroe
Copy link
Collaborator

Hello likely you have been impacted by new product behavior that shipped recently around the way the product treats privileged roles (ex Power Platform Admin role, Global Admin role)

While there is a workaround we can put into the kit to fix this directly, we cannot ship it with the kit until the workaround is available in all regions. Hopefully for the July release.

The product change

Here is information about the product feature: Manage admin roles with Microsoft Entra Privileged Identity Management

How to check if this is the case

  1. Validate the user running the flow has direct and permanent assignment to the Power Platform Admin role.
  2. Take one of the target environments in your repro, one of the environments which is failing, and make sure the user running the flow has System Admin security role in that target environment.

How to address and More information

Please see #8119 for a write up on this change.
Included also is a workaround you can do until we can have it natively in the kit.

@dcurt1977
Copy link
Author

System user running the flow has direct and permanent assignment to the Power Platform Admin role. However, user was not assigned System Admin in the target environment, so checking all environments created after May 13, 2024.

@dcurt1977
Copy link
Author

Are there any flows that I should be checking if turned on.

@Jenefer-Monroe
Copy link
Collaborator

Here is how to fix this in the near term until we can ship natively with the kit (hopefully in August)

How to address and More information

Please see #8119 for a write up on this change.
Included also is a workaround you can do until we can have it natively in the kit.

@Jenefer-Monroe
Copy link
Collaborator

closing out as no further action for starter kit team

@dcurt1977
Copy link
Author

After stepping through the CoE Setup and Upgrade Wizard, the Admin | Sync Template v4 (Apps) and Admin | Sync Template v4 (Flows) that previously failed now passed and the environments and flows are now up to date in the Power Platform Admin View Model-driven App.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working coe-starter-kit CoE Starter Kit issues
Projects
Status: Done
Development

No branches or pull requests

2 participants