Hello,
I have a requirement that when P1 INC created or updated to P1, I need to create Teams channel. I have already done most of the requirements, but the channels are getting created under my username instead of service account.
I am using the flow designer Microsoft Teams Graph actions to create channels and post INC details
and Channels are getting created on the correct Teams but even though I updated the "User ID" field to the service account (MS userid), but still channels are created under my username.
Does anyone have any idea how to fix this issue?
Thanks
Could you be a little more explicit about what the 'correct access' is? We are seeing the same issue using the "PPM Collaboration" application built on the MS Teams Spoke. For example, after updating an older version, we noticed that the "Create Teams Channel" subflow that is called by "PPMCollaborationHandler" script include is trying to use the old action now labeled "Create Team (Deprecated)" instead of the new version "Create Team".
What we see is that the "Create Office 365 Group" works fine to create the group and set the owner, but then the "Create Team" tries to change the member, guest, messaging, etc, settings and fails because the MS Teams application logging in to change the group is not the owner of the group.
The odder thing is that it does seem to work when someone that is an Azure admin tries, which is bizarre. It's like there is some extra interaction beyond the REST call using the MS Teams Spoke token that involves the active user, but I don't see any reflection of that in the code.
That extra oddity aside, the question seems to be: Is there an Azure application permission that can be added that will allow that application to change the desired group settings (to make it a Teams group) without the requester being the owner of that group?
