Migrating from a vanity URL to a custom URLIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } An instance is configured with a vanity URL and needs to be migrated to a custom URL. This process requires both customer-performed configuration steps and internal actions completed by ServiceNow Support and Cloud Operations teams. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Step 1 — Activate the Custom URL plugin Role required: admin Activate the Custom URL plugin (com.snc.customurl) to enable custom URLs on the instance. Navigate to System Definition > Plugins.Find and select the Custom URL plugin. Note: Do not select the Custom URL - Internal plugin. This is an internal component for scripted custom URL APIs. On the Custom URL record, select the Activate/Repair related link.In the Plugin Activation window, select Activate.When the Plugin Activation window reopens with a confirmation message, select Close & Reload Form.In the Plugin Files related list, find the following property and update the setting value: OptionDescriptionglide.customurl.enabledTo enable custom URLs, set the value to True. By default, this property is set to False, which means a custom URL cannot be associated. To disable this feature, set this property back to False. 5. Select Update. Step 2 — Create a new custom URL Role required: admin Important: The custom URL must be the same as the existing vanity URL. The domain must be purchased or registered before adding it to the instance. Navigate to Custom URL.Select New to associate a new domain name.Choose a custom URL to set as the instance URL.Fill in the following fields: OptionDescriptionDomain NameFully qualified domain name (FQDN) of the custom URL. For example, if the custom URL is https://servicenow..com, enter servicenow..com as the FQDN.Is Instance URLSelecting this enables the custom URL for all outbound URLs. Only one active custom URL can be the instance URL. To enable this setting, select the Set as Instance URL button on an active custom URL record. This activates the chosen custom URL and removes any previously set custom URL.StatusStatus of the custom URL record. Once the status shows as Active, the custom URL is provisioned and ready to use.[Optional] Service PortalChoose the service portal to redirect users when they access the instance using the custom URL. 5. A custom URL activates within six hours. Polling for custom URL job completion occurs every 30 minutes. Note: A poll button is available for manual polling of an in-progress custom URL job. Step 3 — Notify Support to raise the change record Once Step 2 is complete, notify Support so a change can be raised for the Cloud Operations System Administrators team to remove the vanity URL configuration. Use the Normal change request template [SA] Disable Vanity URL Configuration to create the record. The change record instructs the Cloud Operations System Administrators team to remove the vanity URL configuration. This change activity finalises the transition. Step 4 — Support will validate the custom URL configuration Once the Cloud Operations team completes the change record, run the following command to verify the custom URL configuration is active on the F5 device. Run the following command on the local machine, replacing with the actual custom URL: echo | openssl s_client -servername <custom-url> -connect <custom-url>:443 2>/dev/null | openssl x509 -noout -dates -subject -issuer If the issuer returned is Let's Encrypt, the custom URL configuration is confirmed as active. Expected output format: notBefore=<date> notAfter=<date> subject= /CN=<custom-url> issuer= /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3