Unable to initiate Teams collaboration chats from Aspen "Invalid Access token. Please check your credential alias"Issue <!-- /*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: ; } } When attempting to start a Microsoft Teams chat from acase in ServiceNow, the system displays an error message:“Invalid Access token. Please check your credential alias.”This prevents users from initiating Teams chat directly from the case form. The issue appears to be related to the Microsoft Teams integration and OAuth credential alias configuration. 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: ; } } NA 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: ; } } We observed that the token request sent via a POST call to the following endpoint resulted in a 400 Bad Request error: https://teamsproxy.service-now.com/teams/chat/app/token Response body: {"error":"invalid_grant","error_description":"AADSTS700003: Device object was not found in the tenant '3bfeb222-e42c-4535-aace-ea6f7751369b' directory. Trace ID: e4123ced-c92f-4b8d-a703-f12ec6b27700 Correlation ID: 7cf2ddc7-0dda-4432-9c99-b3416760973d Timestamp: 2025-12-15 05:20:16Z","error_codes":[700003],"timestamp":"2025-12-15 05:20:16Z","trace_id":"e4123ced-c92f-4b8d-a703-f12ec6b27700","correlation_id":"7cf2ddc7-0dda-4432-9c99-b3416760973d","error_uri":"https://login.microsoftonline.com/error?code=700003","suberror":"device_authentication_failed","claims":"{\"access_token\":{\"capolids\":{\"essential\":true,\"values\":[\"1c80a8e9-b839-4b4b-b360-60a930d9b3b1\",\"ba5ae1a0-5da2-4dcd-9475-23131f6cc734\"]}}}"} OAuth Credential linked to the user for Microsoft Teams is invalid or expired, causing the access token to be rejected during chat initiation. Cannot find the credential named 'Microsoft Teams Chat' associated with the user who received the error.This issue is happening because the device identity (i.e. users, groups, or applications) was deleted or not exist in Microsoft Entra ID. Kindly refer to the solution shared this MS documentation. https://learn.microsoft.com/en-us/troubleshoot/entra/entra-id/app-integration/error-code-aadsts700003-device-object-not-found https://learn.microsoft.com/en-us/answers/questions/2278445/error-code-700003 If customer have any questions or need further help, they need create a Azure support request, or ask Azure community support