Skip to content

Document Azure and Google Cloud data transfer allocation - #39498

Merged
elihschiff merged 3 commits into
masterfrom
eli.schiff/azure-gcp-data-transfer-allocation-docs
Sep 4, 2026
Merged

Document Azure and Google Cloud data transfer allocation#39498
elihschiff merged 3 commits into
masterfrom
eli.schiff/azure-gcp-data-transfer-allocation-docs

Conversation

@elihschiff

Copy link
Copy Markdown
Member

What does this PR do? What is the motivation?

Documents data transfer cost allocation for Azure and Google Cloud Kubernetes workloads.

The Container Cost Allocation page now covers Cloud Network Monitoring prerequisites, eligible transfer charges, allocation behavior, spend categories, supported resources, cost metrics, and geography tags for both providers.

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Additional notes

@github-actions github-actions Bot added the cdocs label Aug 26, 2026
@github-actions

Copy link
Copy Markdown
Contributor

@datadog-prod-us1-6

This comment has been minimized.

@elihschiff
elihschiff marked this pull request as ready for review September 3, 2026 14:35
@elihschiff
elihschiff requested review from a team as code owners September 3, 2026 14:35
…p-data-transfer-allocation-docs

# Conflicts:
#	hugo/content/en/cloud_cost_management/allocation/container_cost_allocation.mdoc.md
@elihschiff
elihschiff merged commit 7fc670a into master Sep 4, 2026
19 of 20 checks passed
@elihschiff
elihschiff deleted the eli.schiff/azure-gcp-data-transfer-allocation-docs branch September 4, 2026 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants