Run only users won't save

[mrQ]

Dear community

I created a Flow that is triggering a child flow. The child flow is using a Microsoft Teams connection. In the child flow, under "run only users" I've selected "Use this connection".

In the parent flow, I wanted to change the "Run only users" to a security group. Strangely, some of the security groups can't be saved. Meaning, if I type in one of the security groups (let's call it "sec-group-A") it almost seems to work - I can select it, add it to the list and can even save it. However, after I've saved it just isn't there anymore once I reopen "Run only users". Hence, it somehow didn't save. 

Another security group can be saved though (let's call it "sec-group-B") and I can't figure out why.

I already tried to add "sec-group-A" and "sec-group-B" to the child flow under "Run only users" and it seems the behaviour is the same. sec-group-B is being saved, while sec-group-A just won't.

Does anyone know how to solve this? 

Thank you and kind regards,

[mrQ · Accepted solution]

After some more research I found the cause for this issue:

sec-group-B is a security group of type "assigned" while sec-group-A is a group of type "dynamic". I was then wondering whether dynamic M365 groups would be allowed and indeed they work! 

So, whenever you'd like to share a flow with a dynamic group, make sure its a M365 and not a security group.