> For the complete documentation index, see [llms.txt](https://docs.omnata.com/omnata-product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/microsoft-entra-id.md).

# Microsoft Entra ID

Microsoft Entra ID is an integrated cloud identity and access solution, and a leader in the market for managing directories, enabling access to applications, and protecting identities. Bring in your users from Microsoft Entra ID to Omnata to integrate a master user record across systems.

### Authentication

#### OAuth (Microsoft Entra ID)

Visit the [Microsoft Docs](https://learn.microsoft.com/en-us/graph/auth-register-app-v2?view=graph-rest-1.0) for Setting up Microsoft Entra ID based authentication

### Setting up a new connection

When setting up a new connection you have the following option for authentication:

* OAuth (Microsoft Entra - Plugin Managed Tokens)

Microsoft Graph application permissions required

| Permission             | Required for                                                                                                                            |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| `User.Read.All`        | `users`, `user_identities`, `user_assigned_licenses`, `user_assigned_plans`, `user_provisioned_plans`, `user_license_assignment_states` |
| `Group.Read.All`       | `groups`                                                                                                                                |
| `GroupMember.Read.All` | `user_group_memberships`                                                                                                                |

On the Omnata connection form, select **OAuth (Microsoft Entra - Plugin Managed Tokens)** and provide:

| Field         | Value                                                         |
| ------------- | ------------------------------------------------------------- |
| Tenant ID     | The Directory (tenant) ID from your Entra app registration.   |
| Client ID     | The Application (client) ID from your Entra app registration. |
| Client Secret | The client secret value you created in Step 2 above.          |

### Inbound Syncs

All streams use **Full Refresh** sync only. There is no Microsoft Graph delta/change-feed for these objects that the plugin currently consumes, so each run re-pulls the full directory. The plugin is designed for landing into Snowflake tables that downstream models can historise into SCD Type 2.

<table><thead><tr><th>Stream</th><th>Sync strategies</th><th>Notes</th><th data-hidden>Primary key</th></tr></thead><tbody><tr><td><code>users</code></td><td>Full Refresh</td><td>All users in the tenant. Source: <code>/users</code>.</td><td><code>id</code></td></tr><tr><td><code>user_identities</code></td><td>Full Refresh</td><td>Federation identities attached to each user (e.g. external accounts).</td><td>composite <code>userId</code> + <code>issuerAssignedId</code></td></tr><tr><td><code>user_assigned_licenses</code></td><td>Full Refresh</td><td>License details per user. Source: <code>/users/{id}/licenseDetails</code>.</td><td>composite <code>userId</code> + <code>id</code> + <code>skuId</code></td></tr><tr><td><code>user_assigned_plans</code></td><td>Full Refresh</td><td>Service plans currently assigned to each user.</td><td>composite <code>userId</code> + <code>servicePlanId</code></td></tr><tr><td><code>user_provisioned_plans</code></td><td>Full Refresh</td><td>Service plans provisioned for each user.</td><td>composite <code>userId</code> + <code>service</code></td></tr><tr><td><code>user_license_assignment_states</code></td><td>Full Refresh</td><td>The active/error/disabled state of each license assignment per user.</td><td>composite <code>userId</code> + <code>skuId</code></td></tr><tr><td><code>groups</code></td><td>Full Refresh</td><td>All groups in the tenant. Source: <code>/groups</code>.</td><td><code>id</code></td></tr><tr><td><code>user_group_memberships</code></td><td>Full Refresh</td><td>Transitive group membership per user. Source: <code>/users/{id}/transitiveMemberOf</code>.</td><td>composite <code>userId</code> + <code>id</code></td></tr></tbody></table>

### Outbound Syncs

There is currently no outbound direction support for this App, but please [contact us](https://omnata.com/contact-us) and we can add features for your use case.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/microsoft-entra-id.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.