microsoft / coe-starter-kit

Other
736 stars 215 forks source link

Cannot escalate permissions for user on D4T Environments #8580

Open Jenefer-Monroe opened 1 month ago

Jenefer-Monroe commented 1 month ago

Does this bug already exist in our backlog?

Describe the issue

Attempting to escalate permissions for D4T environment fails whereas this worked earlier and recently (~5 days ago) in our testing of this preview feature. Cannot escalate permissions for user on D4T Environments.

Expected Behavior

This did work earlier in our testing of this feature

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.33

What app or flow are you having the issue with?

PIM Escalation Solution

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response

ramontebar commented 1 month ago

Hi, we are also getting an error with Teams environments when running the 'PIM Workaround Flow'

Error message: Could not find a property named 'address1_country' on type 'Microsoft.Dynamics.CRM.systemuser'.

coekit_error_on_pim-workaround_flow_teams_environments_2407040735

bilodeauju commented 1 month ago

I was getting the same error message yesterday, but today the issue appears to have resolved itself.

ramontebar commented 1 month ago

Previous error is not happening today, but now we are getting a new error in Teams environments:

{
    "error": {
        "code": 401,
        "message": "The response is not in a JSON format.",
        "innerError": "Cannot read server response."
    }
}
Jenefer-Monroe commented 1 month ago

This stopped repro-ing for me yesterday as well. Yeah! Let's keep open a few days to make sure it stays away,.

@ramontebar, I've seen that error before repro intermittently for random environments. D4T and non D4T environments. It would pass the next day when this happens.

We will write this into the Driver flow for an upcoming release such that it will retry and then let you know about the failure, without stopping the Driver flow from completing image image