chore(deps): update Azure crates (March 2026 release)

[jlaundry]

Summary

Update the Azure dependencies to the March 2026 release.

azure_core and azure_identity include minor bug fixes, but as per @LarryOsterman azure_storage_blob 0.10.1 includes some significant performance improvements.

(azure_core 0.34 and azure_identity 0.34 were just released, but the matching azure_storage_blob 0.11 is not ready yet - we'll revisit that next month.)

Vector configuration

N/A

How did you test this PR?

Integration tests & soak test in my lab environment.

Change Type

• Bug fix
• New feature
• Dependencies
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

• Closes: chore(deps): bump the azure group across 1 directory with 3 updates #24701
• Related: Azure improvement meta tracker #25148

[thomasqueirozb]

Thanks!

[jlaundry]

I'm taking a look at these issues now... first, make cross-build-x86_64-unknown-linux-gnu is failing:

thread 'main' (3284) panicked at /cargo/registry/src/index.crates.io-1949cf8c6b5b557f/aws-lc-sys-0.40.0/builder/cc_builder.rs:731:9:
  ### COMPILER BUG DETECTED ###
  Your compiler (cc) is not supported due to a memcmp related bug reported in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189. We strongly recommend against using this compiler. 

It looks like the cross-rs containers were built on Ubuntu 20.04, which defaults to gcc 9 (as per the link, this bug was fixed in gcc 10.3). If we wanted aws-lc-rs in the future, fixing this probably means replacing gcc in the Dockerfile.

But as below, I've just removed aws-lc-rs completely, so this should be fine now.

[jlaundry]

Second, some of the nats integration tests are failing:

https://github.com/vectordotdev/vector/actions/runs/25378458763/job/74421088034#step:8:3834

         START             vector sinks::nats::integration_tests::nats_tls_client_cert_invalid
  
  running 1 test
  
  thread 'sinks::nats::integration_tests::nats_tls_client_cert_invalid' (51438) panicked at /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/rustls-0.23.37/src/crypto/mod.rs:249:14:
  
  Could not automatically determine the process-level CryptoProvider from Rustls crate features.
  Call CryptoProvider::install_default() before this point to select a provider manually, or make sure exactly one of the 'aws-lc-rs' and 'ring' features is enabled.
  See the documentation of the CryptoProvider type for more information.

This was because azure_core now depends on reqwest 0.13, which depends on rustls-platform-verifier, which depends on rustls ^0.23.4, which now defaults to using aws-lc-rs. It's not clear (to me) why only the nats tests that failed as a result... but in any case, the simple fix is to remove aws-lc-rs by

https://github.com/jlaundry/vector/blob/051c6bd6556a7b80c721f4ed403e9fcd0a88f0f8/Cargo.toml#L226