> 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-custom-role-creation-fails.md).

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

If onboarding stops with:

```
Unable to create custom role at tenant scope. Please enable 'Custom role
definitions' in Entra ID (Roles and administrators > Settings)...
```

your tenant has custom role definitions disabled. Onboarding creates an Archera custom role carrying read-only billing and usage permissions, and it cannot do that while the setting is off.

## How to Fix This

**Entra ID → Roles and administrators → Settings → Custom role definitions → Enable**

Wait **two to three minutes** for the change to propagate, then re-authorize Archera in Step 1 and check status again. The setting is tenant-wide and only needs enabling once.

This is a different failure from the role *assignment* error, which has its own cause and fix.

## Related Resources

* [Why Does Onboarding Fail With "Unable to Assign the Custom Role at Tenant Scope"?](https://docs.archera.ai/help-center/azure-faq/onboarding-tenant-role-assignment-fails.md)
* [Prerequisite Checklist](https://docs.archera.ai/help-center/azure-onboarding/technical-onboarding/prerequisite-checklist.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-custom-role-creation-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.
