Custom URLs association to your instance
-
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- Platform Security
You can enable your ServiceNow instance to be accessible from a company-branded or custom URL.
Custom URL overview
You can use custom URL to enable ServiceNow instance to be accessible from one or more company-branded or custom URLs.
Custom URLs can be associated with specific portal. For example, admin can define http://support.acme.com
for CSM portal and http://hr.acme.com
for HR portal. In such situation there is a need
to redirect users to different IdPs for authentication on the basis of the custom URL that users are accessing.
- Do not create a custom URL with more than 100 domains per instance.
- You must delete custom URL record from ServiceNow instance first and then delete any Domain Name Server (DNS) entries from the DNS server.
- Any deletion of DNS entry from DNS server prior to deletion of custom URL record from ServiceNow instance would result in blocking the deletion of other corresponding custom URL records from ServiceNow.
From Tokyo, you can allow users to auto-redirect to specified IdPs defined at the custom URL record.
Example URLs | Usage |
---|---|
https://acme.service-now.com |
The initial domain name for Acme that came with the ServiceNow instance. |
https://support.acme.com |
A custom URL that associates to your ServiceNow instance. This URL is referred to as an alias (CNAME) of the initial domain name. |
https://US-support.acme.com |
A secondary custom URL that associates to a service portal on your instance. Your instance can support multiple custom URLs to the same service portal. |
Custom URL considerations outside of your instance
Configuration items | Description |
---|---|
Set the CNAME with the provider | The CNAME record must be set as the ServiceNow instance URL. |
Determine your dedicated VIP status | The status of VIP. |