Add provider names for newly supported Azure connection string prefixes in EnvironmentVariablesConfigurationProvider

[Copilot]

Follow-up to #116037, which added Azure App Service connection string prefix support but left provider names as null for 5 of the 6 new prefixes.

Changes

• Provider names assigned for the following CONNSTR_ prefixes:

  Prefix	Provider Name
  DOCDBCONNSTR_	Microsoft.Azure.Cosmos
  EVENTHUBCONNSTR_	Azure.Messaging.EventHubs
  NOTIFICATIONHUBCONNSTR_	Microsoft.Azure.NotificationHubs
  REDISCACHECONNSTR_	StackExchange.Redis
  SERVICEBUSCONNSTR_	Azure.Messaging.ServiceBus
  APIHUBCONNSTR_	null (no specific provider)

• Tests updated — LoadsAzureServiceConnectionStrings now asserts _ProviderName values instead of asserting their absence.

Notes

• Provider names map to NuGet package IDs, consistent with the existing convention (MySql.Data.MySqlClient, Npgsql, System.Data.SqlClient).
• Microsoft.Azure.NotificationHubs uses the older SDK namespace. Reviewers should confirm whether Azure.Messaging.NotificationHubs (newer Azure.Messaging.* pattern) is preferred.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Follow-up on provider names for the newly added connection strings to EnvironmentVariablesConfigurationProvider</issue_title>
<issue_description>In #116037, we added support for additional connection string prefixes to EnvironmentVariablesConfigurationProvider. This issue is intended to track whether any provider names need to be associated with the newly supported connection strings.

Below is a list of potential provider names, but they haven't been validated yet. We need to determine whether these are the correct values or if we should continue using null as the provider's name, as we currently do.

• Cosmos DB: Uses REST APIs or SDK (Microsoft.Azure.Cosmos)
• Event Hubs: Uses AMQP protocol (Azure.Messaging.EventHubs)
• Notification Hubs: Uses REST APIs (Microsoft.Azure.NotificationHubs)
• Redis Cache: Uses Redis protocol (StackExchange.Redis)
• Service Bus: Uses AMQP protocol (Azure.Messaging.ServiceBus)
• API Hub: Generic API connections, no specific provider <--- Null provider
  </issue_description>

<agent_instructions>copilot, propose implementation as a draft PR, take a look at the PR mentioned and the discussion in the issue it fixes for context.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@tarekgh https://github.com//issues/36123 https://learn.microsoft.com/en-us/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet#variable-prefixes https://learn.microsoft.com/en-us/cli/azure/webapp/config/connection-string?view=azure-cli-latest#az-webapp-config-connection-string-set @rosebyte Triage: we will take a look when we will have time.

• Fixes Follow-up on provider names for the newly added connection strings to EnvironmentVariablesConfigurationProvider #116226

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[rosebyte]

@copilot , why this one and CustomConnectionStringPrefix one don't have any full key?