> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector/troubleshooting.md).

# Troubleshooting

Most problems with this connector come from one of a handful of causes. These are the ones worth recognising on sight.

#### "Insufficient privileges to complete the operation"

The connection was authorised before the component you are now using existed, so its scope is missing from the token.

Disconnect the connection in the flow, sign in again and confirm admin consent. The new scopes are added to the token during that sign-in, not retroactively.

#### A license assignment fails

The user has no usage location. Microsoft refuses to assign licenses to accounts without one.

Set it with **Update User** using a two-letter country code, then run the assignment again. If this happens inside an onboarding flow, set the usage location when the account is created rather than fixing it afterwards.

#### A secret value or access pass is gone

Both are issued exactly once, at the moment of creation, and cannot be read back afterwards. This is Microsoft's behaviour, not a connector limitation.

Process the value inside the same flow run — write it to a password manager or key vault, or send it on immediately. If the value is lost, the only route is to create a new one.

#### A SAML certificate was not reported as expiring

SAML signing certificates live on the enterprise application, not on the app registration, so they are outside the default check.

Turn on the option to include service principals. Without it, the certificates that break single sign-on are the ones you will not hear about.

#### A monitor never reports findings

This is the expected result when there is nothing wrong. The findings output only fires when something needs attention.

If you want positive confirmation that the check is running, connect the **ok** output to a log entry or a heartbeat message.

#### A trigger appears to do nothing

First check the configured interval — a daily check will not react within minutes.

Then look at the flow logs for the trigger. If there are no entries at all, the flow or the connection is the problem rather than the trigger: restart the flow and verify the connection.


---

# 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://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector/troubleshooting.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.