Organizations own and manage several domains with different URLs and email addresses. For instance, a company named Zylker could have domains such as zylker.com, zylker.org, or zylkerservices.com. ServiceDesk Plus Cloud enables you to add and verify all the domains associated with your organization in the ESM Directory. The added domains can be verified from the Domain Provider console or by hosting a HTML file with verified credentials.
To add users to any domain, you must verify the validity of the domain and its users. Domain verification is also necessary to confirm your ownership of the domain and to customize the domain per your requirements.
Users added from a verified domain will not receive an invitation email. Additionally, the application language for users imported from verified domains will be auto-configured based on the department's site they are assigned to.
Role Required: OrgAdmin
Go to ESM Directory > Custom Domains.
Click New Domain, add your domain name to the pop-up displayed, and click Save.

The Verified Domains home page will now list your domain. In the status column, select Click to verify.
In the Verify Domain pop-up window, select the verification method: CNAME or HTML File Method.
CNAME record type in the DNS Management page. You will need access to the DNS records to verify via CNAME method. Depending on your Internet Service Provider, the CNAME verification can take a while to be completed.

After an hour, click the Verify button. Your domain will be verified.
Refer to the following video for an illustration on how to verify using the CNAME method:
You can also use the HTML File method where you only need to host the HTML page containing the verification code. After you host the HTML page, you can verify the domain in ServiceDesk Plus Cloud promptly.

Announcement for Existing Users who employed Custom URL to their ServiceDesk Plus Cloud Setups
For users who have already saved a custom URL without a proper CNAME, the verification will fail following the feature upgrade on 27 August 2021. The custom URL will be removed and the application will revert to the default URL. Users are required to redo verification to continue using their own custom URL.
If the CNAME for your sub-domain is configured and verified already, SSL certification will be auto-applied for your custom domain if it is not applied already.
You can now access ServiceDesk Plus Cloud services/instances by using custom domains. A custom domain will help you access a specific service desk instance through a URL that is part of your organization's domain. You can create multiple domains and associate them with specific help desk instances.
Before you set up a custom URL, configure the CNAME of your sub-domain as explained below.
For example: If you have provided your sub-domain is helpdesk.zylker.com and your data center is configured as USA, your sub-domain should point to customer-sdpondemand.manageengine.com.
Represent your brand name in place of the default URL by setting up your custom domain. Instead of the default URL, your users will now access the services via the domain you have configured.
To create a new customized service URL for accessing ServiceDesk Plus Cloud,
1. Go to ESM Directory > Custom Service URLs > New Service URL.

1. Enter a sub domain name and select the verified domain from the drop-down.
2. Click Verify & Save.

Once you have added and verified domains, you can associate them with instances.
To do that,
Go to Service Desk Instances in the ESM Directory.
Choose an instance and click Edit Instance.
Under the custom URL field, you can select the domain you want to associate with this instance. All verified domains will be listed in this field.

If the default instance is not marked, then the users' own default setup will be followed.
ServiceDesk Plus Cloud automatically verifies if the CNAME of your sub-domain points to the application. If the verification is completed successfully, you will be able to use your custom URL to access ServiceDesk Plus Cloud immediately, depending on your data center configuration. If your data center has mandated SSL certification, you can use your custom URL after an SSL certificate is applied.
Once created, custom URLs cannot be edited further. Users can remove the custom URL and add a new URL, if needed.
Do not remove the CNAME entry even after verification as it will be used for service redirection. Without this entry, the service cannot be reached using a custom domain.
Once created, custom URLs cannot be edited further. Users can remove the custom URL and add a new URL, if needed.
SSL Certificate will be automatically applied to secure your domain. The process for SSL certification is initiated immediately after your custom domain is created. Typically, custom domains are validated and SSL certification will be completed in 1 business day.
You can track your SSL Certification status from the ESM Directory > Organization URLs if needed.

If you happen to change your domain, then the following impact can happen depending on how you are going to use the old and new one.
1. Verified domain. You may need to add the new domain as verified, mark as default if necessary.
2. If your user's email in the old domain is retained and the new will be
added as alternate/another email, then make the necessary adjustments to Sync flow (Azure/Provisioning tool) for Email and Alternate email field mapping.
3. Make sure that emails are mapped appropriately.
4. For users who are on SAML , the claim ID is expected on the email of the user
which is confirmed /verified in Zoho. Make sure you have followed instructions up to the 3rd point, as then you can only return the new email as claim id or you can
keep the existing old email as claim id.
5. If you are changing the domain for service access, then make sure to add the domain with a subdomain in ESM Directory > Organization URLs. You will need to do the CName mapping. SSL can take about 48hrs. So plan accordingly.
6. If you are changing your IDP access url, then you need to regenerate the certificate and update the login/logout url for saml configuration and
update the new certificate.