Instance scan findings

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Instance Scan Findings

    After completing an instance scan, you can review the findings in the Scan Result form under the Scan Findings related list. This report includes various issues that may affect the functionality and configuration of your ServiceNow instance regarding Microsoft Exchange Online and calendar synchronization.

    Show full answer Show less

    Key Features

    • Connection and Credential Issues: Problems with finding, associating, or validating the connection and credential aliases can lead to connection failures.
    • OAuth Configuration: Errors in OAuth token generation, expired tokens, or mismatched scopes and grant types can hinder secure communication.
    • Application Registry Errors: Invalid URLs or missing OAuth Entity Profiles can disrupt application integrations.
    • Subscription and Synchronization Problems: Inactive calendar providers, expired subscriptions, or configuration inconsistencies can affect calendar synchronization functionalities.

    Key Outcomes

    To address the findings, it is essential to:

    • Ensure all connection and credential aliases are properly configured and active.
    • Generate a new OAuth token if the current one has expired.
    • Validate and correct any URLs in the Application Registry.
    • Check synchronization settings and ensure that subscriptions are active and correctly linked to the proper configurations.

    Refer to Microsoft Exchange Online documentation for prerequisites and implementation steps to resolve these issues effectively.

    After the instance scan completes, on the Scan Result form, review the findings in the Scan Findings related list.

    Scan findings

    The following findings are reported in the scan report:
    • Could not find the sn_ex_online_spke.Microsoft_Exchange_Online Connection and credential alias.
    • The Connection & credential alias specified in the Override alias is not a child alias to the sn_ex_online_spke.Microsoft_Exchange_Online Connection and credential alias.
    • There are multiple/no connections associated with the ' + selectedAlias.getValue('name') + ' Connection and credential alias.
    • There are multiple/no connection attributes associated with ' + selectedAlias.getValue('name') + ' Connection and credential alias.
    • Incorrect 'Connection URL' specified in the " + selectedAlias.getValue('name') + " Connection and credential alias."
    • OAuth provider associated with the OAuth Entity Scope - ' + scope + ' is not same as the one associated with OAuth Entity Profile of this scope.
    • The OAuth Scope - ' + scopesExpected[i] + ' must be associated with the grant type ' + grantType + '.
    • The Default grant type of the OAuth provider must be same as the Grant type of the OAuth Entity Profile.'
    • OAuth Token has expired.
    • Please generate an OAuth Token.
    • Invalid token URL associated with Application Registry - ' + applicationRegistryGr.getValue('name') + '.
    • Invalid authorization URL associated with Application Registry - ' + applicationRegistryGr.getValue('name') + '.
    • Invalid redirect URL associated with Application Registry - ' + applicationRegistryGr.getValue('name') + '.
    • There is no OAuth Entity Profile associated with the credential - ' + credentialGr.getValue('name') + '.
    • There is no credential associated with the connection - ' + connectionGr.getValue('name') + '.
    • There is no active credential associated with the connection - ' + connectionGr.getValue('name') + '.
    • Invalid Credential record associated with connection - ' + connectionGr.getValue('name') + '.
    • If the grant type of the connection (linked with provider) is set as Authorization Code, the provider must have Strict mode enabled with a valid Strict mode email.
    • Synchronization is not configured - could not find an active provider.
    • There are multiple subscriptions associated with this resource.
    • Calendar provider associated with this Rsv Sync Configuration is inactive.
    • Could not find an email with this Rsv Sync configuration.
    • The Rsv Sync configuration email must be same as the email specified in the 'Email' field of the location record.
    • The same email is associated with a different Rsv sync configuration.
    • The Subscription has expired.
    • The Subscription status is ' + status + '.
    • Invalid Subscription.
    • Could not find a subscription for this Rsv Sync Configuration.
    To fix a finding, refer to the following: