Integration setup issues

Connection fails

1. Confirm the provider and authentication method.
2. Verify IDs, keys, secrets, tokens, and redirect URLs.
3. Confirm required cloud APIs and billing exports are enabled.
4. Verify the selected accounts, projects, subscriptions, compartments, or organization scope.
5. Check that the credential has the required permissions and is not expired.
6. Retry the callback flow for Slack, Jira, Teams, or another OAuth integration.

Connection succeeds but no data appears

Check discovery scope, billing setup, source status, and ingestion state. Confirm that the account is visible in integration details and that Cost Explorer filters include it.

Provider-specific notes

• AWS setup may offer access-token or CLI-console flows.
• GCP setup can require billing account and project IDs plus enabled APIs.
• OpenAI setup requests an account name, API key, and optional Organization ID.
• Entitlement sources must be healthy before License Optimizer can evaluate coverage.

Escalation details

Detail	Why it helps
Provider and authentication method	Identifies the expected setup flow.
Integration status message	Shows whether the failure is authentication, discovery, billing, or ingestion.
Selected scope	Confirms which accounts, projects, subscriptions, compartments, or workspaces should appear.
Latest visible billing date	Separates provider export delay from missing permissions.

Rotate any credential that may have been exposed during troubleshooting.