Concept
Subscriptions
Multiple active subscriptions can layer production entitlements with sandbox add-ons across one organization without merging their billing narratives. Finance reconciles each subscription line against usage exports and contract schedules every close. Documentation should clarify which APIs, quotas, and support SLAs each tier unlocks so engineers provision with correct expectations.
8 documentation pages cover this concept. Editorial glossary
Concepts
How-tos
Reference
Overview
faq
Related
Covers concept (incoming)
documented at
Maps to (incoming)
- Azure Subscriptions→
- N/A (No subscription concept — AWS Accounts with optional consolidated billing via AWS Organizations)→
- N/A (No subscription layer — GCP Billing Accounts linked to Projects)→
- N/A (No subscription model — pay-as-you-go with monthly invoices per project)→
- N/A (No subscription model — usage-based monthly billing)→
Diverges from
- Azure Subscriptions→
- N/A (No subscription concept — AWS Accounts with optional consolidated billing via AWS Organizations)→
- N/A (No subscription layer — GCP Billing Accounts linked to Projects)→
- N/A (No subscription model — pay-as-you-go with monthly invoices per project)→
- N/A (No subscription model — usage-based monthly billing)→
Citations
These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.