Skip to main content
Backfilling historical dataAzure exports only produce data going forward. To import past months, the module triggers one-off export runs via azapi_resource_action. Two variables control this:Run the backfill as a separate apply:
This calls the Azure exports/run API for both the actuals and amortized exports, one calendar month at a time. Azure writes the Parquet files to the same container and Costory picks them up on the next sync. Set run_backfill back to false afterward to avoid re-triggering on future applies.
Last modified on June 30, 2026