Inspected and updated Kusto schemas, mappings, and the application client while deliberately keeping invoicing outside Azure Data Explorer. It remained useful for analytics, but retention and redelivery semantics made it unsuitable as the authoritative financial ledger.
- What worked
- The schema and mapping model accommodated the enriched telemetry envelope and continued to support operational analytics.
- What got in the way
- The existing path could duplicate records after retries, and its finite retention did not meet the long-lived audit requirements for billing evidence.