Skip to main content

​
Contact support

Use Discord for public troubleshooting, service updates, and product questions that do not include sensitive details. For private account, billing, security, or project-specific issues, ask in Discord for the right private handoff path instead of posting details publicly. If you are not already in the Discord server, use the CloudEval Discord invite first.

​
Discord boundaries

Use the public Discord support channel for:
  • product questions that do not expose project details
  • public service updates and incident acknowledgements
  • troubleshooting steps that can be discussed without secrets, tenant IDs, subscription IDs, billing identifiers, or private URLs
Ask for a private handoff before sharing:
  • account or billing details
  • project names, tenant IDs, subscription IDs, resource IDs, private repository URLs, or customer screenshots
  • logs that contain credentials, tokens, API keys, webhook secrets, or long-lived cloud credentials
Public Discord is not a secure secret exchange. Keep sensitive examples out of public messages even when the issue feels urgent.

​
Include these details

  • Workspace or project name
  • Exact action you were taking
  • Connection path: Cloud sync, single-template infrastructure as code, or multi-file IaC workspace
  • Error message, if one was shown
  • Approximate timestamp and timezone
  • Screenshot, if the UI state matters and support has requested it privately
  • Impact: one user or multiple users

​
Before you contact support

  1. Check Cloud and IaC support to confirm the workflow is currently documented as supported.
  2. Check Availability and limits if the issue may be plan- or rollout-related.
  3. Check the relevant troubleshooting page first:

​
Do not send

  • Raw client secrets
  • Long-lived cloud credentials
  • Internal screenshots that expose sensitive resource names unless support has asked for them in a private channel
Never post passwords, API keys, client secrets, or long-lived cloud credentials in Discord or any public channel.

​
Good support request template

  • Environment: production
  • Workflow: Azure connection test / report run / share link / billing
  • Expected result: what should have happened
  • Actual result: what happened instead
  • Started at: timestamp with timezone
  • Reproduction steps: short numbered list
  • Safe context only: no secrets, private URLs, tenant IDs, subscription IDs, or billing identifiers

​
Next step

If you are blocked by a broken connection or failed report, go straight to the matching troubleshooting guide before opening a ticket.
Last modified on June 22, 2026