...
- Will be used to facilitate automated billing via the Cornell KFS system. Expected integration date: TBA
- Any Azure resource with that tag will be billed directly to the provided KFS account number.
- Anything in a Cornell Azure subscription that is not tagged (or cannot be tagged) will be billed to the Cornell KFS account number associated with the Azure subscription as a whole.
Note that applying the "Cost Center" tag to a resource does not retroactively adjust the billing data for the resource, prior to the tag being set.
Tag key/name: "Cost Center" (single space included between "Cost" and "Center")
Tag value formats:
- A seven-character KFS account number.
OR - A seven-character KFS account number, followed by a hyphen, followed by a sub-account number.
OR - A fully qualified KFS accounting string as outlined here: https://www.dfa.cornell.edu/accounting/chartofaccounts/transactionstring
- Under this scheme, the parts of the accounting string labeled as optional in the link above can be left off, but a total of six hyphens are required.
...
- Resource naming and tagging decision guide: https://docs.microsoft.com/en-us/azure/architecture/cloud-adoption/decision-guides/resource-tagging/
- Use tags to organize your Azure resources: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-using-tags
- Which Azure resources support tagging: https://docs.microsoft.com/en-us/azure/azure-resource-manager/tag-support
- Naming conventions: https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions#organize-resources-with-tags
- Standard optional tags recommended for AWS are also relevant for use in Azure. See AWS Standard Tagging