Cloud onboarding
Grant CloudPulse read access in your cloud, then register the account in the app. Production uses federation (no long-lived customer keys stored by CloudPulse).
Azure
Microsoft Azure
Entra app + management group + optional billing export.
GCP
Google Cloud
Org IAM + workload identity federation + optional BigQuery export.
AWS
Amazon Web Services
One CloudFormation stack (and StackSet for org members) + optional CUR.
OCI
Oracle Cloud
Tenancy setup script + federated JSON paste.
What you do vs CloudPulse support
| You (customer admin) | CloudPulse support |
|---|---|
| Run the downloadable setup artifact; fill Accounts fields; confirm data in Insights. | Create your CloudPulse tenant; share federation IDs when needed; help with optional org-wide extras (reservation orders, StackSet, etc.). |
Examples below use placeholders only (
<entra-tenant-id>,
<12-digit-account>, …). No customer estate names or IDs appear in these docs.