AzureOpenAIProviderNames

Namespace AgentPrism · Assembly AgentPrism.Azure.dll

The provider name registered by the UseAzureOpenAI call, and the ModelBinding.ProviderSettings keys.

public static class AzureOpenAIProviderNames

Inheritance

object ← AzureOpenAIProviderNames

Inherited Members

object.GetType(), object.MemberwiseClone(), object.ToString(), object.Equals(object?), object.Equals(object?, object?), object.ReferenceEquals(object?, object?), object.GetHashCode()

Remarks

These names are stable. Agent definitions are stored in the database under these names; changing them breaks stored definitions.

The name is azure-openai, not azure: the package may later register another Azure model service, at which point the name azure would no longer say what it refers to.

Fields

AzureOpenAI

The provider that uses the Azure OpenAI Chat Completions endpoint: azure-openai.

public const string AzureOpenAI = "azure-openai"

Field Value

string

SettingsPrefix

The prefix for provider-specific settings: azure-openai.

public const string SettingsPrefix = "azure-openai"

Field Value

string

Properties

SupportedSettings

The setting keys this provider supports. Empty today.

public static IReadOnlyList<string> SupportedSettings { get; }

Property Value

IReadOnlyList<string>

Remarks

The list is deliberately empty. The custom fields Azure lets you add to a chat request (data sources, the max_completion_tokens key) are written through Azure.AI.OpenAI.Chat.AzureChatExtensions; it was measured that all of these extensions throw MissingMethodException at run time against the OpenAI SDK version we use. Offering a setting that doesn’t work is worse than not offering it at all.

Because the list is empty, ModelProviderSettings.Validate rejects any key and says “supports no extra settings” in its message.