> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/es/troubleshooting/how-to-change-the-tenant-name.md).

# Cómo cambiar el nombre del Tenant

Hay una opción para cambiar el nombre del tenant.

Con KONNEKT versión 2.10, el comportamiento ha cambiado en cuanto a lo que KONNEKT denomina nombre de tenant. Al habilitar "[OAuth mejorado](/es/configuration/system-settings/enhanced-authentication.md)" esta configuración surtirá efecto.

Todas las versiones de KONNEKT 2.9.1 y anteriores utilizan el nombre de tenant inicial. Al habilitar la configuración "Enhanced OAuth", este comportamiento cambiará. En su lugar, mostrará el nombre de tenant predeterminado que puede configurarse mediante Microsoft Admin Center.

{% hint style="info" %}
Surte efecto con KONNEKT versión 2.10 y posteriores
{% endhint %}

Los pasos que deben realizar los administradores o usuarios son:

* Habilitar "Enhanced OAuth" mediante una directiva de GPO o Intune
* Aplicar el nuevo registro de la aplicación en Azure
* eliminar los datos de usuario anteriores del registro de usuarios

{% hint style="warning" %}
¡La ruta UNC cambiará después de habilitar esta configuración!

Por ejemplo, si hay referencias entre archivos o carpetas, ¡estos vínculos se romperán!
{% endhint %}


---

# 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.konnekt.io/es/troubleshooting/how-to-change-the-tenant-name.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.