Forum Discussion
Teams Aadsync adding and deleting users - known issue but no official documentation
Found the action that triggers that information.
If you want to add the permission to a library but you go with this entry point:
Then you add some users as "members" - they seem to be added to the AAD group but not yet to Teams.
Short time later:
Mystery solved 🙂 Thanks for your directions
Well. Not really. I already had a look into this.
We have AAD Connect - we get the Office 365 Group synced to our AD but this is a one way sync. So there is no adding to the Azure AD group. (Well users find ways... but normally we teach them to use Teams for this)
The owners added a library to the underlying SharePoint page and then tried to add a security group to that library by breaking inheritance.
It must have to do something with that action. I am trying to reverse engineer with the audit log (would be easier if it could be scoped to a certain Team though)
Found the action that triggers that information.
If you want to add the permission to a library but you go with this entry point:
Then you add some users as "members" - they seem to be added to the AAD group but not yet to Teams.
Short time later:
Mystery solved 🙂 Thanks for your directions
- Hi, great that you found out your trigger. But the article do mention it.
”Typically, the changes flowing through the pipeline are made to groups via admin centers, Exchange Online, SharePoint Online, or PowerShell modules.”
Before the Teams AadSync was introduced these changes was displayed as ”random owner has removed/added bla bla”. You’ve probably noticed that.
