What updates are needed for Multi-Provider SSO when an instance is migrated to SPPSummaryWhen an instance is migrated to servicenowcloud.com.au from service-now.com or when a custom URL is implemented for the first time, the Service Provider information for Single-Sign-On record has to be updated accordingly. The Identity Provider record in Multi-Provider SSO defines not only the IDP information, but also the Service Provider (ServiceNow) information. If this information changes due to an instance move to a different domain (not datacenter) or implementation of a custom url, the updates have to be performed on both sides - ServiceNow and the IDP, or users will be unable to log in via SSO. InstructionsIn the Identity Provider record, the items to change are: ServiceNow HomepageEntity ID / IssuerAudience URI and if e-Signature is used, also the URL containing consumer.do The change will be to replace any occurrence of service-now.com with servicenowcloud.com.au, or the old instance URL with the new custom URL. After the record is saved, Test Connection if prompted. The IDP record does not have to be deactivated for the domain name change. In case something goes wrong, you can do these steps: With debugging turned on, if you go within the same browser tab that failed your login and go to "Node Log File Browser" in your module list and search for message=SAML (case sensitive) for the timeframe of the failed login, you will find the exact error message and can address the root cause.