[CoE Starter Kit - Issue] Admin | Add Maker To Group -> BadRequest

[lucasubieta]

Does this question already exist in our backlog?

• [x] I have checked and confirm this is a new question.

What is your question?

Hi there!,

I'm having problems with this flow -> statusCode 400

The user is the owner of the makers group, so I shouldn't have any problems. Any suggestions?

Thanks a lot! 😊

What solution are you experiencing the issue with?

None

What solution version are you using?

July 24

What app or flow are you having the issue with?

Admin | Add Maker To Group

What method are you using to get inventory and telemetry?

None

[Jenefer-Monroe]

My guess is that the HTTP with Microsoft Entra ID (preauthorized) connection is broken or misconfigured.

Please go to connections and make sure the connection for these is as follows (or your tenant equivalent if you are not a commercial tenant: https://graph.microsoft.com/

Sometimes the product creates one of these connected to the envt and this will not work.

[lucasubieta]

Hi Jenefer,

Thanks a lot for your reply.

I just reconfigured the 'HTTP with Microsoft Entra ID' and 'Office 365 Groups' connectors. I also checked the Office 365 app registration in Azure (not sure if it’s related, but just in case), and it’s all set but still not working :(

[silvafr1]

Hello, Isn´t because of the new Microsoft change?

https://admin.microsoft.com/AdminPortal/home#/MessageCenter/:/messages/MC918447?MCLinkSource=DigestMail https://learn.microsoft.com/en-us/connectors/webcontents/#authorize-the-connector-to-act-on-behalf-of-a-signed-in-user

Thank you!

[Jenefer-Monroe]

No, that change has been delayed while they continue to iterate on the feature. Also, oops I hadn't had my coffee yet :) That is the group connector not the preauth one lol.

This call uses an environment variable, lets go make sure its correctly configured. Note that it needs to be the group GUID, not its display name or email.

[lucasubieta]

haha! i really appreaciate your work Jenefer 💯, I checked the group connector as well and it's ok, also reconfigured it. Regarding the variable, i would say that it's ok, just doube check the id as well..

[Jenefer-Monroe]

great can you please restart the flow and resubmit the failure? sometimes flows cache env vars.

[Jenefer-Monroe]

also please double check to make sure your connections are healthy

[lucasubieta]

Reconnected all the connectors, still the same..

[lucasubieta]

i checked on the flow run that is taking the correct env var. I also tried to disable and enable it again, still the same

[Jenefer-Monroe]

What is the specific error message you get from this call?

And can you call this action from a separate flow? We arent doing anything special here, just calling List Group Members

[lucasubieta]

Hi! I just tried a simple flow with the "List group members" action pointing to the same group, and it worked fine.

This is the error I'm getting from the CoE flow. I even replaced the action in the flow with the same action, just in case, but I'm still seeing the same error;

Thanks!,

[lucasubieta]

Hi again! I just tried the flow again, replacing the "group variable" with the group itself, and it worked fine. So the issue must be with the "makers group variable." I checked, and it’s configured properly, so I’m not sure what could be causing this.

If I leave it as it is, with the modified flow, I’ll need to remember to change it again whenever I update the solution, right? Since it will be replaced with the original flow.

Thanks

[Jenefer-Monroe]

You're right you'll have an unmanaged layer. Lets try to fix it one more time. My guess is that it had a space at the beginning or end or something like that. I suggest you do the following:

Go to default solution in the CoE Environment > Environment Variables > find this env var > delete the current value > add it again