Good to know about Entra ID

Behaviours that follow from Struct reading group membership out of the sign-in token, and the ones that surprise people.

These behaviours follow from the model described in How to use Microsoft Entra ID, and they are the ones that surprise people.

Changes take effect at next sign-in. Struct reads membership from the sign-in token, so adding or removing someone in Entra reaches Struct when they next sign in, not immediately. If someone must lose access at once, remove them in Struct as well, or disable their Entra account.

Security groups only. Struct receives security groups only. A Microsoft 365 group or distribution list will never match a mapping. See Group Object ID.

Nested membership is included. Membership is resolved through nesting, so a member of a child group matches a mapping on the parent. See Group Object ID.

Very large numbers of groups. If a user belongs to a very large number of groups, Entra omits the list from the token rather than truncating it. Struct treats this as unknown and leaves that user's access exactly as it is, rather than concluding they are in no groups. Nobody is removed because of it.

Guest accounts. Guests in your directory are treated like any other user. If they are in a mapped group, the mapping applies to them.

Several connections can coexist. You can have more than one connection, one per directory. This is useful after an acquisition, or for a separate test directory.

Invited users and Entra users coexist. Someone invited to Struct by e-mail keeps their own roles and user groups even after a connection is added, unless a mapping covers them or you turn on one of the policies in Two optional policies.