--- sourceDocument: Australia Employee Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/employee-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Employee Service Management ft:clusterId : - emplsm bundleId : - emplsm workflow : - Employee --- # Instance scan findings # Instance scan findings {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 This document outlines the common findings reported after completing an instance scan for ServiceNow integrations, specifically related to Microsoft Exchange Online and calendar synchronization configurations. Reviewing these scan findings on the Scan Result form helps ensure your connections, credentials, OAuth configurations, and synchronization setups are correctly implemented and active. Show full answer Show less ## Key Findings and Their Implications * **Connection and Credential Alias Issues:** Errors include missing aliases, incorrect alias hierarchies, multiple or absent connections or attributes, and incorrect connection URLs, all of which can disrupt integration with Microsoft Exchange Online. * **OAuth Configuration Problems:** Common findings involve mismatches between OAuth providers and entity profiles, missing or expired OAuth tokens, invalid token, authorization, or redirect URLs, and missing OAuth entity profiles tied to credentials. These issues prevent secure authentication and authorization. * **Credential and Connection Problems:** Missing, inactive, or invalid credentials linked to connections can cause failures in synchronization or data access. * **Provider and Subscription Status:** Findings include inactive calendar providers, multiple conflicting subscriptions, expired or invalid subscriptions, and missing active providers, all of which affect calendar synchronization reliability. * **Synchronization Configuration Issues:** Errors such as missing emails in the sync configuration, mismatched emails between sync setup and location records, or duplicate email associations can lead to synchronization failures. ## Practical Use for ServiceNow Customers Understanding these scan findings enables you to quickly diagnose and resolve integration issues with Microsoft Exchange Online and calendar synchronization in ServiceNow. Correcting the specified errors ensures proper connection setup, secure OAuth authentication, active credentials, and valid synchronization configurations. This leads to reliable calendar data synchronization and smooth operation of related workflows. ## Next Steps To address each finding, refer to the detailed Microsoft Exchange Online - Calendar synchronization guidelines and the Synchronization - Prerequisites and implementation documentation. Additionally, consult resources on resolving connection setup issues and review related components such as providers, OAuth providers, scheduled jobs, flows, and configuration forms installed with Workplace Calendar Synchronization. After the instance scan completes, on the Scan Result form, review the findings in the Scan Findings related list. ## Scan findings {#sacn-finding-messages__section_fzv_ry2_gbc} 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. {#sacn-finding-messages__ul_yss_5y2_gbc} To fix a finding, refer to the following: * [Microsoft Exchange Online - Calendar synchronization](https://www.servicenow.com/docs/YTk9P2miUCvNoiEUhoNtFw "Synchronize reservations between Microsoft Exchange Online and Workplace Reservation Management.") * [Synchronization - Prerequisites and implementation](https://www.servicenow.com/docs/N2urO3N8hECCK1YwUuCNKQ "When you connect to your calendar provider for synchronization, you may incur a few connection or synchronization-related issues.") {#sacn-finding-messages__ul_bbs_zfc_3bc} **Related concepts** * [Resolving connection setup issues in Workplace Calendar Synchronization](https://www.servicenow.com/docs/5WZacGjWfIisiAhzCxoceg "This section helps administrators troubleshoot connection setup issues in Workplace Calendar Synchronization. Calendar sync integrates ServiceNow Workplace with external calendar providers — Microsoft Exchange Online and Google Calendar — to synchronize room and resource availability.") **Related reference** * [Components installed with Workplace Calendar Synchronization](https://www.servicenow.com/docs/U17Gm9kaZsoCk6hv8BB87Q "Several types of components are installed with the Workplace Calendar Synchronization application, including tables and user roles.") * [Properties installed with Workplace Calendar Synchronization](https://www.servicenow.com/docs/blLIqm6Kzu9JLoYmRZstyg "Customize the properties available with Workplace Calendar Synchronization.") * [Scheduled jobs installed with Workplace Calendar Synchronization](https://www.servicenow.com/docs/fhgjHChTvqf3NO6yFEb3ww "The Workplace Calendar Synchronization includes scheduled jobs to process a few synchronizations seamlessly.") * [Flows installed with Workplace Calendar Synchronization](https://www.servicenow.com/docs/3gpngdl1u01bS2Z6mEQZXQ "Below are the flows that run on different timelines.") * [Provider form](https://www.servicenow.com/docs/oipn_h8c_4ZUFrCYP3Bn2w "The Provider form includes calendar provider details and provider configuration field details.") * [Third-party OAuth Provider form](https://www.servicenow.com/docs/nhTwstHfTDjBZb~UN9T0kg "The Third-party OAuth Provider form includes OAuth provider details such as the client ID and client secret for personal authentication.")