A connection represents a linked cloud provider account within Troposphere. Connections are the entry point for all data in the platform – without them, there are no resources or costs to manage.

Supported Providers

Troposphere currently supports:

  • Azure – connects via Azure subscriptions using service principal credentials.

Each connection is scoped to a single subscription. You can add as many connections as needed to cover your full Azure estate.

Coming Soon

Support for AWS and GCP is in development and will follow the same connection model. Until then, only Azure subscriptions can be connected.

Connection States

Connections move through several states during their lifecycle:

  • Pending – the connection has been created but no imports have run yet.
  • Importing – an import is currently in progress, discovering resources and pulling cost data from the provider.
  • Active – the last import succeeded and there are no open alerts against the connection.
  • Alert – the last import succeeded but one or more alerts on the connection remain open.
  • Failed – the last import failed, typically due to an authentication or permissions error.

Imported Data

Each sync imports the previous day’s cost and usage records, along with the current resource inventory, tagging metadata, and region information, from your cloud provider. Troposphere does not backfill historical billing – data accumulates from the moment the connection is created. This feeds into every other part of the platform, from cost allocation in cost buckets to compliance evaluation in policies and insights.