chore(deps): update azure azure-sdk-for-net monorepo

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
Azure.ResourceManager.AppService (source)	1.4.1 → 1.5.0
Azure.ResourceManager.ServiceBus (source)	1.1.0 → 1.2.0

---

Release Notes

Azure/azure-sdk-for-net (Azure.ResourceManager.AppService)

v1.5.0

Compare Source

1.5.0 (2026-06-02)

Features Added

• Upgraded api-version to 2025-05-01.
• Separated CertificateRegistration and DomainRegistration from App Service.

Bugs Fixed

• Fix deserialization when AppServiceApiDefinitionInfo.Uri is not a valid URI.
• Fix deserialization when FunctionAppStorage.Value is not a valid URI.

Other Changes

• Upgraded dependent Azure.Core to 1.57.0.
• Upgraded dependent Azure.ResourceManager to 1.14.0.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[claude]

Code review

No issues found. This is a mechanical Renovate dependency bump touching only Directory.Packages.props (Azure.ResourceManager.AppService 1.4.1 → 1.5.0, Azure.ResourceManager.ServiceBus 1.1.0 → 1.2.0), with no code changes. Nothing to flag from a design/architecture standpoint — safe to merge pending CI.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: af4542156c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[coderabbitai]

Warning

Review limit reached

@thomhurst, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 34 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cf3e329e-d06e-4a65-834b-ca221b4ccca0

📥 Commits

Reviewing files that changed from the base of the PR and between 63852cf and 68bf3bd.

📒 Files selected for processing (1)

• Directory.Packages.props

📝 Walkthrough

Walkthrough

The central package management file updates Azure.ResourceManager.AppService from 1.4.1 to 1.5.0 and Azure.ResourceManager.ServiceBus from 1.1.0 to 1.2.0.

Changes

Azure package updates

Layer / File(s)	Summary
Central package version updates Directory.Packages.props	Updates the centrally managed App Service and Service Bus Azure Resource Manager package versions.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A rabbit checks the package tree,
Two Azure versions now agree.
App Service hops to 1.5.0,
Service Bus follows, 1.2.0.
Neat little updates, clean and bright,
The props file rests just right.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies an Azure SDK dependency update, which matches the package version changes in the pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/azure-azure-sdk-for-net-monorepo

---

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Code Review

This PR is an auto-generated Renovate dependency bump touching only Directory.Packages.props:

• Azure.ResourceManager.AppService: 1.4.1 → 1.5.0
• Azure.ResourceManager.ServiceBus: 1.1.0 → 1.2.0

No application code, logic, or behavior changes are included — this is purely a central-package-management version bump, and no repo code consumes changed/removed APIs from these packages in this diff. No design, architectural, or maintainability concerns apply to a two-line version-string change.

Verdict: LGTM, no issues found.

[claude]

Code review

No issues found. This PR was rebased (new commit a662806) but the change is unchanged in substance from the prior review: a mechanical Renovate bump in Directory.Packages.props only (Azure.ResourceManager.AppService 1.4.1 → 1.5.0, Azure.ResourceManager.ServiceBus 1.1.0 → 1.2.0). No source code is touched, so there's nothing architectural or design-related to flag. Safe to merge pending CI.

[claude]

Code review

No issues found. This remains a mechanical Renovate dependency bump touching only Directory.Packages.props:

• Azure.ResourceManager.AppService: 1.4.1 → 1.5.0
• Azure.ResourceManager.ServiceBus: 1.1.0 → 1.2.0

Verified the diff is still limited to these two version strings (no other files changed). Both are minor version bumps per the release notes (additive features + bug fixes, no breaking changes called out), and no source in this repo directly consumes changed/removed APIs from these packages in this diff, so there's nothing architectural or design-related to flag.

Verdict: LGTM — safe to merge pending CI.

[claude]

Code review

No issues found. The PR was updated (commit 68bf3bd5e3, "fix(deps): retain AppService 1.4.1") to drop the Azure.ResourceManager.AppService bump — the diff is now a single-line, mechanical Renovate version bump in Directory.Packages.props:

• Azure.ResourceManager.ServiceBus: 1.1.0 → 1.2.0

No source code is touched, so there's nothing architectural or design-related to flag.

Verdict: LGTM — safe to merge pending CI.