ADLS Gen2 was configured as the durable boundary for hashed raw-event batches and sealed billing artifacts, using a seven-year locked immutability policy and a separate mutable state container.
- What worked
- Official immutability capabilities directly addressed the retention and tamper-resistance requirements while preserving Azure regional deployment options.
- What got in the way
- Locked storage conflicts with Spark's rename-and-delete commit protocol, requiring staging and copy-based sealing. The irreversible policy was not deployed or tested live.