To enforce tagging in AWS and Azure you need three layers, not one switch: a block at creation time (a service control policy or an Azure Policy deny), a correction layer for values and existing resources (AWS tag policies, Azure Policy modify), and a check in the billing data. Only the third layer shows whether a tag actually reaches the cost line that finance later maps to a cost centre.

What each mechanism actually enforces

MechanismActsDoesDoes not
AWS tag policy, basic rules with enforced_forwhen supported resource types are taggedallowed values and capitalisation of a supplied keymissing keys, resources with no tags at all
AWS tag policy with report_required_tag_forin the compliance report and IaC checksrequired keys in CloudFormation, Terraform and Pulumi once the hook or provider check is onconsole, CLI and direct API calls
SCP with aws:RequestTagon every API call in member accountsrequired keys at creation, for actions that support tag-on-createthe management account, service-linked roles, actions without that condition key
AWS Config required-tagsafter configuration changesreports up to six required tags on listed resource typesprevent creation
Azure Policy denyon create and updaterequired tag on new and updated resourcesexisting resources, which are only marked non-compliant
Azure Policy modifyon create and update; existing resources via remediationadd a missing tag, for example from the resource groupresource types that do not support tags
Billing activationwhen the bill is processedtag appears on the cost linecharges with no resource behind them

The first row matters most. AWS states that basic tag policy rules evaluate neither untagged resources nor missing required keys. Setting enforced_for alone stops CostCenter where you wanted cost-center, but not an instance with no cost centre at all.

An API call or deploymentcreates a resourceLayer 1, block at creation: SCP withaws:RequestTag, Azure Policy denyLayer 2, correct values and existing resources:AWS tag policy, Azure Policy modify with remediationLayer 3, check in the billing data: cost allocationtags activated in AWS, tag inheritance on in AzureThe tag on the cost line, mappedby finance to a cost centre
Three layers, one tag: creation is blocked without the key, values and existing resources are corrected, and the billing data shows whether the tag reached the cost line

Keep the required schema small

Three keys are enough to start: team for the owning team, env for prod, staging or dev, and cost-center for the finance cost centre. Define allowed values for each, agreed between finance and engineering, and name one exception approver. The env key is also what lets you make non-production costs visible.

Settle capitalisation before the first rollout. Azure treats tag names as case-insensitive for operations but shows the stored casing in cost reports, and tag values are case-sensitive. In AWS, a tag policy that fixes capitalisation treats CostCenter and costcenter as different keys. Lower case everywhere avoids duplicate groups in cost reports.

Personal data does not belong in tags. Microsoft warns that tags are stored as plain text and surface in cost reports, deployment histories and exported templates; AWS also advises against sensitive information in tags. team=payments does the job; an email address does not.

AWS: require tags at creation with an SCP

A service control policy denies API calls that lack a tag. The condition key aws:RequestTag/{key} with the Null operator tests whether the key is absent from the request. This SCP blocks ec2:RunInstances without cost-center or without team:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "DenyRunInstancesWithoutCostCenter",
      "Effect": "Deny",
      "Action": "ec2:RunInstances",
      "Resource": "arn:aws:ec2:*:*:instance/*",
      "Condition": { "Null": { "aws:RequestTag/cost-center": "true" } }
    },
    {
      "Sid": "DenyRunInstancesWithoutTeam",
      "Effect": "Deny",
      "Action": "ec2:RunInstances",
      "Resource": "arn:aws:ec2:*:*:instance/*",
      "Condition": { "Null": { "aws:RequestTag/team": "true" } }
    }
  ]
}

Keep the statements separate: IAM combines several keys under one condition operator with a logical AND, so a single statement would deny only when both tags were missing.

Three limits belong in your developer documentation. SCPs do not affect users and roles in the management account, nor service-linked roles. Not every create action supports aws:RequestTag; check each action in the Service Authorization Reference before you add it. And member accounts cannot retrieve their effective SCP, so AWS recommends documenting the rules and giving developers read access to CloudTrail to trace denied calls.

AWS: values, IaC checks and existing resources

The tag policy handles what the SCP cannot: allowed values and capitalisation, inherited across the organisation.

{
  "tags": {
    "cost-center": {
      "tag_key": { "@@assign": "cost-center" },
      "tag_value": { "@@assign": ["cc-*"] },
      "enforced_for": { "@@assign": ["ec2:ALL_SUPPORTED"] },
      "report_required_tag_for": { "@@assign": ["ec2:ALL_SUPPORTED"] }
    }
  }
}

enforced_for blocks tagging operations with a disallowed value on supported EC2 types. report_required_tag_for marks the key as required for IaC: the AWS-managed CloudFormation hook AWS::TagPolicies::TaggingComplianceValidator warns or fails, and the Terraform AWS Provider from version 6.22.0 and a Pulumi policy pack check the same policy. Activate the hook in every account and Region, for example with StackSets.

For existing resources, the tag policy's compliance report covers only resources that have carried at least one tag at some point. Find untagged resources with AWS Resource Explorer and the query tag:none. The AWS Config rule required-tags (identifier REQUIRED_TAGS) checks up to six keys on the listed resource types and serves as ongoing detection.

Azure: audit first, then deny

Azure Policy ships the built-ins you need. "Inherit a tag from the resource group if missing" fills a missing tag from the resource group; "Require a tag on resources" denies whatever is still missing. Azure evaluates modify before deny, so a resource in a correctly tagged resource group receives the tag before the deny check runs. Because "Require a tag on resources" does not apply to resource groups, also assign "Require a tag on resource groups".

Step 1: audit the required tag without blocking.

az policy assignment create \
  --name require-cost-center \
  --policy 871b6d14-10aa-478d-b590-94f262ecfa99 \
  --scope /subscriptions/{subscription_id} \
  --params '{"tagName": {"value": "cost-center"}}' \
  --enforcement-mode DoNotEnforce

Step 2: inherit a missing tag from the resource group.

az policy assignment create \
  --name inherit-cost-center \
  --policy ea3f2387-9b95-492a-a190-fcdc54f7b070 \
  --scope /subscriptions/{subscription_id} \
  --params '{"tagName": {"value": "cost-center"}}' \
  --mi-system-assigned --location westeurope \
  --identity-scope /subscriptions/{subscription_id} --role Contributor

Step 3: remediate existing resources.

az policy remediation create \
  --name inherit-cost-center-backfill \
  --policy-assignment inherit-cost-center

Step 4: enforce after the audit period.

az policy assignment update \
  --name require-cost-center \
  --scope /subscriptions/{subscription_id} \
  --enforcement-mode Default

DoNotEnforce evaluates compliance without blocking requests. The modify assignment needs a managed identity with the role the definition names in roleDefinitionIds, Contributor for this built-in. Without a remediation task, existing resources stay marked non-compliant, because modify does not change existing resources during an evaluation cycle.

When the tag reaches billing data

AWS. User-defined tags must be activated as cost allocation tags, in the Billing and Cost Management console under "Cost allocation tags", and, in an organisation, only from the management account (a standalone account activates its own). After you first apply a tag it can take up to 24 hours for the key to appear there, and up to another 24 hours to activate. "Backfill tags" applies the activation retroactively for up to twelve months, but only to resources that already carried the tag at the time. In CUR 2.0, activated keys appear in the tags map column with prefixes such as resourceTags/ and accountTag/.

Azure. Tag inheritance in Cost Management applies subscription and resource group tags to usage records, not to the resources themselves. It is available for EA, MCA and MPA billing accounts, applies from the first of the current month and takes 8 to 24 hours. Purchases and resources that do not emit usage at subscription scope do not receive the tags. On other agreement types, the modify policy on the resources is the route.

AWSAzure, EA, MCA and MPATag applied to the resourceKey appears under cost allocationtags, up to 24 hoursActivated from the managementaccount, up to another 24 hoursKey in the CUR 2.0 tags column; backfill up totwelve months, only where the tag already wasTag on the subscriptionor resource groupTag inheritance in Cost Management,8 to 24 hoursUsage records carry it from thefirst of the current month
When a tag reaches the bill: AWS activates a key in two waits of up to 24 hours and backfills only where the tag already was; Azure inherits onto usage records from the first of the month

Rollout from audit to deny

  1. Measure the baseline: the share of cost carrying each required key, not the number of tagged resources.
  2. Agree the schema, allowed values and exception owners, and store them in the repository.
  3. Switch on audit mode: tag policy without enforced_for, IaC hook in warn mode, the Config rule, Azure assignments with DoNotEnforce. Run it for at least one month-end close.
  4. Fix what it finds: default tags in IaC modules, Azure remediation, bulk tagging with the AWS Tag Editor.
  5. Enforce first in a test OU and a test subscription, never straight at the root. Check autoscaling and services that create resources on your behalf; AWS warns that strict tag policies can otherwise block scaling.
  6. Enforce broadly: SCP on production OUs, hook on fail, Azure on Default. Document exceptions rather than weakening the policies.

Costs you cannot tag

Even with complete enforcement, some cost carries no resource tag: tax, support fees, credits and refunds, purchases such as reservations in Azure, and resource types that do not support tags, such as classic Cloud Services. AWS covers this with account tags from AWS Organizations, which once activated apply to all usage in an account, explicitly including refunds, credits and charges that cannot be tagged. In Azure the subscription level plays that role. What remains belongs in an allocation rule and a visible residual, not in invented tags. Allocating shared costs in multi-tenant SaaS covers how to split it.

Review coverage in the monthly cloud cost review as allocation coverage: allocated cost plus the stated residual equals the bill total. AWS CUR 2.0 or FOCUS explains which export columns carry the tags.

Where Costfluent fits

Costfluent reads tags from AWS, Azure and Google Cloud billing data through read-only connectors and shows tag coverage overall and per key. Ordered rules in cost allocation assign cost to a segment by account or subscription, resource group, resource name or tag; whatever no rule claims stays visible on an unallocated line. Setting tags and enforcing policies still happens in AWS and Azure.

Sources and method

Checked on 2026-10-10. AWS Organizations, Enforce tagging consistency, Report tagging compliance, Tag policy syntax and examples, Enforce required tag key with IaC and Service control policies; AWS IAM, Conditions with multiple context keys or values; AWS whitepaper, Implementing and enforcing tagging; AWS Config, required-tags; AWS Billing, Cost allocation tags, Activating user-defined cost allocation tags, Backfill and Account tags; AWS Data Exports, CUR 2.0 tags column; Microsoft Learn, Policy definitions for tagging resources, Use tags, Deny effect, Modify effect, Effect basics, Assignment structure, az policy assignment, az policy remediation and Tag inheritance in Cost Management; the built-in definitions RequireTag_Deny.json and InheritTag_Add_Modify.json. The tables, examples and rollout order are Costfluent recommendations; test every policy in a dedicated test OU or subscription before assigning it broadly.