# Updating the domain name

Nexthink offers the ability to customize the subdomain portion of your domain name used to access your Nexthink tenant to reflect changes such as rebranding, mergers, or acquisitions. Therefore, you can change your domain in the following way:

* Current domain name: `<current-subdomain>.<region>.nexthink.cloud`
* New domain name: `<new-subdomain>.<region>.nexthink.cloud`

To complete this change, coordinate with the Nexthink Support team to request the domain name update, as Nexthink must perform initial configuration changes that will result in a short service downtime.

After Nexthink completes the domain name change in the system, perform the steps in this guide to finalize the update within your own environment and ensure continued access to Nexthink.

## Collector URLs <a href="#important-notice-collector-urls" id="important-notice-collector-urls"></a>

{% hint style="warning" %}
Do not update Collector URLs as part of the domain name change.
{% endhint %}

Nexthink Collectors must continue using the original Collector URL. Changing the Collector URL is not supported and will result in Collector connectivity issues.

The domain name change described in this documentation does not modify Collector URLs. If your organization requires Collectors to use the new domain, do not perform this procedure, as this scenario is unsupported and Collector URL changes are out of scope for Nexthink.

## Before you begin <a href="#before-you-start-prerequisites" id="before-you-start-prerequisites"></a>

Before requesting or performing a domain name change, ensure the following:

* Contact Nexthink Support to schedule the procedure and actions that must be performed by Nexthink.
* Ensure access to a local administrator account. You must be able to log in using a local (non-SSO) admin account to reconfigure SSO after the change.
* Coordinate with your IT or identity provider team. After the domain name change, SSO-based access will not work until the identity provider is reconfigured. During this time, users will not have access to the Nexthink platform.

## Reconfigure SSO in the identity provider after the domain name change

{% stepper %}
{% step %}
Log in to the tenant portal with the local admin account at:

`https://<new-subdomain>.<region>.nexthink.cloud/login`

Example:

`https://yournewname.eu.nexthink.cloud/login`

{% hint style="info" %}
You cannot log in with SSO yet because the URL has changed and it has not yet been configured in the SSO identity provider.
{% endhint %}
{% endstep %}

{% step %}
Navigate to **Administration > Single sign-on**.
{% endstep %}

{% step %}
Download and open the `metadata.xml` file.

<figure><img src="/files/eJN4j6UMvU994sdMIyEs" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Find the `Location` attribute, so that in the next step you can provide it to the team that will update the identity provider configuration.

The `Location` attribute is the only part of the file that has changed from before the URL update:

`https://<subdomain>-login.<region>.nexthink.cloud/sso/saml/<value>`

<figure><img src="/files/H3Rn1ONJHDKpWlCPW0GT" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Request to update the SSO connection

{% hint style="info" %}
Nexthink recommends involving your IT department in this procedure to ensure a smooth transition.
{% endhint %}

{% stepper %}
{% step %}
Create a new task in your service desk application.
{% endstep %}

{% step %}
Provide the new `metadata.xml` file.
{% endstep %}

{% step %}
Explain in the description that the Nexthink application (Service Provider) changed its URL, which makes it necessary to update the SSO location with the new URL in your corporate identity provider.
{% endstep %}

{% step %}
Clarify that only the `Location` changed in the metadata; the application remains the same, that is, the same certificate, audience, and group attribute.
{% endstep %}
{% endstepper %}

#### Example

> The tenant name `tenant_name` changed to `new_tenant_name` (new URL).\
> Please update the Location in the SAML configuration using the attached `metadata.xml` file.
>
> The published application name remains the same: `tenant_name`.

## Ensure correct SSO configuration

{% hint style="warning" %}
Until SSO is reconfigured, users will not be able to access Nexthink using SSO.
{% endhint %}

{% stepper %}
{% step %}
Wait until the IT team confirms they have updated the `Location` in the SAML configuration.
{% endstep %}

{% step %}
Verify that authentication with SSO works by logging in using the URL with the new domain name:

`https://<new-subdomain>.<region>.nexthink.cloud`
{% endstep %}
{% endstepper %}

## Update the subscription configuration in Zoom App Marketplace

Perform the following steps if you use Collaboration Experience with Zoom:

{% stepper %}
{% step %}
Open the configured application in the [Zoom App Marketplace](https://marketplace.zoom.us/).
{% endstep %}

{% step %}
Go to the **Feature** section.
{% endstep %}

{% step %}
Use the toggle to enable **Event Subscriptions** and select **+ Add Event Subscription**.
{% endstep %}

{% step %}
Enter the **Subscription name**.
{% endstep %}

{% step %}
Paste the following URL for the **Event notification endpoint URL**: `{{eventNotificationEndpointURL}}`
{% endstep %}

{% step %}
Click **Validate**.
{% endstep %}

{% step %}
Click **Add Events**.
{% endstep %}

{% step %}
From the **Meeting** section, select the **End Meeting** option and click **Done**. This ensures Zoom sends out information when ending a meeting.
{% endstep %}

{% step %}
**Save** the event subscription.
{% endstep %}
{% endstepper %}

## URL behavior after the domain name change

After the domain name change:

* Old URLs continue to work to ensure backward compatibility.
* New URLs are active and should be used going forward.

Update the following after the domain name change:

* Bookmarks to use the new domain.
* API integrations and scripts to reference the new domain.


---

# Agent Instructions: 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:

```
GET https://docs.nexthink.com/platform/configuring_nexthink/setting-up-the-platform-instance/updating-the-domain-name.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.