This article explains a common issue where a user is successfully added to a Microsoft 365 group via an integration but does not yet appear as a member in the associated Microsoft Teams.
Symptom
A user has been added to a Microsoft 365 group via eAdm eFeide. You can see the user as a member of the group in the Azure portal, but they are not visible within the corresponding Teams instance and cannot access its resources.
Explanation: A delay is normal
This is expected behavior and does not indicate an integration failure.
The synchronization of members from a Microsoft 365 group to its associated Team is an asynchronous background process managed entirely by Microsoft. When a user is added to the group, there is often a delay before they become a member of the Team itself.
Microsoft's Official Sync Process
According to Microsoft's official documentation, the membership sync process has two key requirements:
-
Time Delay: It may take 24 hours or more for membership changes in a Microsoft 365 group to sync with Teams.
-
Activity Requirement: The background sync process is triggered only if at least one user in the team (either an owner or a member) is active in the Teams desktop client. Simply having the application running counts as activity; the user does not need to navigate to the specific team being updated.
Note: The Teams mobile clients do not trigger the membership sync. To ensure the process runs, at least one user from the team must be using the desktop or web client.