[CCC-2415] Document Azure EA to MCA export migration - #39304
Conversation
Preview links (active after the
|
|
/review |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
🤖 Automated review by Claude. AI-generated; verify before acting.
Two style nits on this otherwise clear migration section. No blockers.
Reviewed 4d152a275d3848ad598f22db78c236c858109ea4 — workflow run
| * Storage directory and export prefix | ||
| * Dataset version, format, and compression type | ||
| 2. Leave the Azure Cloud Cost Management configuration in Datadog enabled and unchanged. | ||
| 3. After the MCA becomes active, follow the [cost export instructions](#generate-cost-exports) to recreate the actual and amortized exports at the corresponding MCA scope. Use the export names, storage account, container, directory, and prefix recorded from the EA exports. |
There was a problem hiding this comment.
Style: The rest of this page uses numbered reference-style Markdown links with definitions at the bottom (see CONTRIBUTING.md style guide). This inline link is the only exception. Consider converting it to a reference link like [cost export instructions][17] and adding the definition ([17]: #generate-cost-exports) with the other definitions at the bottom of the file.
|
|
||
| Azure exports cost data starting from the month you created the export. Datadog automatically ingests up to 15 months of available historical cost data from these exports. You can manually backfill up to 12 months of Azure cost data using the Azure Cost Exports UI. | ||
|
|
||
| If you migrated from an EA to an MCA, follow the migration instructions below before running a historical export. Run the export from the agreement scope that covered the requested dates. |
There was a problem hiding this comment.
Suggestion: Link directly to the migration section rather than relying on "below," so readers can jump straight to it.
| If you migrated from an EA to an MCA, follow the migration instructions below before running a historical export. Run the export from the agreement scope that covered the requested dates. | |
| If you migrated from an EA to an MCA, follow the [migration instructions](#migrate-exports-after-changing-billing-agreements) before running a historical export. Run the export from the agreement scope that covered the requested dates. |
1 participant
What does this PR do? What is the motivation?
Fixes CCC-2415.
Documents the Azure EA-to-MCA export migration path so customers can preserve historical cost data.
Merge readiness
For Datadog employees:
<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./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used AI-assisted research and drafting; the content was reviewed and refined manually.
Additional notes
git diff --checkpasses.