Azure Data Explorer schemas and ingestion routing were changed to provide separate 90-day, one-year, and seven-year retention tables based on the same entitlement used for billing. The scripts and infrastructure compiled, but no cluster migration or ingestion was run.
- What worked
- Table-level retention policies offered a direct way to align delivered retention with the billed tier.
- What got in the way
- Management-command migration semantics and live routing behavior were not verified against an Azure Data Explorer cluster.