Form reference
Cloud budgets
20 declared fields for Cloud budget. Required fields include Name, Cloud connection, Accountable owner, Budget month (first day, UTC).
Demo baseline · November 13, 2026About this form
Use this reference to identify built-in form labels, data types, and validation. Specialized workspaces can render a subset of these fields or provide workflow-specific controls. Your role, record state and tenant configuration can change what you see.
- Registry key
cloud_budgets- Record label
- Cloud budget
Field definitions
| Field | Type or reference | Built-in rules | Choices and constraints |
|---|---|---|---|
Namename | text | Required Default list field | — |
Cloud connectionconnectionId | reference cloud_connections | Required Default list field | — |
Accountable ownerownerId | reference users | Required Default list field | — |
Accountable cost centercostCenterId | reference cost_centers | Default list field | — |
Service accountability contextserviceCiId | reference__csdm_services | Default list field | — |
Budget month (first day, UTC)periodStart | date | Required Default list field | Use the first day of the month. The budget covers this complete UTC calendar month. |
Period end (exclusive)periodEnd | text | Read-only Default list field | — |
Exact billing service (empty: all services)serviceLabel | text | Optional by default | Match the provider's billing service label exactly. Cost center and service CI references express accountability and do not allocate or filter provider costs. |
Currencycurrency | text | Required Default list field | Three uppercase ISO currency letters matching the imported bill. No currency conversion is implied. |
Monthly budget amountamount | text | Required Default list field | Positive decimal amount with at most six fractional digits. This is a budget ceiling, not an automated cloud spending stop. |
Warning threshold (%)warningPercent | number | Required | Minimum 0.01Maximum 100 |
Configuration or review evidencereason | textarea | Required | Explain the budget decision in at least20 characters. Saving configuration resets approval; a different administrator must activate the draft. |
Versionversion | text | Read-only Default list field | — |
Approval statestate | text | Read-only Default list field | — |
AuthorcreatedById | text | Read-only Default list field | — |
Reviewed byreviewedById | text | Read-only Default list field | — |
ReviewedreviewedAt | text | Read-only Default list field | — |
Demo datasetdemoDataset | text | Read-only Default list field | — |
CreatedcreatedAt | text | Read-only Default list field | — |
UpdatedupdatedAt | text | Read-only Default list field | — |
Related procedure: Review a FinOps budget.
Verification evidence
The disposable audit exercised 12 applicable validation assertions on this definition. The authenticated collection read returned HTTP 200. See the verification matrix for scope.
Collection read results by built-in role
These statuses were observed over HTTP with one role per disposable MFA account. A successful list response can be empty and does not establish individual record, field, or write access.
| Role | HTTP status |
|---|---|
| Asset Manager | 200 |
| Change Manager | 200 |
| CMDB Manager | 403 |
| Contract manager | 200 |
| Customer service agent | 200 |
| Customer service customer | 403 |
| Customer service manager | 200 |
| Datacenter Customer | 403 |
| Datacenter Fulfiller | 200 |
| Datacenter Manager | 200 |
| Datacenter Vendor | 403 |
| EH&S auditor | 403 |
| EH&S manager | 403 |
| Executive Reader | 200 |
| Field service dispatcher | 200 |
| Field service technician | 200 |
| HR case agent | 403 |
| HR knowledge manager | 403 |
| HR lifecycle manager | 403 |
| HR profile manager | 403 |
| Employee Relations investigator | 403 |
| HR service catalog administrator | 403 |
| Inventory Counter | 403 |
| ITIL Fulfiller | 403 |
| Knowledge Manager | 200 |
| Business Manager | 200 |
| Platform Administrator | 200 |
| Service Desk Agent | 200 |
| Vendor manager | 200 |
| Third-party risk manager | 200 |
| Employee with no workspace role | 403 |
Edit and verify
- Open the list from the appropriate workspace and select an existing record or a permitted create action. Confirm the intended tenant and record number.
- Use the visible controls for the current record type and state. For reference fields, select a returned record from the lookup. Fill visible required fields and use the dedicated workflow action when the record has approval or completion gates.
- After saving, reopen the record and compare its persisted values, state and activity to the intended change. Check the downstream linked record when the action creates one.
Troubleshoot
- Missing field or control: compare the role, module, record state, form conditions and tenant overrides.
- Lookup returns no result: check that the referenced record is active, in scope and compatible with the current field.
- Save is rejected: keep the exact validation message and compare the field key, choice, constraints and required related records.
- See Edit and troubleshoot records and Configuration Studio.