search

microsoft / coe-starter-kit

Other
720 stars 211 forks source link

[CoE Starter Kit - BUG] Admin | Gather Tenant SRs #8567

Open Alyson95170 opened 2 days ago

Alyson95170 commented 2 days ago

Does this bug already exist in our backlog?

Describe the issue

Hi, I have noticed Admin | Gather Tenant SRs is failing due to - RetrievePrivilegeForUser: The user with id e46ee-***** has not been assigned any roles. They need a role with the prvReadBusinessUnit privilege. The account has System Admin within the environment the CoE is installed in, is there something I have missed?

Expected Behavior

This had no issues running prior to the upgrade

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.32

What app or flow are you having the issue with?

Admin | Gather Tenant SRs

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

AB#3707

eeuo commented 2 days ago

I have the same issue. The flow fails at the point "Get Parent BU for ID". In my situation it fails on 5 out of 138 environments with different user ids.

image

Alyson95170 commented 2 days ago

I have just checked the environment and the service account running the CoE was not listed as system admin in the environment it was trying to gather the information from, I have added this now and re-submitted and now running successful .

eeuo commented 2 days ago

I got this also working after installing this workaround solution "PIMWorkaroundSolution_1_0_0_3_managed.zip" and running the flow in it. After that I manually run the "Admin | Gather Tenant SRs" flow and it succeeded.

The instructions to workaround can be found here: https://github.com/microsoft/coe-starter-kit/issues/8119

Jenefer-Monroe commented 2 days ago

Thank you folks. Yes the way privileged accounts works has changed in the product and so you need to explicitly grant the permissions to the environments now. As explained in https://github.com/microsoft/coe-starter-kit/issues/8119 we will be putting this in the kit directly but cannot quite yet, we need the action and connector to be supported in all regions before we can do that. Until then you will need to use the solution provided in that bug to work around this change.