Bump Azure.Messaging.ServiceBus from 7.20.1 to 7.20.2

[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.

You can trigger a rebase of this PR 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ClaudiodelaRiva]

This has been included in the combined pull request Combined dependency updates (2026-07-17)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.