> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/azure-faq/onboarding-tenant-role-assignment-fails.md).

# Why Does Onboarding Fail With "Unable to Assign the Custom Role at Tenant Scope"?

If onboarding stops with:

```
Unable to assign the custom role at tenant scope. Grant 'User Access
Administrator' at the root management group...
```

the account running onboarding lacks User Access Administrator at the **root management group**. Several of our role assignments are scoped at the tenant root, so Owner or User Access Administrator on a subscription is not enough.

## How to Fix This

1. **Microsoft Entra ID → Overview → Properties → Access management for Azure resources → Yes**, then save. This requires Global Administrator.
2. Sign out and back in so the new role takes effect.
3. Re-authorize Archera and re-run onboarding.

Turn the toggle back off once onboarding completes. If your tenant grants User Access Administrator at the root management group another way, that works equally well and no toggle is needed.

## If It Worked Before and Stopped

An integration that was healthy and later loses access has usually had its role assignments removed by an Azure Policy or by a Privileged Identity Management (PIM) expiry. Re-running onboarding restores them.

## Related Resources

* [Why Does Onboarding Fail With "Unable to Create Custom Role at Tenant Scope"?](https://docs.archera.ai/help-center/azure-faq/onboarding-custom-role-creation-fails.md)
* [Required Permissions](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/required-permissions.md)


---

# 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.archera.ai/help-center/azure-faq/onboarding-tenant-role-assignment-fails.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.
