Updating stable release branch by jeremyfrosti · Pull Request #41047 · Azure/azure-rest-api-specs

jeremyfrosti · 2026-03-05T19:09:53Z

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

New resource provider.
New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
Update existing version to fix OpenAPI spec quality issues in S360.
Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
Other, please clarify:
- edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.
For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

github-actions · 2026-03-05T19:10:41Z

Next Steps to Merge

Next steps that must be taken to merge this PR:

❌ The suppressions added to the AutoRest config files (README.mds) require review. Refer to step 1 in the PR workflow diagram, or to step 3, depending on the kind of suppression you did.

Important checks have failed. As of today they are not blocking this PR, but in near future they may.
Addressing the following failures is highly recommended:

⚠️ The check named SDK Validation Status has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

Comment generated by summarize-checks workflow run.

* Add Azure Linux 4.0 Image aliases * Add cspell.yaml for spell check handling

* fix purge date bug * added else --------- Co-authored-by: Marcos Salamanca <masalama@microsoft.com>

Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

…rp (#42878) The unscoped @@clientName decorators were renaming startIpAddress to startIPAddress for all languages, causing a breaking change in Java SDK. Scope these renames to csharp only so other languages keep the original camelCase property names. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* init * sql instance changes * updating readme * updates * updating api version in jsons * moving to preview * adding sql instance changes * readme update * taking base as 2025-08-01 * merging 2025-02-28-preview changes * adding sql instance snapshot backup changes * VaultName parameter fix * fixing json * updating main.tsp * updating examples * updating .tsp files and bms.json based on tsp npx tsv cmd * adding versioning * updates * updates * fixing js sdk validation * reverting last commit * removing VaultNameParameter * Add C# clientName decorators for acronym casing and contextual naming fixes --------- Co-authored-by: chandrikagonuguntla <chandrikagonuguntla@users.noreply.github.com>

…vel, SourceSideScanStatus, SourceSideScanSummary, VMWorkloadPolicyType) (#42918)

This skill and its eval cases have been moved to the azure-sdk-tools repo.

update python client name and here is namespace review result Azure/azure-sdk#9492

* visibility workaround for monitor accounts * Update client.tsp

@added

* Add ServiceBus 2026-01-01 stable API version with ipV6Enabled and dnsNamePolicy Add new stable API version 2026-01-01 for Microsoft.ServiceBus based on 2025-05-01-preview. Adds ipV6Enabled and dnsNamePolicy properties to SBNamespaceProperties using @added versioning decorators. Includes generated OpenAPI spec and examples. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Rename servicebus.json to openapi.json for naming consistency Rename output file from servicebus.json to openapi.json in tspconfig.yaml for consistency across EventHub and ServiceBus specs. Updated readme.md references accordingly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert "Rename servicebus.json to openapi.json for naming consistency" This reverts commit 3919b92. * Rename stable output to openapi.json for cross-version compatibility Rename ServiceBus 2026-01-01 output from servicebus.json to openapi.json to avoid false cross-version breaking change comparison against deprecated 2015-08-01 servicebus.json. Preview files remain unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Rename stable 2026-01-01 output to openapi.json, keep tspconfig unchanged Manually rename stable/2026-01-01/servicebus.json to openapi.json to avoid false cross-version breaking change comparison against deprecated 2015 specs. tspconfig.yaml remains unchanged (servicebus.json) to keep preview consistent. Added TypeSpecValidation suppression for the renamed stable file. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert to servicebus.json naming for stable output Revert stable output to servicebus.json to pass TypeSpec Validation and LintDiff checks. Cross-version breaking change approval will be obtained separately via aka.ms/brch. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove dnsNamePolicy, rename to openapi.json for 2026-01, add ipV6Enabled examples - Remove DnsNamePolicy union and property from models.tsp - Rename stable/2026-01-01/servicebus.json to openapi.json - Update readme.md package-2026-01 tag to reference openapi.json - Add ipV6Enabled to SBNameSpaceCreate, Update, Get examples - Add new SBNamespaceCreateWithIpV6Enabled.json example Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove dnsNamePolicy, rename to openapi.json for 2026-01, add ipV6Enabled examples - Remove DnsNamePolicy union and property from models.tsp - Rename stable/2026-01-01/servicebus.json to openapi.json - Update readme.md package-2026-01 tag to reference openapi.json - Add ipV6Enabled to SBNameSpaceCreate, Update, Get examples - Add new SBNamespaceCreateWithIpV6Enabled.json example Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Corrections * Corrections * adding justifications to suppression * Changed Tags From SBNamespaces -> Namespaces * Changed Tags From SBqueues -> queues * Changed Tags From SBTopics -> Topics * Changed Tags From SBSubscription -> Subscriptions * Changed Tags From SBAuthorizationRule-> Namespace AuhorizationRule * Changed Tags From SBAuthorizationRule-> Namespace AuhorizationRule * Enable compatibility-lro in tspconfig.yaml --------- Co-authored-by: Ashraf Siddiquee <asiddiquee@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Shubham Chaudhari <schaudhari@microsoft.com> Co-authored-by: ZiWei Chen <98569699+kazrael2119@users.noreply.github.com>

* added dotnet specific ovverides for EKM clients --------- Co-authored-by: Hari K <kha@microsoft.com> Co-authored-by: Mike Harder <mharder@microsoft.com>

@visibility

* Add Chaos Studio 2026-05-01-preview API version Port Chaos Studio specification from azure-rest-api-specs-pr (renzo/addPermissionFix branch, based on 2026-02-01-preview). Adds new resources: Workspaces, Scenarios, ScenarioConfigurations, ScenarioRuns, DiscoveredResources, WorkspaceOperationResults, and FixResourcePermissions support. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add RefreshRecommendationsResult model for refreshRecommendations LRO - Add RefreshRecommendationsResult, RefreshRecommendationsTask, RefreshRecommendationsTaskKind, and RefreshRecommendationsTaskError models - Change refreshRecommendations return type from Workspace to RefreshRecommendationsResult - Add documentation to WorkspaceOperationResults interface - Regenerate openapi.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Restore Target.location x-ms-mutability visibility Restore @visibility(Lifecycle.Create, Lifecycle.Read) on Target.location that was unintentionally removed. This is unrelated to fixResourcePermissions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix example validation and add missing x-ms-examples - Remove invalid 200 responses from Execute and Validate examples - Add missing 202 responses to GetLatestValidation and ScenarioRuns_Get examples - Create ScenarioRuns_Cancel example - Add x-ms-examples for GetLatestPermissionsFix and ScenarioRuns_Cancel in openapi.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: resolve API spec CI check failures and review comments ModelValidation fixes: - Remove Azure-AsyncOperation header from Experiments_Delete (LRO uses Location only) - Remove Azure-AsyncOperation header from Workspaces_Delete (LRO uses Location only) - Fix ScenarioConfigurations_Validate headers (capitalize, remove async-op, add api-version) - Fix ScenarioConfigurations_Execute polling URL path (/configurations/ not /scenarioConfigurations/) LintDiff/Review fixes: - Fix nextLink api-version in Experiments_ListAllExecutions (2025-01-01 → 2026-05-01-preview) - Fix 'header' → 'headers' in PrivateAccesses_CreateOrUpdate example - Fix privateEndpoinConnections typo → privateEndpointConnections TypeSpec fixes: - Fix KeyValuePair doc comment grammar ('parameters actions' → 'parameters for actions') - Fix WorkspaceUpdate doc comment copy-paste ('experiment' → 'workspace') - Remove duplicate @added decorator on requiredAzureRoleDefinitionIds Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: resolve API spec CI check failures and review comments ModelValidation fixes: - Add missing x-ms-examples for ScenarioConfigurations_GetLatestPermissionsFix - Fix operationId mismatch (GetLatestPermissionFix → GetLatestPermissionsFix) - Add source example file to TypeSpec examples directory - Remove Azure-AsyncOperation header from Experiments_Delete (Location-only LRO) - Remove Azure-AsyncOperation header from Workspaces_Delete (Location-only LRO) - Fix ScenarioConfigurations_Validate headers (capitalize, remove async-op, add api-version) - Fix ScenarioConfigurations_Execute polling URL path (/configurations/ not /scenarioConfigurations/) Review comment fixes: - Fix nextLink api-version in Experiments_ListAllExecutions (2025-01-01 → 2026-05-01-preview) - Fix 'header' → 'headers' in PrivateAccesses_CreateOrUpdate example - Fix privateEndpoinConnections typo → privateEndpointConnections - Fix KeyValuePair doc comment grammar ('parameters actions' → 'parameters for actions') - Fix WorkspaceUpdate doc comment copy-paste ('experiment' → 'workspace') Note: Kept dual @added decorators on requiredAzureRoleDefinitionIds — both are required because the version enum order is v2024 → v2026-preview → v2025-stable. Regenerated openapi.json via tsp compile. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: resolve LintDiff and Protected Files CI failures - Remove accidentally included eng/tools/lint-diff/vite.config.js (Protected Files check) - Update @armCommonTypesVersion from v5 to v6 (LatestVersionOfCommonTypesMustBeUsed) - Regenerate openapi.json for all API versions with common-types v6 references Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: revert common-types v6, add suppressions, fix review comments Revert @armCommonTypesVersion v5→v6 change: - v6 introduced breaking changes in already-shipped API versions (2024-11-01-preview, 2025-01-01) by changing ManagedServiceIdentity model structure - Reverted to v5 to preserve backward compatibility Add LintDiff suppression for LatestVersionOfCommonTypesMustBeUsed: - TypeSpec @armCommonTypesVersion is namespace-level, cannot be per-version - Upgrading would break shipped API versions Fix review comments: - Fix lowercase header keys in ScenarioRuns_Cancel.json (location → Location) - Add ?api-version= to polling URLs in ScenarioRuns_Cancel.json - Fix lowercase header keys in ScenarioConfigurations_Validate.json - Add ?api-version= to polling URLs in ScenarioConfigurations_Validate.json - Fix privateEndpoinConnections typo in PrivateAccesses_ListPrivateEndpointConnections.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: suppress PathForTrackedResourceTypes, move whatIf to request body - Add LintDiff suppression for PathForTrackedResourceTypes on WorkspaceOperationResults (LRO polling endpoint, not a resource CRUD path) - Move whatIf from @query parameter to FixResourcePermissionsRequest body model on fixResourcePermissions POST operation (RPC-Post-V1-05) - Regenerate openapi.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add correct LRO response codes for POST operations (PostResponseCodes) Update 5 POST LRO operations to comply with RPC-Async-V1-11/V1-14 and RPC-POST-V1-02/V1-03 response code requirements: Operations returning a body on completion (200 + 202 + default): - ScenarioConfigurations_Validate → returns Validation resource - ScenarioConfigurations_FixResourcePermissions → returns PermissionsFix resource Operations returning no body on completion (204 + 202 + default): - Workspaces_RefreshRecommendations → async fire-and-forget - ScenarioConfigurations_Execute → creates run, poll via Location - ScenarioRuns_Cancel → poll run state via Location Added ArmResourceActionNoBodyAsyncWithLocation template to lro-helpers.tsp for the 204 pattern. Updated example JSON for fixResourcePermissions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: resolve TypeSpec Validation, ModelValidation, and LintDiff failures TypeSpec Validation (--warn-as-error): - Add #suppress for arm-post-operation-response-codes on 6 operations using custom LRO templates (not recognized by TypeSpec ARM linter) - Add #suppress for polling-operation-no-status-monitor on getLatestPermissionsFix (LRO uses final-state-via:location pattern) ModelValidation (RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE): - Add 204 response to RefreshRecommendations, Execute, Cancel examples - Add 200 response with Validation body to Validate example - Fix lowercase Location header in Execute example LintDiff: - Add suppression for PostOperationIdContainsUrlVerb (Experiments_ExecutionDetails name established in prior API versions) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: correct Validate example properties (startedAt/completedAt, remove validatedAt) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: wire RefreshRecommendationsResult to refreshRecommendations operation Change refreshRecommendations from ArmResourceActionNoBodyAsyncWithLocation (returning void/204) to ArmResourceActionNoContentAsyncWithLocationResult (returning RefreshRecommendationsResult from Location URL). The RefreshRecommendationsResult models were already defined but not referenced by the operation. This wires them up so the SDK generates the correct return type. Cherry-picked from azure-rest-api-specs-pr PR#25753 (commits 179991539c4, 7f62e8e81b7). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add api-version to http-client-csharp-mgmt emitter config Without api-version specified, the mgmt emitter defaults to the latest version (v2025_01_01 stable) where Workspace resources are @removed. This means Workspace operations including refreshRecommendations are not generated in the .NET SDK. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert "fix: add api-version to http-client-csharp-mgmt emitter config" This reverts commit 7903975. * fix: use ArmResourceActionAsyncWithLocation for refreshRecommendations Switch from ArmResourceActionNoContentAsyncWithLocationResult (202-only) to ArmResourceActionAsyncWithLocation (200+202) to satisfy the PostResponseCodes lint rule (RPC-Async-V1-11, RPC-POST-V1-02). The 200 response declares the RefreshRecommendationsResult schema that clients receive when polling completes. Updated example with sample RefreshRecommendationsResult body. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * style: apply tsp format to lro-helpers.tsp and scenarioRun.tsp Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add LintDiff suppressions to readme.md for Workspace false positives The suppressions.yaml format was not being picked up by the LintDiff CI check. Move suppressions to readme.md under the package-2026-05-01-preview tag where the proven code/from/where format works. Suppressed rules: - PathForTrackedResourceTypes: WorkspaceOperationResults is an LRO polling endpoint, not a tracked resource path - AllTrackedResourcesMustHaveDelete: Workspace has Workspaces_Delete - TrackedResourcePatchOperation: Workspace has Workspaces_Update with tags Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add clientName renames for listAll to avoid mgmt emitter collision The mgmt emitter generates duplicate GetAll method names when both list (by resource group) and listAll (by subscription) exist. Add @@clientName renames for PrivateAccesses.listAll and Workspaces.listAll matching the existing pattern for Experiments.listAll. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: rename WorkspaceOperationResults.get to avoid method collision WorkspaceOperationResults.get and OperationStatuses.get both generate Get(string location, string operationId) on MockableChaosSubscriptionResource. Rename to getWorkspaceOperationResult for csharp to disambiguate. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: rename models to satisfy AZC0030 naming conventions - FixResourcePermissionsRequest → ChaosFixResourcePermissionsRequestContent - ScenarioParameter → ChaosScenarioParameterContent Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: align property names and response codes with implementation ScenarioRunProperties: - state → status - startedAt → startTime, completedAt → endTime - errors → executionErrors ValidationProperties: - state → status - startedAt → startTime, completedAt → endTime - errors → validationErrors Response codes (all POST LROs now 202-only): - Workspaces_RefreshRecommendations: 200+202 → 202 - ScenarioConfigurations_Execute: 202+204 → 202 - ScenarioConfigurations_Validate: 200+202 → 202 - ScenarioRuns_Cancel: 202+204 → 202 All operations use ArmResourceActionNoContentAsyncWithLocationResult template matching the private repo implementation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: RefreshRecommendations returns 200+202 per ARM Gateway analysis RefreshRecommendations returns 200 with RefreshRecommendationsResult body on completion, plus 202 with Location header initially. The other three POST LROs (Execute, Validate, Cancel) remain 202-only. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add 200 response to Execute, Validate, and Cancel POST LROs All POST LRO operations return a body when polling completes via the Location URL, so they need 200 (with schema) + 202 response codes to satisfy PostResponseCodes lint rule and accurately represent the LRO contract. - Execute: 200 returns ScenarioRun - Validate: 200 returns Validation - Cancel (ScenarioRuns): 200 returns ScenarioRun - Cancel (ScenarioConfigurations): 200 returns OperationStatusResult - RefreshRecommendations: already had 200+202 All now use ArmResourceActionAsyncWithLocation template. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: revert to 202-only for Execute, Validate, Cancel; suppress PostResponseCodes These operations return 202 with a Location header for polling. The final result is obtained by polling the Location URL. Suppress the PostResponseCodes LintDiff rule in readme.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * style: apply tsp format to client.tsp Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: Private Preview Polling Pivot — replace RefreshRecommendationsResult with evaluations/latest and discoveries/latest Port commits b36ebc9 and 8f011f3 from azure-rest-api-specs-pr PR#25753. - Add WorkspaceEvaluation and WorkspaceDiscovery singleton resources - Remove RefreshRecommendationsResult and related models - Update refreshRecommendations to poll WorkspaceEvaluations.getLatest - Update WorkspaceOperationResults comments - Rename ScenarioParameter clientName to ChaosScenarioParameterInfo - Fix experimentExecution.tsp $ref formatting - Add example files for new endpoints - Add readme.md suppressions for singletons Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add filters to ScenarioConfigurations_CreateOrUpdate examples Add filters (locations + zones) to the ScenarioConfiguration CreateOrUpdate example JSON in both example directories. Ported from azure-rest-api-specs-pr PR #25753. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add Evaluating, EvaluationFailed, EvaluationCancelled to Recommendati… (#42241) * Add Evaluating, EvaluationFailed, EvaluationCancelled to RecommendationStatus union Add three new status values to the RecommendationStatus union in scenario.models.tsp to support tracking in-progress and terminal evaluation states for scenario recommendations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add Evaluating, EvaluationFailed, EvaluationCancelled to RecommendationStatus union Add three new status values to the RecommendationStatus union in scenario.models.tsp to support tracking in-progress and terminal evaluation states for scenario recommendations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Aparna Amarnath <apamarnath@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Brrusino/chaos read only actions (#42192) * Add read-only location-based Action resources for 2026-05-01-preview - Add Action and ActionVersion proxy resources at subscription+location scope - Follow existing TargetType pattern (GET + LIST only, read-only) - Add ActionKind extensible enum (Discrete, Continuous, Cancelable) - Add actionResourceId optional field to ScenarioAction - Add example JSON files for all 4 new operations - Add csharp client names and flatten directives for new types Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix actionResourceId to reference version-specific resource Update actionResourceId description and examples to use the full action version path (.../actions/{actionName}/versions/{version}) instead of the parent action path. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix URN from virtualMachine:shutdown to compute:Shutdown in 2026-05-01-preview examples Corrected all references to use the canonical URN urn:csci:microsoft:compute:Shutdown/1.0 and updated actionResourceId paths to use microsoft-compute-shutdown. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert V1 resource examples to legacy URN V1 resources (Experiments, Capabilities, CapabilityTypes) use the legacy URN format (urn:csci:microsoft:virtualMachine:shutdown/1.0). Only V2 resources (Actions, ActionVersions, Scenarios) use the corrected URN (urn:csci:microsoft:compute:Shutdown/1.0). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add missing Action TypeSpec and example files These files were not included in the original commit due to CRLF line-ending issues. Fixed line endings and added: - action.models.tsp and action.tsp - Example JSON files for Actions and ActionVersions operations Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Replace urn/actionResourceId/targetTypes with actionId in ScenarioAction ScenarioAction for 2026-05-01-preview now uses a single actionId field (e.g., 'microsoft-compute-shutdown/1.0') instead of the separate urn, actionResourceId, and targetTypes fields. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Replace urn with canonicalId in Action and ActionVersion properties Use canonicalId (e.g., 'microsoft-compute-shutdown/1.0') instead of the legacy URN format in ActionProperties and ActionVersionProperties. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Run prettier and tsp format on Chaos files Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix prettier formatting in generated Scenario examples Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Consolidate ActionVersionProperties into ActionProperties Both Action and ActionVersion resources now share a single ActionProperties model instead of having duplicate definitions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: make fixResourcePermissions POST request body optional Remove the body from the example to reflect that the request body is optional (the ArmResourceActionAsyncWithLocation template already marks it as body?: Request which generates required: false in OpenAPI). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * style: run tsp format on client.tsp Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add physical zone targeting and zone resolution info to Chaos Studio spec - Add physicalZones field to ConfigurationFilters in scenarioConfiguration.models.tsp - Add ZoneResolutionInfo and ZoneResolutionMode models to scenarioRun.models.tsp - Add zoneResolution property to ScenarioRunProperties - Update ScenarioConfigurations_Get example with physicalZones in filters - Update ScenarioRuns_Get example with zoneResolution in response - Add new ScenarioConfigurations_CreateOrUpdate_With_Physical_Zones example - Regenerate openapi.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove additionalProperties from Action.parametersSchema Change parametersSchema type from Record<unknown> to empty model {} to remove the additionalProperties:{} from the generated OpenAPI spec. The field remains a free-form JSON object but without the unnecessary additionalProperties constraint. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update scenarioRun models and ScenarioRuns_Get example Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add Queued to WorkspaceEvaluationStatus enum (#42341) The BE returns 'Queued' as a valid evaluation status when a job is accepted but hasn't started running. This value was missing from the TypeSpec union, causing the GW's enum-typed model to silently fall back to 'Pending' on 2026-05-01-preview. Co-authored-by: REDMOND\xuefl <xuefl@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove duplicate @added decorator from requiredAzureRoleDefinitionIds The field was first introduced in v2025_01_01; the redundant @added(v2026_05_01_preview) decorator has been removed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Restore @added(v2026_05_01_preview) on requiredAzureRoleDefinitionIds The version enum orders v2026_05_01_preview before v2025_01_01, so both decorators are needed to include this field in both specs independently. The Copilot review suggestion to remove the duplicate was incorrect. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add missing enum values and restore errors property for 2026-05-01-preview (#42374) * Add missing enum values: ScenarioRunState (Queued, ValidationSucceeded), WorkspaceDiscoveryStatus (Queued), WorkspaceEvaluationStatus (PartiallySucceeded) Cross-referenced BE domain model enums against TypeSpec definitions and found missing values that cause MapEnumValue to silently fall back to defaults. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add missing errors (OperationError[]) to ValidationProperties and ScenarioRunProperties Both models had errors?: OperationError[] in V2026_02_01_preview but it was accidentally dropped in V2026_05_01_preview. This property carries system/infrastructure errors (e.g., ScenarioExecutionRbacValidationError) separate from the business errors in validationErrors/executionErrors (ScenarioErrors). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: REDMOND\xuefl <xuefl@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update ScenarioRun models/examples and fix PR review issues From Downloads: - Update scenarioRun.models.tsp with latest zone resolution models - Update ScenarioRuns_Get.json example PR review fixes: - Fix 'header' -> 'headers' in PrivateAccesses CreateOrUpdate example (200 and 201 responses) - Fix ScenarioRuns_Get 202 response: 'location' -> 'Location', add api-version to polling URL; remove empty headers from 200 - Change workspace.models.tsp scopes from string[] to armResourceIdentifier[] - Change scenarioConfiguration.models.tsp scenarioId from string to armResourceIdentifier - Change ConfigurationExclusions.resources from string[] to armResourceIdentifier[] - Regenerate openapi.json Note: Workspaces_Delete kept as ArmResourceDeleteWithoutOkAsync per TypeSpec ARM framework guidance (ArmResourceDeleteAsync is deprecated and the lint rule explicitly prohibits 200 on async delete operations). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add 200 response to Workspaces_Delete per RPC-Delete-V1-03 Switch Workspaces.delete from ArmResourceDeleteWithoutOkAsync to ArmResourceDeleteAsync to satisfy the ARM reviewer requirement that DELETE operations include a 200 response (alongside 202, 204, default). Suppress the deprecation warning with a comment explaining the reason. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: update Workspaces_Delete 204 description to 'No Content' Define WorkspaceDeleteNoContentResponse with 'No Content' description instead of the default 'Resource does not exist.' Use ArmResourceDeleteAsyncBase with explicit response union to control the 204 description per ARM reviewer feedback on RPC-Delete-V1-03. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chore: retrigger CI checks Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add 200 response to Workspaces_Delete example oav validation requires all spec-defined response codes to appear in x-ms-examples. Add empty 200 response to satisfy the check. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add 200 response to source example for Workspaces_Delete The CI regenerates the generated examples from the source examples/ directory. Need to update both the source and generated copy. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: remove 200 response from Workspaces_Delete to satisfy DeleteResponseCodes rule LRO delete operations must only have 202, 204, and default responses. Keep custom WorkspaceDeleteNoContentResponse for correct 204 description. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add SettingUp status to ScenarioRunState (#42426) * Add SettingUp status to ScenarioRunState enum Add SettingUp enum value to ScenarioRunState union in scenarioRun.models.tsp, representing the setup phase between Starting and Running in the scenario run lifecycle. Regenerated openapi.json to include the new enum value. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add CleaningUp status to ScenarioRunState enum Add CleaningUp enum value to ScenarioRunState union after Running and before Canceling, representing the cleanup phase in the scenario run lifecycle. Updated lifecycle: ... -> SettingUp -> Running -> CleaningUp -> Canceling -> terminal states Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Shankar Daruga <sdaruga@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix ScenarioAction parameters and duration types for 2026-05-01-preview (#42539) * Fix scenario action parameters to use KeyValuePair and add template syntax - Change ScenarioAction.parameters from ScenarioParameter[] to KeyValuePair[] to align with experiment action parameters and BE faultParameters format - Update all scenario examples (CreateOrUpdate, Get, ListAll) to use realistic Zone Down scenario with template expressions (%%{parameters.*}%%, %%{filters.*}%%) matching BE static content format - Action metadata (type, required, description) now only lives in the read-only Action resource, not in scenario action definitions Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Change ScenarioAction duration fields from duration to string (Bug #37620364) ScenarioAction.duration, waitBefore, and timeout fields support template macro syntax (%%{parameters.<name>}%%) which gets resolved at execution time. The duration type generates System.TimeSpan in C# models, which cannot hold template strings and causes FormatException crashes. Scoped to V2 resources (2026-05-01-preview) only: - ScenarioAction: duration, waitBefore, timeout V1 experiment models (ContinuousAction, DelayAction) are unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address PR review comments - Add string variant back to ProvisioningState union - Change recommendedRoles to uuid type - Change resourceId to armResourceIdentifier type - Update ARM references to Azure in model descriptions - Move LintDiff suppressions from suppressions.yaml to readme.md with where: jsonpath scoping Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Replace test substitution placeholder with valid arm-id in Scenarios examples The customRunbook1ResourceId placeholder %%{parameters.customRunbook1ResourceId}%% failed arm-id format validation after resourceId was retyped to armResourceIdentifier. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove redundant @added decorator for requiredAzureRoleDefinitionIds Keep only the earliest version (v2025_01_01) where the property first appears. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert "Remove redundant @added decorator for requiredAzureRoleDefinitionIds" This reverts commit 8110cea. * Fix fixResourcePermissions LRO template to declare 202-only response Switch from ArmResourceActionAsyncWithLocation (which declares 200+202) to ArmResourceActionNoContentAsyncWithLocationResult (202-only) so the C# emitter no longer generates eager-deserialize code that crashes with JsonException on the empty 202 body. Brings fixResourcePermissions in line with validate, execute, and refreshRecommendations on ScenarioConfiguration, which already use the correct template. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: remove extra 200 response from fixResourcePermissions to match tsp compile output Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Suppress PostResponseCodes and GuidUsage lint errors for 2026-05-01-preview - PostResponseCodes: fixResourcePermissions LRO POST returns 202 with Location header - GuidUsage: Azure.Core.uuid approved by ARM API reviewer Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix GuidUsage suppression: target .format property Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address PR review: remove /latest endpoints, workspaceOperationResults, fix delete responses, lowercase headers - Remove WorkspaceOperationResults GET endpoint and delete .tsp file - Remove WorkspaceEvaluations, WorkspaceDiscoveries /latest GET endpoints and delete .tsp files - Remove getLatestValidation and getLatestPermissionsFix from ScenarioConfigurations - Remove @pollingOperation decorators referencing removed endpoints - Fix Workspaces_Delete to include 200+202+204 responses for proper ARM DELETE semantics - Lowercase Location and Azure-AsyncOperation headers in all example files Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix Workspaces_Delete to return only 202+204 (remove 200) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Rename SettingUp to Preparing in ScenarioRunState enum (#42780) Renames the SettingUp enum value to Preparing in the ScenarioRunState union for a more generalized lifecycle phase name. Co-authored-by: Shankar Daruga <sdaruga@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add endpoint property to WorkspaceProperties (#42788) Adds a read-only endpoint property to the Workspace model so that Chaos agents can discover the base URL they need to connect to and communicate with a workspace. Co-authored-by: Shankar Daruga <sdaruga@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Rename endpoint to communicationEndpoint in WorkspaceProperties (#42810) Renames the endpoint property to communicationEndpoint for clarity. This is the communication endpoint used to connect and communicate with the workspace for fault-injection orchestration. Co-authored-by: Shankar Daruga <sdaruga@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove suppressions for definitions/paths that no longer exist Remove 5 suppressions from the 2026-05-01-preview tag that target definitions or paths no longer present in the openapi.json: - PathForTrackedResourceTypes on workspaceOperationResults (path removed) - NestedResourcesMustHaveListOperation on WorkspaceDiscovery (definition removed) - NestedResourcesMustHaveListOperation on WorkspaceEvaluation (path removed) - PathForNestedResource on evaluations/latest (path removed) - PathForNestedResource on discoveries/latest (path removed) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: aamarnath12 <aamarnath12@gmail.com> Co-authored-by: Aparna Amarnath <apamarnath@microsoft.com> Co-authored-by: Brent Rusinow <44413020+brrusino@users.noreply.github.com> Co-authored-by: Frank Li <frankvsense@gmail.com> Co-authored-by: REDMOND\xuefl <xuefl@microsoft.com> Co-authored-by: Shankar Daruga <dmvs000@gmail.com> Co-authored-by: Shankar Daruga <sdaruga@microsoft.com>

* bump to 2026-03-01 * tsp * tsv compile again * BreakthroughMode fix mutablitity in preview

Co-authored-by: Vikeshi Tiwari <vikestiwari@microsoft.com> Co-authored-by: Tejaswi Salaigari <tsalaigari@microsoft.com>

…ResilienceManagement (#43430) Co-authored-by: Vikeshi Tiwari <vikestiwari@microsoft.com>

…43432) * Add ARM modeling lease for Microsoft.DeviceUpdate/DuDeviceRegistry * Add ARM modeling lease for Microsoft.Migrate/NetworkAssessments --------- Co-authored-by: Vikeshi Tiwari <vikestiwari@microsoft.com>

…ython avatar_type (#43437) Co-authored-by: Xiting Zhang <xitzhang@microsoft.com>

* Copy fleet-2026-02-01-preview to fleet-2026-03-02-preview. * Initial changes for fleet-2026-03-02-preview release (#40256) * [fleet] Adding mesh member property to fleet member api (#39540) * adding mesh member typespec definition * added meshmember model to fleetmember * adjusted provisioning state * fixed meshmember model definition to not be a resource * removed incorrect name field from mesh member property * removed excess imports * final fixes * ran tsp compile * rename mesh member state property Co-authored-by: dvadas <davidvadas@microsoft.com> * applying suggested changes * adjusted doc line for mesh member prop --------- Co-authored-by: dvadas <davidvadas@microsoft.com> * Delete 2025-08-02-clustermesh version of fleets.json * Add clustermeshprofile.tsp and meshmember.tsp. * Ran tsp format. * Add examples for clusterMeshProfile APIs. * Make clusterMeshProfile status optional, since on create it will be nil. * Add missing "state" field to Member meshProperties example. * Improve doc comments and allow memberLabelSelector to be nil. * Run prettier to remove blank line. --------- Co-authored-by: zuhair <48816804+zuhairm2001@users.noreply.github.com> * Extract label selector out to its own model. (#40665) * Extract label selector out to its own model. * No restrictions in the generic selector. * Update examples to match tsp changes. * fix: update type of lastAppliedMemberSelector on ClusterMeshProfileStatus (#41124) * fix: update last applied member label selector to member selector in cluster mesh profile * tidy + example fix * fix incorrect name --------- Co-authored-by: Sean Hobbs <sehobbs@microsoft.com> * Updating Mesh Member and ClusterMesh Profile State Enums (#42446) * init * tsp compile + fix enum name --------- Co-authored-by: zuhair <48816804+zuhairm2001@users.noreply.github.com> Co-authored-by: Sean Hobbs <ealianis@outlook.com> Co-authored-by: Sean Hobbs <sehobbs@microsoft.com>

* Add 2026-06-01-preview tag * add preview suffix * typo * Add client-side EC reference to VoiceLive 2026-06-01-preview (#43328) * Add Hosted agent invocations events (#43329) Co-authored-by: Jian Miao <jianm@microsoft.com> * API view * Reference 2026-06-01-preview VoiceLive.json in readme * Voice Live WebRTC Feature Events - 2026-06-01-preview (#43406) * WebRTC Core Events * sdp.create * update wbrtc api view * format fix * VoiceLive: add azure-realtime-native voice type (2026-06-01-preview) (#43370) * VoiceLive: add azure-realtime-native voice type (2026-06-01-preview) * Regenerate 2026-06-01-preview swagger for azure-realtime-native voice * Add azure-realtime-native voice names to cspell dictionary * Address Copilot review: clarify extensible enum doc, remove unneeded suppress --------- Co-authored-by: Yulin Li <yulili@microsoft.com> * Add JS client name overrides for transcription fields and Response; Python avatar_type --------- Co-authored-by: Xiting Zhang <xitzhang@microsoft.com> Co-authored-by: Khushmeet Chandi <khushmeetchandi@gmail.com> Co-authored-by: Jian Miao <eric.mjian@gmail.com> Co-authored-by: Jian Miao <jianm@microsoft.com> Co-authored-by: Yulin Li <liyulin@pku.edu.cn> Co-authored-by: Manthan Thakker <manthanthakker40@gmail.com> Co-authored-by: Yulin Li <yulili@microsoft.com>

@doc

* Add CognitiveServices 2026-03-15-preview TypeSpec source and examples Adds the 2026-03-15-preview API version for CognitiveServices Management plane: - Version enum member in main.tsp - Updated models.tsp with new preview features (evaluateDeploymentPolicies, ManagedNetwork V2, AccountConnections, ProjectConnections, CapabilityHosts, AgentApplications, AgentDeployments, and supporting models) - Updated Account.tsp, ManagedNetworkSettingsPropertiesBasicResource.tsp - readme.md AutoRest tag configuration - cspell dictionary additions - 160 example files for all resource operations Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add ManagedComputeDeployment resource for 2026-03-15-preview Adds managed compute deployment CRUD operations with long-running create/update/delete, compute operation status tracking, and ARM-compliant suppression justifications. Co-authored-by: ChunyuMSFT <79233053+ChunyuMSFT@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add ManagedComputeUsages API for 2026-03-15-preview Adds managed compute usage listing endpoint for tracking compute resource utilization. Co-authored-by: abpatel <abpatel@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add AcceleratorCapacity resource for 2026-03-15-preview Adds subscription-level AcceleratorCapacity read-only resource for querying available accelerator capacity per type and region, including deployment size information. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add polymorphic Compute resource with ContainerInstance type Adds Compute resource with polymorphic type support (ContainerInstance), including CRUD operations, power management (start/stop/restart), and provisioning state tracking. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add compiled RM output for 2026-03-15-preview Generated swagger (cognitiveservices.json) and 178 example files compiled from TypeSpec source via `npx tsp compile .`. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add 200 response to DeleteProject.json for 2026-03-15-preview The Project.tsp delete operation includes ArmDeletedResponse (200) but the 2026-03-15-preview example was missing it, causing ModelValidation CI failure. Other versions were fixed in PR #42414 but this version's example didn't exist on main at that time. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Rename acceleratorCapacities to managedComputeCapacities (#42794) Rename resource type from acceleratorCapacities to managedComputeCapacities to match RP PR Azure/Platform-ResourceProvider#15582507 (Qianqian's rename). Changes: - AcceleratorCapacity.tsp → ManagedComputeCapacity.tsp (file + content) - models.tsp: AcceleratorCapacityProperties → ManagedComputeCapacityProperties, AcceleratorCapacityListResult → ManagedComputeCapacityListResult - Example: ListAcceleratorCapacities.json → ListManagedComputeCapacities.json - main.tsp import updated - Recompiled RM output Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * change the id and name of sku in .json example file (#43118) * change the id and name of sku in .json example file * change location * Add Workbench resource under Project (#42801) * Add Workbench resource * fix: update suppress justifications for new Workbench resource * fix: address PR review — add PatchModel, update suppress text, fix response codes * fix: regenerate swagger and remove 204 from examples * fix: revert to ArmResourceActionAsync and add 204 * fix: correct JSON nesting in workbench example files The "204": {} response was incorrectly nested inside the "202" response object instead of being a sibling response entry. This caused: - ModelValidation failure (204 not found at response level) - PrettierCheck failure (structural formatting mismatch) - TypeSpec Validation failure (examples out of sync) Also regenerated swagger via tsp compile to sync RM output examples. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: revert PATCH to use full Workbench class * fix: add suppress for PATCH using full Workbench class * fix: add missing UpdateWorkbench example and regenerate swagger Add UpdateWorkbench.json example for the Workbenches_Update (PATCH) operation, which was missing and causing ModelValidation CI failure (XMS_EXAMPLE_NOTFOUND_ERROR). Regenerate swagger to pick up the x-ms-examples reference. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: format Workbench.tsp to pass TypeSpec Validation format rule Run 'tsp format' on Workbench.tsp to fix TypeSpec Validation CI failure (Rule Format failed). Pure formatting change — no behavioral impact. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: suppress PatchBodyParametersSchema for Workbench PATCH operation Workbench uses the same PatchModel = Resource pattern as Compute, where the full resource is the PATCH body with required properties nested inside the optional properties bag. Add targeted suppression paths for: - parameters[6].schema (top-level 'properties' field required) - parameters[6].schema.properties.properties (targetClusterId, imageLink required) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Jyosthna Sri Sai Manne <jmanne@microsoft.com> Co-authored-by: Fareed Mabrouk <fmabrouk@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Apply tsp format for TypeSpec 1.12.0 compatibility Reformat @@doc() calls in 4 CogSvc .tsp files to match the new line-breaking rules introduced by TypeSpec compiler 1.12.0 on main. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add VmManagedCompute managed compute deployment shape (#43238) * Add VmManagedCompute managed compute deployment shape Update Cognitive Services managedComputeDeployments TypeSpec and generated swagger for the VmManagedCompute SKU shape from PRP. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Keep GlobalManagedCompute examples and add VM examples Preserve existing managed compute deployment examples and add separate VmManagedCompute examples for the new SKU shape. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Drop instanceType from ManagedComputeDeploymentProperties Per review feedback, instanceType and computeId would be mutually exclusive selectors for VM-backed managed compute deployments. Since this preview only supports the BYOC path (computeId pointing to a Foundry compute resource), instanceType is redundant: the VM SKU is already determined by the referenced compute resource. Removing it now to keep the API surface minimal; can be reintroduced in a future preview if a self-managed-compute path is added, at which point proper mutual-exclusion validation can be expressed. Pool.instanceType (cluster/node-pool model) is intentionally unaffected. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add managed compute deployment to 2026-01-15-preview Mirror managed compute deployment versioning and generated 2026-01-15-preview Swagger/examples while preserving 2026-03-15-preview output. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert 2026-01-15-preview managed compute deployment This reverts commit 8b3f40a. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update managed compute deployment examples Align managed compute deployment samples with the BYOC source specs, including VM computeId/project template examples, mixed list output, and documented delete LRO responses. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Move managed compute priority into properties Add priority as a string field on managed compute deployment properties and update VM managed compute examples. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove managed compute backend projection The referenced BYOC managed compute docs do not define a backend response field; keep the response shape aligned to documented properties.computeId instead. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Align managed compute deployment schema Add Updating provisioning state for the 2026-03-15-preview contract, model deployment routes as dynamic string maps, and make managed compute deployment SKU fields required with capacity validation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert "Align managed compute deployment schema" This reverts commit c934cb0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Ling Yan <neilyan@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix .NET SDK duplicate-client-name error for UserAssignedIdentity Add @@clientName decorator to disambiguate CogSvc custom UserAssignedIdentity from ARM common-type UserAssignedIdentity in the C# SDK namespace. The emitter regression (20260514.4 → 20260518.7) now surfaces this latent name collision as an error. This follows the same pattern used for 14 other CogSvc types (AssignedIdentity, IdentityKind, Sku variants, etc.). No impact on swagger output, wire format, or other SDK languages. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: ChunyuMSFT <79233053+ChunyuMSFT@users.noreply.github.com> Co-authored-by: abpatel <abpatel@microsoft.com> Co-authored-by: QianqianNie <44004519+QianqianNie@users.noreply.github.com> Co-authored-by: Breado <52954733+Clara-breado@users.noreply.github.com> Co-authored-by: jyo219 <jyosthna.jfc003@gmail.com> Co-authored-by: Jyosthna Sri Sai Manne <jmanne@microsoft.com> Co-authored-by: yan0lovesha <neil.yan@outlook.com> Co-authored-by: Ling Yan <neilyan@microsoft.com>

* Add 2026-05-01-preview API version (copy from 2025-08-18-preview) * Added new RT changes * updated readme * Updated tsconfig to fix lintdiff error * Remove 'provisioningState' and 'status' fields from organization examples for clarity * Confluent: adopt LiftrBase VnetInjectionDetails for AccessPointProperties * Update egressRoutes to use array format in AccessPoint resource examples and models * Swagger PrettierCheck fix * Fix prettier formatting in AccessPointResources example files --------- Co-authored-by: Raja Singhal <rajasinghal@microsoft.com> Co-authored-by: Nikhil Gupta <52026487+nikhgup@users.noreply.github.com>

* Onboard Microsoft.AzureResilienceManagement (RPaaS, preview) to public First-time onboarding of the Microsoft.AzureResilienceManagement resource provider to the public azure-rest-api-specs repo. RP is RPaaS-managed (openapi-subtype: rpaas) and currently in private preview. Includes three preview API versions: - 2025-02-01-preview - 2026-03-01-preview - 2026-04-01-preview (default) Spec content matches azure-rest-api-specs-pr origin/RPSaaSMaster at 2e6674f3ba66cf08a684416719a7af54111f0bac. TypeSpec compiles cleanly with the public repo toolchain; no emitter drift. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix CI: v2 folder structure, LRO POST responses, skipToken suppression, multi-version default tag - Move TypeSpec project to v2 layout: resource-manager/Microsoft.AzureResilienceManagement/AzureResilienceManagement/ (5-segment path required by tsv FolderStructure rule) - Update tspconfig.yaml to v2 pattern (emitter-output-dir: {project-root}, drop azure-resource-provider-folder) - Update readme.md input-file paths to be relative to the moved readme - Fix LRO POST operations (addOrUpdateResources, refreshReadinessState, resyncReadinessCheck) to return 202+204+default by switching from ArmResourceActionNoResponseContentAsync to ArmResourceActionAsync<R, Req, ArmNoContentResponse, ...> (Spectral PostResponseCodes); suppress conflicting TSP ARM library rule arm-post-operation-response-codes inline - Add targeted XMSSecretInResponse suppression for ServiceGroupTenantParameters.skipToken (the standard OData paging continuation token, not a secret) - Add multi-version default tag package-preview-2026-04 (combines 2026-04 + 2026-03) to satisfy Avocado MISSING_APIS_IN_DEFAULT_TAG (2026-04 dropped some operations that exist in 2026-03) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix CI: tsp format, YAML quoting in skipToken suppression, revert to single-version default tag with Avocado suppression - tsp format moved #suppress directives above @decorators (drill.tsp) - Remove embedded single quotes from skipToken reason text (was causing YAML parsing error in LintDiff readme.md parser at line 19:27) - Revert default tag to package-2026-04-01-preview (single version); multi-version tag triggered MULTIPLE_API_VERSION in Avocado - Add Avocado MISSING_APIS_IN_DEFAULT_TAG suppression in suppressions.yaml documenting the intentional API removal in 2026-04-01-preview - Update suppressions.yaml path to the new v2 location Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix LintDiff: add arm-types-dir for v2 layout; fix Avocado suppression format - Add arm-types-dir: {project-root}/../../../../common-types/resource-management to tspconfig.yaml. The emitter default (../../common-types) only works for v1 layout; in v2 the project lives 4 levels deeper, breaking external schema from emitted swagger to common-types/resource-management. LintDiff was failing with 'Error reading file common-types/resource-management/v6/types.json' due to wrong relative path. - Recompile produced correct 6-up paths in all three preview swaggers (verified locally) - Correct Avocado suppression format in suppressions.yaml: tool 'Swagger Avocado' (not 'Avocado'), use 'path:' targeting the swagger file (not readme.md), drop the unsupported 'rules:' field. Mirrors the pattern used by alertsmanagement and cost-management. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix ModelValidation: add 204 response entry to LRO POST examples The drill LRO POST operations (AddOrUpdateResources, RefreshReadinessState, ResyncReadinessCheck) emit 202+204+default per ARM LRO guidelines, but the example files only documented the 202 response. Adding 204 entries so oav-runner ModelValidation passes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix TypeSpec Validation: add 204 to source example files Previous commit edited only the emitted swagger example files, but the TypeSpec project keeps source examples at examples/<version>/ which the emitter copies to preview/<version>/examples/ during compile. The post-compile diff check in tsv then complained that the working tree differed from the (regenerated) emit. Fix by also adding 204 entries to the source example files so tsp compile is idempotent. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Change UsagePlans PATCH from sync to async (ArmTagsPatchAsync) enableAsyncOperation=true on RT registration wraps all operations as async, causing swagger validation failure for sync PATCH (200 response rejected because RPaaS returns 202). Change: ArmTagsPatchSync -> ArmTagsPatchAsync in usagePlan.tsp. Run tsp compile to regenerate openapi.json and examples. Source examples for 2026-03-01-preview and 2026-04-01-preview updated with 202 response. Mirrors private-repo PR #28559 / commit 656b0cac9c8. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Add CSharp client-name customizations for the blob service static website model and enabled property. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix for Go breaking changes * fotmat --------- Co-authored-by: tadelesh <chenjieshi@microsoft.com>

Preserve pre-migration Swagger enum names via @@clientName overrides. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

@secret

…peSpec stable/2024-04-24) (#43164) Security fix: Added @secret + @visibility(Lifecycle.Read) to EnvironmentInfo.ingestionKey in models.tsp. This adds format:password, readOnly:true, x-ms-secret:true to the generated swagger, preventing ingestion keys from being exposed in GET/LIST responses. Removed ingestionKey from MaximumSet example response bodies (readOnly fields should not appear in responses). VMExtensionPayload.ingestionKey intentionally left unchanged (write-only input field). References: - ICM #31000000574418 - ADO #37399766 Co-authored-by: aluvalar <aluvalar@DESKTOP-ECHQUT4> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Nikhil Gupta <52026487+nikhgup@users.noreply.github.com>

* Mitigate Python SDK breaking changes for azure-mgmt-consumption * Update back-compatible.tsp * Update tspconfig.yaml * Update tspconfig.yaml --------- Co-authored-by: kazrael2119 <98569699+kazrael2119@users.noreply.github.com>

* update config * update * update

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Customize Storage policy names for C# singleton detection * update * bump api version to main * format * add suppression * format * update usage * update * update * fix issues * fix issues

* Microsoft.Devices DeviceProvisioningServices 2026-03-01-preview * Updated LRO Header * Fixed Merge Issue * Fixed Merge Issue * LRO Changes * Fixed Comments

* Update tspconfig.yaml * Update tspconfig.yaml

@SharedRoute

…erviceTreeId in Enable feature (#43317) * Add API version 2026-06-01 for Microsoft.ComputeLimit with optional serviceTreeId on enable action - Add FeatureEnableRequest model with optional serviceTreeId (uuid) to enable operation - Version enable operation using @sharedRoute/@removed/@added/@renamedFrom pattern - Add ArmCombinedLroHeaders (Azure-AsyncOperation + Location + Retry-After) to all async actions - Add example files and generated swagger for 2026-06-01 * Add suppress directive for operationId in enableV2 method * Update compute limit feature API for version 2026-06-01: suppress operationId warning, adjust tag, and modify request body requirement * Update FeatureEnableRequest model to change serviceTreeId type from uuid to string * Update FeatureEnableRequest model and API definitions for 2026-06-01: add request body schema and adjust versioning to address comments 1. You should not use openapi extension anymore. 2. The renaming will cause SDK breaking changes. * Remove Azure-AsyncOperation header from ComputeLimit API responses. * Refactor ComputeLimit API for 2026-06-01: update FeatureEnableRequest model, introduce enableV2 action, and replace deprecated examples * Add optional serviceTreeId to enable action in API version 2026-06-01 - Add FeatureEnableRequest model with optional serviceTreeId property - Use @renamedFrom/@SharedRoute pattern to version the enable operation without changing operationId (Features_Enable) across versions - Add v2026_06_01 to Versions enum and update readme.md default tag - Add FeatureEnableRequest csharp clientName in client.tsp * Remove Features_EnableV2 example JSON file for API version 2026-06-01 * Refactor client and back-compat TSP files for improved readability

@added

…icrosoft.ComputeBulkActions (#43268) * Add LaunchBulkInstancesOperation resource * Fix CI: format + suppressions for LintDiff/BreakingChange/TypeSpec Validation * Refactor: move VM attribute types to reusable vmAttributes.tsp * Fix readme.md YAML: escape colon in ParameterNotUsingCommonTypes suppression reason * Move LaunchBulkInstancesOperation to new 2026-06-06-preview api-version * Rename interface BulkActions -> LaunchBulkInstancesOperation; rename example files; prettier-format * Fix nested resource URL: use bare LaunchBulkInstancesOperationEnvelope for @listsResource; use LaunchBulkInstancesOperationId for child path * Address review findings #1, #5, #6, #7: orphan example cleanup, version-scoped suppressions, internally consistent VMAttributes example * Add createdTime to LaunchBulkInstancesOperationProperties (read-only) to match Kronox DTO * Address ARM API review feedback on PR #43268 Consolidates the LaunchBulkInstancesOperation surface into the existing 2026-04-06-preview API version (no separate 2026-06-06-preview) and applies the blocking review findings from the ARM API reviewer agent. Findings addressed: - EX-RESOURCE-ID: set id/name/type to the canonical Microsoft.Compute/locations/launchBulkInstancesOperations envelope across all LaunchBulkInstancesOperation_* example response bodies. - EX-LRO-HEADERS: rename location header to PascalCase Location, replace contoso.com placeholders with realistic management.azure.com polling URLs. - RPC-Async-V1-11: emit both Location and Azure-AsyncOperation headers on Cancel and Delete 202 responses by setting LroHeaders = ArmCombinedLroHeaders & RetryAfterHeader in TSP. - Section 10A (Suppression Scoping): add a where: JSONPath array to the ParameterNotUsingCommonTypes suppression so it covers both the new launchBulkInstancesOperations paths and the existing virtualMachinesBulk* paths after the location parameter rename. - EX-DESCRIPTIVE-VALUES (ListVirtualMachines): fix the example so the operation name parameter no longer duplicates the subscriptionId, and use realistic VM name/type/filter/nextLink values. - Section 1.6 (Resource Type Naming): rename the routes.tsp alias key locationparameter -> location so all bulk-action POST paths use the same parameter name; update example payloads accordingly. - EX-TITLE: drop the duplicate "- generated by [MaximumSet] rule" suffix from BulkCreate_MinimumSet_Gen.json and BulkVdiFlexCreate_MinimumSet_Gen.json titles. - SEC-SECRET-DETECT: replace the customData base64 string that decoded to "export SENSITIVE=1" in BulkReimage_MaximumSet_Gen.json with a clearly-fake placeholder. Cleanup: - Drop the redundant @added(Microsoft.Compute.Versions.\2026-04-06-preview\) decorators across vmAttributes.tsp, launchBulkInstancesOperation.tsp, and models.tsp now that 2026-04-06-preview is the only version (decorators are no-ops on a single-version service and the generated swagger is byte-identical without them). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Match source RP: drop Azure-AsyncOperation header from Cancel/Delete 202 Reverts the prior LroHeaders = ArmCombinedLroHeaders override on the LaunchBulkInstancesOperation Cancel (POST) and Delete (DELETE) operations so the emitted 202 headers exactly match the source Microsoft.ComputeBulkActions/2026-02-01-preview RP: Location + Retry-After only. CreateOrUpdate PUT continues to emit Azure-AsyncOperation + Retry-After on 201 via the default azure-async-operation final-state-via mode, which also matches the source RP. This re-introduces the RPC-Async-V1-11 lint observation on Cancel/Delete async POST/DELETE, which is acceptable because the same pattern is already in production under Microsoft.ComputeBulkActions/2026-02-01-preview with the corresponding PostResponseCodes suppression. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix Operations_List example: replace data-action/internal payload Replaces the Operations_List_MaximumSet_Gen.json example payload, which had isDataAction: true, actionType: "Internal", and a placeholder nextLink, with a representative control-plane operation: - name: Microsoft.Compute/locations/launchBulkInstancesOperations/read - isDataAction: false - display provider/resource/operation/description matching the real read op - origin: "user,system" - realistic nextLink URL with api-version and an opaque page token Addresses ARM reviewer feedback (EX-PAYLOAD / RPC-Operations-V1): the operations listing endpoint is itself a control-plane read, so its sample payload should describe a control-plane operation rather than a hidden data-action operation. Applied to both the canonical preview/2026-04-06-preview/examples/ folder and the mirrored examples/2026-04-06-preview/ folder. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Restore @added decorators in models.tsp Restores the 9 \@added(Microsoft.Compute.Versions.\2026-04-06-preview\)\ decorators on the ExecuteCreateFlex unions/models in models.tsp that existed on origin/main and were inadvertently removed during the "drop redundant @added decorators" cleanup in the consolidation commit. These decorators are no-ops for a single-version service today, but they are present on origin/main and removing them produced unnecessary churn in the PR diff. Keeping them aligned with origin/main minimizes the diff and preserves the existing version-gating pattern for when a second API version is introduced later. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Annotate BulkactionVMExtension protected settings as secrets Add @secret decorator to BulkactionVMExtensionProperties.protectedSettings and .protectedSettingsFromKeyVault. The autorest emitter now produces x-ms-secret: true and format: password on both properties in the generated swagger, satisfying ARM Section 7.2 / SEC-SECRET-DETECT. Addresses reviewer finding #20 (EXISTING). The same omission exists in the source Microsoft.ComputeBulkActions RP and will be fixed there in a coordinated follow-up. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix ModelValidation: remove protectedSettings from example responses Removed protectedSettings and protectedSettingsFromKeyVault from response payloads in 4 LaunchBulkInstancesOperation example files (canon + mirror). These autogenerated keys triggered SECRET_PROPERTY errors after the @secret annotation was added in f3a470d. Request bodies still carry them; only responses were corrected, since a service must never return secrets. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Change GetOperationStatus URL to launchBulkInstancesOperations/asyncOperations/{asyncOperationId} Replaces the previous .../locations/{location}/operations/{id} path with .../locations/{location}/launchBulkInstancesOperations/asyncOperations/{asyncOperationId} to match the service contract. The TSP operation now uses an explicit @route since the literal launchBulkInstancesOperations collection segment cannot be injected via ArmResourceRead. Updated path parameter from id to asyncOperationId. Also updated Azure-AsyncOperation and Location header URLs in the CreateOrUpdate, Cancel, and Delete examples. Validated locally with tsp compile --warn-as-error, azsdk run_typespec_validation (Succeeded), and oav validate-example. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add PathForNestedResource suppression for GetOperationStatus path The new GetOperationStatus path .../locations/{location}/launchBulkInstancesOperations/asyncOperations/{asyncOperationId} intentionally uses a fixed launchBulkInstancesOperations collection segment followed by asyncOperations/{id} to match the service-side routing contract. This is the documented exception case for the PathForNestedResource rule. Also updates the existing ParameterNotUsingCommonTypes suppression entry to point at the new path since the previous /operations/{id} path no longer exists. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <copilot@microsoft.com> Co-authored-by: Yash Khandelwal (from Dev Box) <yakhande@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

@key

….) in TypeSpec (#43273) Document and evaluate the correct way to declare array-item identifiers in ARM TypeSpec specs (@key / @Identifiers), and forbid @extension(...) in TypeSpec source.

@in

The RP at EngSys-SLISLO-ControlPlane uses Newtonsoft StringEnumConverter with no [EnumMember] aliases, so the wire values must be the literal C# enum identifiers. The TypeSpec previously used mathematical/symbolic wire values that the RP rejected with MalformedStructureError. Verified live against the RP runtime; this is what 5/5 SDKs need to emit to successfully POST/PUT/GET an SLI resource. Changes (sliProperties.tsp): - ConditionOperator: ==, !=, <, <=, >, >=, @in, !in, !startswith, !contains, startswith, contains -> eq, ne, lt, lte, gt, gte, in, notin, notstartswith, notcontains, startswith, contains (per DimensionOperator + ScalarComparatorEnum in the RP) - WindowUptimeCriteriaComparator: <, >, <=, >= -> lt, gt, lte, gte (per ComparatorEnum in the RP) - SamplingType: lowercase max/min/avg/sum -> PascalCase Average/Sum/Count/Min/Max (per SpatialAggregationTypeEnum which the RP reuses for both spatial aggregation and sampling type) Friendly enum names (Equal, GreaterThanOrEqual, ...) are unchanged, so generated SDK consumers see no source-level breaking change - only the bytes on the wire change. 6 example JSON files updated to use new wire values. openapi.json regenerated via tsp compile. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Bring preview-only features back * Add maxOutputDocuments x2; failOnError; KB/KS count; new gpt models * Add CMK features: federatedIdentityClientId, isServiceLevelKey * [WIP] PurviewSensitivityLabelInfo * Fix searchSensitivityLabelInfo model * Add WorkIQ KS; Add searchSensitivityLabelInfo for several KS Reference * Add McpServer KS * Update ContentUnderstandingSkillChunkingProperties * Update WebKnowledgeSourceParameters, SearchIndexKnowledgeSourceParameters * Add SharePoint and Purview features * Add modelName; KnowledgeBaseModelWebSummarizationActivityRecord * Add ImageServing, AssetStore, FreshnessPolicy, SensitivityLabels * Add IndexedSql KS * Add routes and models for new File KS; Fix client.tsp * Add FabricDataAgent KS * Add FabricOntology KS * Enable pagination for ListIndex and IndexStatsSummary APIs * Consolidate deprecated ChatCompletionSkill properties since GA * Copy examples from ADO except for FabricOntology; Fix part of oav validate-example errors; TODO: Fix rest validate-exmaple errors * Fix examples for validate errors and prettier check * Update KnowledgeBaseWorkIQReference * Add FabricOntology examples * Remove KS Create and CreateOrUpdate examples for the known issue from searchIndexParameters.searchFields.name as * * Fix client.tsp * Fix format * Draft change log * Fix FabricOntology KS examples * Fix readme.md * Update changelog * Remove outdated example files * Fix response schema in SearchIndexAutocompleteDocumentsGet.json cross versions * Fix response schema in SearchIndexAutocompleteDocumentsGet.json cross versions (compiled assets) * Bug Fix: Add responseSensitivityLabelInfo to KnowledgeBaseRetrievalResponse * Add warning property to KnowledgeBaseActivityRecord (#42580) * Add warning property to KnowledgeBaseActivityRecord * Fix examples * Adopt 2026-04-01 GA fix (#42653) * Fix nit: remove duplicate from merge main * Remove duplicates in client.tsp * Update descriptions of McpServerToolInclusionMode * Fix a nit * Revert "Update descriptions of McpServerToolInclusionMode" This reverts commit abc536e. * Fix tsp format * Fix tsp format with tsp compiler 1.12.0 * Map two Search preview models to indexes client namespace Add client namespace mappings for Search.SharePointConnectorAppRegistration and Search.ContentUnderstandingSkillChunkingMethod to Azure.Search.Documents.Indexes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix missing models of MCP Server KS (#43318) * Fix missing models of MCP Server KS * update changelog * Fix client.tsp * Expose KS File ops in SDK * Expose KS File ops in SDK * Expose KS File ops in SDK * Fix missing models of File KS and IndexedSql KS (#43321) * Draft fix for missing models of File KS and IndexedSql KS * update models per feature owner's confirmation * Fix nits: add two missing doc comments * fix package paths for java models * Add Content-Disposition header to uploadFile operation of File KS (#43433) * Adjust Python Search preview type visibility Expose HybridCountAndFacetMode, HybridSearch, QueryLanguage, and QuerySpellerType for Python, and keep DebugInfo available for generated Python preview APIs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Refactor: replace KnowledgeBaseRetrievalActivityRecord inheritance with spread pattern (wire-level unchanged) (#43463) * Refactor: replace KnowledgeBaseRetrievalActivityRecord inheritance with spread pattern (workaround for a known SDK emitter issue; wire-level unchanged) * tsp formatted --------- Co-authored-by: Zixin Yao <ziyao@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: efrainretana <efrainretana@microsoft.com> Co-authored-by: Isaiah Dickerson <idickerson@microsoft.com>

* type spec * swagger * fix open api * Fix * fix typespec validation * missed a few --------- Co-authored-by: Celina Zhao <zhaocelina@microsoft.com>

jeremyfrosti requested review from a team, MaryGao, benbp, live1206, maririos, mikeharder, praveenkuttappan, pshao25, raych1, solankisamir and weshaggard as code owners March 5, 2026 19:09

github-actions Bot added resource-manager RPaaS SuppressionReviewRequired TypeSpec Authored with TypeSpec labels Mar 16, 2026

william051200 and others added 14 commits May 6, 2026 06:53

Add Azure Linux 4.0 image aliases (#42695)

345bc8e

* Add Azure Linux 4.0 Image aliases * Add cspell.yaml for spell check handling

Sync eng/common directory with azure-sdk-tools for PR 15475 (#42870)

f6c1438

* fix purge date bug * added else --------- Co-authored-by: Marcos Salamanca <masalama@microsoft.com>

Pass Npm Config to CSpell (#42910)

f127e37

Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

Preserve PostgreSQL private endpoint connection state name (#42791)

f2c2f8a

Add C# clientName decorators for remaining naming fixes (ProtectionLe…

ca1b73e

…vel, SourceSideScanStatus, SourceSideScanSummary, VMWorkloadPolicyType) (#42918)

Remove .github/skills/evals/azure-typespec-author folder (#42913)

4ecac5b

This skill and its eval cases have been moved to the azure-sdk-tools repo.

Add Python client name for FileSharesManagementClient (#42923)

61f4dfa

update python client name and here is namespace review result Azure/azure-sdk#9492

Change service name to 'FileShares' in tspconfig.yaml (#42925)

75ca22c

[JS] visibility workaround for monitor accounts (#42784)

b21d8a7

* visibility workaround for monitor accounts * Update client.tsp

added dotnet specific ovverides for EKM clients (#42793)

0aea5f5

* added dotnet specific ovverides for EKM clients --------- Co-authored-by: Hari K <kha@microsoft.com> Co-authored-by: Mike Harder <mharder@microsoft.com>

audunn and others added 30 commits May 21, 2026 15:28

[NetApFiles] bump to 2026-03-01 (#42979)

232dfa7

* bump to 2026-03-01 * tsp * tsv compile again * BreakthroughMode fix mutablitity in preview

Move AIGrounding lease under service-level folder (#43402)

f246632

Co-authored-by: Vikeshi Tiwari <vikestiwari@microsoft.com> Co-authored-by: Tejaswi Salaigari <tsalaigari@microsoft.com>

Add service-level lease for Microsoft.AzureResilienceManagement/Azure…

92233e7

…ResilienceManagement (#43430) Co-authored-by: Vikeshi Tiwari <vikestiwari@microsoft.com>

Add ARM modeling lease for Microsoft.DeviceUpdate/DuDeviceRegistry (#…

29c599c

…43432) * Add ARM modeling lease for Microsoft.DeviceUpdate/DuDeviceRegistry * Add ARM modeling lease for Microsoft.Migrate/NetworkAssessments --------- Co-authored-by: Vikeshi Tiwari <vikestiwari@microsoft.com>

Add JS client name overrides for transcription fields and Response; P…

7d69cde

…ython avatar_type (#43437) Co-authored-by: Xiting Zhang <xitzhang@microsoft.com>

Add csharp customizations for ResourceGraph migration (#43066)

cd28334

mgmt, java, compute, tspconfig, advanced-versioning (#43408)

045bef3

Rename Storage static website CSharp API (#43449)

c847b84

Add CSharp client-name customizations for the blob service static website model and enabled property. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Fix Go breaking changes for resource graph (#43450)

06c196e

* Fix for Go breaking changes * fotmat --------- Co-authored-by: tadelesh <chenjieshi@microsoft.com>

Mitigate Python SDK breaking changes for azure-mgmt-cdn (#43455)

73b5a14

Preserve pre-migration Swagger enum names via @@clientName overrides. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

[JS] Resolve breaking change for RedisEnterprise (#43452)

52ed116

Remove C# access customizations from management specs (#43362)

dc596ed

[JS] Enable compatibility-lro for managementgroups (#43080)

aa9df24

* update config * update * update

Remove temporary CSharp API version pins (#43456)

fa7d6ab

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Customize Storage policy names for C# singleton detection (#43377)

7811c12

* Customize Storage policy names for C# singleton detection * update * bump api version to main * format * add suppression * format * update usage * update * update * fix issues * fix issues

Microsoft.Devices DeviceProvisioningServices 2026-03-01-preview (#40007)

182eacf

* Microsoft.Devices DeviceProvisioningServices 2026-03-01-preview * Updated LRO Header * Fixed Merge Issue * Fixed Merge Issue * LRO Changes * Fixed Comments

Fixes the gen folder for App Config Python (#43435)

8c26075

* Update tspconfig.yaml * Update tspconfig.yaml

Add TSP-ARRAY-IDENTIFIERS rule: ban @extension("x-ms-identifiers", ..…

8601a87

….) in TypeSpec (#43273) Document and evaluate the correct way to declare array-item identifiers in ARM TypeSpec specs (@key / @Identifiers), and forbid @extension(...) in TypeSpec source.

Update Typespec for Azure Policy to match with actual behavior (#43353)

55e7cec

* type spec * swagger * fix open api * Fix * fix typespec validation * missed a few --------- Co-authored-by: Celina Zhao <zhaocelina@microsoft.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Updating stable release branch#41047

Updating stable release branch#41047
jeremyfrosti wants to merge 2039 commits into
release-sql-Microsoft.Sql-2025-01-01from
main

jeremyfrosti commented Mar 5, 2026

Uh oh!

github-actions Bot commented Mar 5, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

Conversation

jeremyfrosti commented Mar 5, 2026

ARM (Control Plane) API Specification Update Pull Request

PR review workflow diagram

Purpose of this PR

Due diligence checklist

Additional information

Getting help

Uh oh!

github-actions Bot commented Mar 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Next Steps to Merge

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

github-actions Bot commented Mar 5, 2026 •

edited

Loading