m-nash

Configuration Schema Differences: Microsoft.Extensions.Azure (Old) vs New Config System

Configuration Schema Differences: Microsoft.Extensions.Azure (Old) vs New Config System

Configuration Schema Differences: Microsoft.Extensions.Azure (Old) vs New Config System

This document catalogs every difference between the configuration schema used by the old Microsoft.Extensions.Azure client registration system and the new IConfigurationSection-based system being built. Each finding includes links to the relevant source code in the

m-nash

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "Azure.Identity Credential Definitions",
  "definitions": {
    "credential": {
      "type": "object",
      "description": "Credential configuration. Available properties depend on the selected CredentialSource.",
      "properties": {
        "CredentialSource": {
          "type": "string",

m-nash

JSON Schema IntelliSense for Azure SDK Client Configuration

Issue: Azure/azure-sdk-for-net#55538

Problem

When customers configure Azure SDK clients via appsettings.json, they get no IntelliSense or validation for well-known sections like Credential, Retry, and Diagnostics. ASP.NET Core customers expect this to "just work" — the same way Logging, Kestrel, and other ASP.NET sections already get IntelliSense via .NET Aspire's JsonSchemaSegment approach.

Approach: JsonSchemaSegment via NuGet