For the complete documentation index, see llms.txt. This page is also available as Markdown.

Reference B: Instance-scope troubleshooting

The onboarding wizard surfaces a single general validation message for any failure during Validate Connection: We couldn't validate the connection. Please confirm your Tenant ID and that the Cortex Cloud application is installed in your Azure DevOps organization, then try again. The following table maps observed symptoms to root causes and the resolving user action.

Symptom
Likely cause
User action

Validation fails immediately after consent

The Cortex Cloud application was not added to your Azure DevOps organization's user list.

Add the Cortex Cloud name shown in the wizard to Organization Settings → Users in Azure DevOps, then select Validate Connection again.

Validation fails with Tenant ID referenced in support logs

The Tenant ID does not exist or is malformed.

Re-check the Tenant ID. Confirm the value is a valid GUID.

Microsoft consent page returns access denied

The person who attempted to authorize was not an Entra ID Global or Privileged Role Administrator.

Re-run Authorize. Coordinate with the Entra ID admin to approve the consent prompt.

Integration status changes to Error with "Admin consent has been revoked"

The tenant admin revoked consent for the Cortex Cloud application.

Coordinate with your admin to approve the prompt.

Integration status changes to Error with "The Cortex Cloud service principal no longer has access"

The Cortex Cloud application was removed from the Azure DevOps organization.

Re-add the Cortex Cloud application via Organization Settings → Users in Azure DevOps.

Integration status changes to Error with "Service principal credentials are no longer valid"

The Cortex Cloud application was disabled or deleted in Entra ID. (Rare; indicates a tenant-level intervention.)

Contact Cortex Cloud Support if the application was not intentionally disabled.

Integration status changes to Error with "Authentication temporarily unavailable"

A Cortex Cloud-side condition is affecting the regional application credential.

No customer action required. Cortex Cloud Operations is alerted automatically. Contact Support if the condition persists.

Last updated

Was this helpful?