Bump the azure group with 1 update

[dependabot]

Updated Azure.Messaging.ServiceBus from 7.20.1 to 7.20.2.

Release notes

Sourced from Azure.Messaging.ServiceBus's releases.

7.20.2

7.20.2 (2026-07-08)

Acknowledgments

Thank you to our developer community members who helped to make the Service Bus client library better with their contributions to this release:

• Daniel Marbach (GitHub)

Bugs Fixed

• Fixed a bug where ServiceBusAdministrationClient operations (such as GetQueueAsync, GetTopicAsync, QueueExistsAsync, and TopicExistsAsync) threw a ServiceBusException wrapping an ArgumentException ("Value cannot be empty or contain only white-space characters") when an entity had a shared access authorization rule whose key values were masked (returned empty) by the service for callers lacking the listkeys/action permission. The deserialization path now accepts empty key values, and creating CreateQueueOptions/CreateTopicOptions from the returned properties no longer throws, matching the behavior of the other Azure Service Bus SDKs. (#​60469)

• Fixed a bug in the ServiceBusProcessor where terminal errors (such as DNS resolution failures) caused a tight retry loop with no delay between attempts, potentially overwhelming logs and consuming excessive resources. (#​54572)

• Fixed a race condition in AmqpSender where concurrent calls to CreateMessageBatchAsync during initial AMQP link creation could observe an inconsistent MaxBatchSize, causing a spurious ArgumentOutOfRangeException. (#​56301)

• The sender now reads the com.microsoft:max-message-batch-size vendor property from the AMQP link to correctly limit batch size on Premium large-message entities, where max-message-size can be up to 100 MB but the batch limit is 1 MB. The 4,500 message count cap on batches has been removed as the service does not enforce a count limit. (#​44914)

Other Changes

• Several areas of the AMQP transport integration have been cleaned up, modernized, and made more efficient. (A community contribution, courtesy of danielmarbach)

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions