Allocated Tags
Column definition from FOCUS v1.3. Read its requirements and implementation guidance before mapping provider data.
- Source
- FOCUS MCP snapshot
- Edition
- v1.3
- Column ID
AllocatedTags- Mode
- Read-only
- Library snapshot (UTC)
- 2026-10-08
Constraints
Description
The Allocated Tags column represents the set of tags assigned to tag sources which are specifically applicable to allocated charges resulting from a data generator-calculated split cost allocation.
Requirements
AllocatedTags adheres to the following requirements:
- AllocatedTags MUST be present in a Cost and Usage FOCUS dataset when the service provider supports Data Generator-Calculated Split Cost Allocation.
- AllocatedTags MUST conform to KeyValueFormat requirements.
- AllocatedTags nullability is defined as follows:
- AllocatedTags MUST be null when a charge is not related to a data generator-calculated split cost allocation.
- AllocatedTags MAY be null in all other cases.
- When AllocatedTags is not null, AllocatedTags adheres to the following additional requirements:
- AllocatedTags MUST NOT include resource tags already present in Tags.
- AllocatedTags MUST include all applicable user-defined and data generator-defined tags for the AllocatedResourceId.
- Tag keys that do not support corresponding values MUST have a corresponding true (boolean) value set.
- Data generator MUST NOT alter tag values unless applying true (boolean) to valueless tags.
- Data generator-defined tags adhere to the following additional requirements:
- Data generator-defined tag keys MUST be prefixed with a predetermined, data generator-specified tag key prefix that is unique to each corresponding provider-specified tag scheme.
- Data generator SHOULD publish all data generator-specified tag key prefixes within their respective documentation.
- User-defined tags adhere to the following additional requirements:
- Data generator MUST prefix all user-defined tags scheme with a predetermined, data generator-specified tag key prefix that is unique to each corresponding user-defined tag scheme when the data generator has more than one user-defined tag scheme.