Skip to content

[DOCS-14474] Clarify PAYG account support in Azure CCM setup#37015

Draft
domalessi wants to merge 1 commit into
masterfrom
domalessi/docs-14474-azure-ccm-payg
Draft

[DOCS-14474] Clarify PAYG account support in Azure CCM setup#37015
domalessi wants to merge 1 commit into
masterfrom
domalessi/docs-14474-azure-ccm-payg

Conversation

@domalessi
Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Fixes DOCS-14474

Clarifies Azure Cloud Cost Management's support for Pay as you go (PAYG) accounts. The previous Overview said only that PAYG support was in Preview and to contact support with setup issues, without naming the actual eligibility requirement or workarounds.

Changes:

  • Promotes PAYG account support to its own top-level section between Overview and Setup, so eligibility is visible before users start setup.
  • States the specific requirement: Cloud Cost Management needs actual and amortized cost exports.
  • Names the failure mode: PAYG subscriptions limited to Usage details (usage only) exports cannot send cost data to Datadog.
  • Links Microsoft's Cost Management export support matrix so users can check their subscription.
  • Adds a migration path (MCA or EA) for PAYG subscriptions that lack the required exports.
  • Updates the Overview to acknowledge EA accounts alongside MCA (both are valid at all three scopes).

Merge instructions

Merge readiness:

  • Ready for merge

Additional notes

Promote PAYG account support to its own top-level section, name the
specific export-type requirement, and provide a migration workaround for
subscriptions that only expose Usage details exports.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant