chore(deps): update dependency microsoft.azure.webjobs.extensions.signalrservice to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.Azure.WebJobs.Extensions.SignalRService (source)	1.12.0 -> 2.1.0

---

Release Notes

Azure/azure-sdk-for-net (Microsoft.Azure.WebJobs.Extensions.SignalRService)

v2.1.0

Compare Source

2.1.0 (2025-07-25)

Features Added

• Enable retry policy for HTTP requests with transient errors by default.

Other Changes

• Upgrade Microsoft.Extensions.Azure to 1.12.0.

v2.0.1

Compare Source

2.0.1 (2025-03-12)

Bugs Fixed

• Fix SignalR trigger completion message serialization for dotnet-isolated worker.

v2.0.0

Compare Source

2.0.0 (2025-03-11)

Breaking Changes

• Modify AddDefaultAuth method in SignalRFunctionsHostBuilderExtensions.cs to use IServiceCollection instead of IFunctionsHostBuilder to remove the dependency for legacy package Microsoft.Azure.Functions.Extensions.

Bugs Fixed

• Correctly support returning result for SignalR invocation in MessagePack protocol from isolated-worker process.

Other Changes

• Update MessagePack to 2.5.192
• Update Microsoft.Azure.SignalR, Microsoft.Azure.SignalR.Management, Microsoft.Azure.SignalR.Protocols to 1.29.0

v1.15.0

Compare Source

1.15.0 (2025-08-07)

Breaking Changes

Behavioral Breaking Changes

• Deprecated SharedTokenCacheCredential. The supporting credential (SharedTokenCacheCredential) was a legacy mechanism for authenticating clients using credentials provided to Visual Studio. For brokered authentication, consider using InteractiveBrowserCredential instead. The following changes have been made:
  • SharedTokenCacheCredential class is marked as [Obsolete] and [EditorBrowsable(EditorBrowsableState.Never)]
  • SharedTokenCacheCredentialOptions class is marked as [Obsolete] and [EditorBrowsable(EditorBrowsableState.Never)]
  • DefaultAzureCredentialOptions.ExcludeSharedTokenCacheCredential property is marked as [Obsolete] and [EditorBrowsable(EditorBrowsableState.Never)]
  • SharedTokenCacheUsername property is marked as [Obsolete] and [EditorBrowsable(EditorBrowsableState.Never)]
  • SharedTokenCacheCredential is no longer included in the DefaultAzureCredential authentication flow

Bugs Fixed

• Tenant ID comparisons in credential options are now case-insensitive. This affects AdditionallyAllowedTenants values which will now be matched against tenant IDs without case sensitivity, making the authentication more resilient to case differences in tenant IDs returned from WWW-Authenticate challenges (#​51693).

Other Changes

• BrokerAuthenticationCredential has been renamed as BrokerCredential.

• Added the EditorBrowsable(Never) attribute to property VisualStudioCodeTenantId as TenantId is preferred. The VisualStudioCodeTenantId property exists only to provide backwards compatibility.

v1.14.1

Compare Source

1.14.1 (2025-07-08)

Bugs Fixed

• Added support in AzurePowerShellCredential for the Az.Accounts 5.0.0+ (Az 14.0.0+) breaking change where Get-AzAccessToken returns PSSecureAccessToken with a SecureString Token property instead of plaintext.

v1.14.0

Compare Source

1.14.0 (2025-05-13)

Other Changes

• Removed references to Username, Password, AZURE_USERNAME, and AZURE_PASSWORD in XML comments from EnvironmentCredentialOptions and EnvironmentCredential due to lack of MFA support. See MFA enforcement details.
• Marked AZURE_USERNAME and AZURE_PASSWORD as obsolete due to lack of MFA support. See MFA enforcement details.
• Added support for the AZURE_TOKEN_CREDENTIALS environment variable to DefaultAzureCredential, which allows for choosing between 'deployed service' and 'developer tools' credentials. Valid values are 'dev' for developer tools and 'prod' for deployed service.

v1.13.0

Compare Source

1.13.0 (2024-10-14)

Features Added

• ManagedIdentityCredential now supports specifying a user-assigned managed identity by object ID.

Bugs Fixed

• If DefaultAzureCredential attempts to authenticate with the MangagedIdentityCredential and it receives either a failed response that is not json, it will now fall through to the next credential in the chain. #​45184
• Fixed the request sent in AzurePipelinesCredential so it doesn't result in a redirect response when an invalid system access token is provided.
• Updated to version 4.65.0 of Microsoft.Identity.Client to address a bug preventing the use of alternate authority types such as dStS (4927) .

Other Changes

• The logging level passed to MSAL now correlates to the log level configured on your configured AzureEventSourceListener. Previously, the log level was always set to Microsoft.Identity.Client.LogLevel.Info.
• AzurePowerShellCredential now utilizes the AsSecureString parameter to Get-AzAccessToken for version 2.17.0 and greater of the Az.Accounts module.
• Improved error logging for AzurePipelinesCredential.

---

Configuration

📅 Schedule: 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.