Azure improvement meta tracker

[jlaundry]

This meta issue is to capture the various improvements discussed in the previous PRs, and the things that I plan to help with in the near term:

azure_common

• Update dependencies
  • chore(deps): update Azure crates (March 2026 release) #25169 azure_core 0.34.0 and azure_identity 0.34.0 are fairly minor, but azure_storage_blobs 0.10.1 contains some serious performance improvements
  • azure_core 0.35.0 (May 2026) should include Change typespec_client_core::http::policies::logging Request and Response log level to debug Azure/azure-sdk-for-rust#3643 which will reduce the noise in the default vector output log
• chore(azure sinks): refactor Blob code out of azure_common #25689

azure_logs_ingestion

• Create an integration test container (Microsoft don't provide an Azurite equivalent, so I'm going to write my own...) and create some integration tests
• Once integration tests are in place, add support for sending logs gzip compressed, and ensure messages respect the maximum size etc

azure_blob

• fix(azure_blob): make AccountName optional when BlobEndpoint is provided #24663
• Add support to Azure blob sink to configure Content-Encoding and Content-Type #21795

azure_monitor_logs

• Around September (once the upstream API is deprecated), deprecate and remove this sink

not my work, but for completeness:

• feat(new source/sink) Added Azure Event Hub source/sink #24659
• feat(new sink): Azure Data Explorer Sink #24633
• feat(azure_blob sink): support blob index tags and metadata #25545

[jlaundry]

@jlaundry this got merged Can you recap the followups you had planned?

@pront I couldn't comment on #24729 now that it's closed, was this what you were after?

[pront]

@jlaundry this got merged Can you recap the followups you had planned?

@pront I couldn't comment on #24729 now that it's closed, was this what you were after?

Ah, apologies for that. Locking was automated GitHub behavior. This is perfect thanks!

[mortenmj]

#24663 is forcing us to remain at v0.51. We're detecting one critical and several high level CVEs on that image. We would appreciate seeing that fixed so that we can upgrade our version.