Billing And Storage
AI Cloud usage is tied to tenant, project, runtime, and storage context.
Billing Concepts
| Concept | Meaning |
|---|---|
| Balance | Available funds or credits for usage. |
| Hourly burn | Estimated cost of currently running work. |
| Accrued usage | Usage accumulated by a runtime or project. |
| Quota | Product or project limit for capacity or resources. |
| Entitlement | Policy that allows or restricts a class of usage. |
Before Long-Running Work
Check:
- selected project;
- runtime family and SKU;
- expected duration;
- hourly burn;
- balance or entitlement;
- quota headroom;
- storage requirements.
Tenant Admin Review
Tenant admins should review:
- active runtimes;
- stale workloads;
- quota pressure;
- balance and burn;
- service accounts that can launch work;
- project ownership and cost attribution.
Storage
Storage should be attached only when the workload needs it. Confirm the bucket or storage resource belongs to the correct project and that the user or service account has the needed permission.
Common storage checks:
- project ownership;
- quota;
- access grant;
- data locality or region;
- cleanup owner;
- retention expectation.
Cost Control Habits
- Release unused runtimes promptly.
- Prefer smaller profiles for tests.
- Use project-specific service accounts for automation.
- Review stale notebooks, endpoints, and schedulers.
- Keep storage ownership and retention clear before handoff.