Conversation
…ations Add missing maxLength constraints to server-schema.json to match Azure API Center limits that are enforced server-side. Without these schema-level constraints, servers with fields exceeding APIC limits pass local validation but fail during sync — and due to fail-fast batch processing, a single failure blocks all subsequent servers from being created. Schema changes (partners/server-schema.json): - externalDocumentation.title: add maxLength 50 - externalDocumentation.url: add maxLength 200, format uri - license.name: add maxLength 50 - license.url: add maxLength 200, format uri - repository.url: add maxLength 200, format uri - repository.source: add maxLength 100 Server data fixes: - grounding-with-bing-custom-search.json: shorten externalDocumentation.title from 52 to 37 chars (was exceeding 50-char APIC limit, causing cascading failure that blocked grounding-with-bing-search, sharepoint-grounding, web-search, and all later servers) - azure-mcp-server.json: trim useCases[0].description from 1001 to 988 chars (exceeding existing 1000-char maxLength constraint) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
lindazqli
approved these changes
Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
server-schema.jsonis missing severalmaxLengthconstraints that Azure API Center enforces server-side. When server JSON files contain fields that exceed these undocumented limits, the APIC REST API returns 4xx errors during sync. Due to the fail-fast batch processing in the sync pipeline, a single server's field violation blocks ALL subsequent servers from being created/updated.Impact observed
grounding-with-bing-custom-search.jsonhasexternalDocumentation.title= 52 characters (APIC limit: 50). Since servers are processed alphabetically in batches, this failure cascades and blocks:grounding-with-bing-search(same batch)sharepoint-grounding(later batch)web-search(later batch)Changes
Schema changes (
partners/server-schema.json)Added missing
maxLengthconstraints to match APIC enforcement:externalDocumentation.titlemaxLength: 50externalDocumentation.urlmaxLength: 200,format: urilicense.namemaxLength: 50license.urlmaxLength: 200,format: urirepository.urlmaxLength: 200,format: urirepository.sourcemaxLength: 100Server data fixes
grounding-with-bing-custom-search.jsonexternalDocumentation.titleazure-mcp-server.jsonuseCases[0].descriptionValidation
All 67 server JSON files pass validation against the updated schema.