> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-microsoft-entra-id/good-to-know-about-entra-id.md).

# 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](/tutorials/guides.md), 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](/tutorials/guides/how-to-use-microsoft-entra-id/how-to-find-the-ids-in-entra-id.md#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](/tutorials/guides/how-to-use-microsoft-entra-id/how-to-find-the-ids-in-entra-id.md#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](/tutorials/guides/how-to-use-microsoft-entra-id/how-to-set-up-an-entra-id-connection.md#two-optional-policies).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.struct.com/tutorials/guides/how-to-use-microsoft-entra-id/good-to-know-about-entra-id.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.