DevOps Change Velocity - Tool cannot be connected due to a technical issue while performing tool connectivity check<!-- /*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: ; } } Issue Customer is trying to connect to an Azure tool using an OAuth 2.0 credential in DevOps Workspace and faces the error: Tool cannot be connected due to a technical issue while performing tool connectivity check. Cause When connecting to Azure using OAuth 2.0 credential, two subflows in Flow Designer are executed: Create Additional Connection Alias for Azure and DevOps Clone OAuth Credential.To make sure your issue is the same as this article, check sn_devops_log table for the error: com.snc.process_flow.exception.ProcessAutomationException: Role ID doesn't exist: <some_id>This error will be logged into the table when you click the connect button. This errors means that the two subflows lost its reference to the oauth_admin role. Resolution 1. Open Subflow - Create Additional Connection Alias for Azure2. Click the three dots at the top right > Properties3. Scroll down and expand Advanced options- You will see Run with role(s)4. Delete the role that looks like an ID5. Add the role oauth_admin- Run with role(s) should now have: connection_admin and oauth_admin6. Update7. Publish9. Repeat same steps with Subflow - DevOps Clone OAuth Credential10. Try to connect the tool again using the OAuth 2.0 credential.After you change both subflows, the Run with role(s) should look like this: