Merge latest code, remove immutable backups, update examples for mvu pvc by nasc17 · Pull Request #1 · nehrao1/azure-rest-api-specs

nasc17 · 2026-05-19T20:38:37Z

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

* Add StandbyPool API version 2026-04-01 to service.tsp * Add Mix VM State support for StandbyPool 2026-04-01 * Add examples, swagger spec, and swagger examples for StandbyPool 2026-04-01 * Update readme.md with package-2026-04 tag * fix: surgical patch for service.tsp - add only 2026-04-01 version entry * fix: surgical patch for standbyVMPool.tsp - add Mix state and VMStateDistribution * fix: preserve LF line endings for service.tsp * fix: preserve LF line endings for standbyVMPool.tsp * fix: rename VMStateDistribution to VmStateDistribution (PascalCase casing rule) * fix: rename VMStateDistribution to VmStateDistribution in swagger * fix: align swagger with tsp compile output (remove extra required/identifiers, reorder VmStateDistribution) * fix: add trailing newline to service.tsp * fix: add trailing newline to standbyVMPool.tsp * fix: make VmStateDistribution properties optional for PATCH compatibility * fix: remove required from VmStateDistribution for PATCH compatibility * Update client.tsp * fix: surgical readme.md update - add package-2026-04 tag only * empty --------- Co-authored-by: kazrael2119 <98569699+kazrael2119@users.noreply.github.com> Co-authored-by: Kushagra Bhardwaj <kubhardwaj@microsoft.com> Co-authored-by: Mike Harder <mharder@microsoft.com>

… for review (Azure#42654) * Add TriggerSource parameter to mark SDK PRs as ready for review When spec-gen-sdk pipeline is triggered by the release-plan-app, create the SDK pull request in 'ready for review' state instead of draft. A new 'TriggerSource' parameter (default: 'unspecified') is added to differentiate callers. Related: Azure/azure-sdk-tools#15209 Related: Azure/azure-sdk-tools#15294 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Updated to check name suffix --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* JS and Python updates * python updates * go initial * go clients * more name fixes go * updateMessage VisibilityTimeoutParameter * Revert "updateMessage VisibilityTimeoutParameter" This reverts commit 3caed55. * metadataheaderparameters removed * python -> omitSlashfromEmptyUrl * xml.name additions * go xml fixes * remove duplicate go * enable csharp generation (Azure#41629) * go clientOption * go file prefix * go clientOption responseEnvelopeName * remove unnecessary Storage.Queues qualifiers from client.tsp There's already a `using Storage.Queues;` * python -> update tspconfig * set version python * ignore pkg files python * JS: not using clientNamespace * add suppressions * format * clean up * clean up --------- Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com.com> Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com> Co-authored-by: Libba Lawrence <llawrence@microsoft.com> Co-authored-by: gracewilcox <graceawilcox@gmail.com> Co-authored-by: Jorge Rangel <102122018+jorgerangel-msft@users.noreply.github.com> Co-authored-by: catalinaperalta <caperal@microsoft.com>

…wer instructions (Azure#42543) * Fix ARM API reviewer agent instructions: clarify async response codes, fix false positives, and improve formatting ## Problem The ARM API reviewer agent instructions in `armapi-review.instructions.md` and `openapi-review.instructions.md` have several issues that lead to incorrect review feedback: 1. **Async PATCH response codes**: The instructions state that async PATCH must return `202`, but don't clearly explain that `200` is **also** required in the swagger definition for SDK response type discovery. Reviewers may miss this or not understand why both are needed. 2. **Async DELETE false positives**: The instructions list sync and async DELETE response codes but don't explicitly warn against conflating them. The agent frequently flags async DELETE operations for missing `200`, which is only required for *synchronous* DELETE. Section 6.3 mentions `200` in the context of the polling URL's terminal response, further confusing the distinction. 3. **LRO cross-references**: The general LRO section in `openapi-review.instructions.md` doesn't point readers to the ARM-specific or data-plane-specific sections for precise per-verb response code requirements, leading to inconsistent review guidance. 4. **Markdown formatting issues**: Unescaped asterisks in `EX-*` headings/checklist items render incorrectly, inconsistent blank lines between sections, minor table alignment issues, and a stray trailing whitespace. ## Fix ### Substantive clarifications (armapi-review.instructions.md) - Added a callout in section 4.2 explaining why async PATCH uniquely requires **both** `202` and `200` in swagger (SDK deserialization) - Added a prominent false-positive warning in section 5.1: async DELETE requires `202` + `204` only — do **not** flag for missing `200` - Added a clarifying note in section 6.3 that `200`/`204` refers to the **polling URL's** terminal response, not the initial DELETE response codes ### Cross-references (openapi-review.instructions.md) - Added a note in the general LRO section directing reviewers to `armapi-review.instructions.md` sections 5–6 for ARM-specific response codes and section 21 for data-plane LRO patterns ### Formatting fixes (both files) - Escaped `*` in `EX-*` heading and checklist item to prevent unintended markdown italic rendering - Normalized blank lines between checklist section headers for consistent markdown rendering - Fixed table column alignment in section 19.3 - Fixed list indentation for the `TenantLevelAPIsNotAllowed` enforced-by note - Removed trailing whitespace and extra blank lines * Revert unnecessary change.

* Fix 404 URLs in api-version-evolution.md Update versioning documentation URLs to match the new site structure: - 01-preview-version -> 01-about-versioning/ - Remove /arm/ segment from preview-after-preview, stable-after-preview, preview-after-stable, and stable-after-stable URLs Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix prettier formatting for api-version-evolution.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…e#42797) * Added client customizations to adhere to .NET naming guidelines * Adding few more client customizations * Fixing typespec errors. * Update the client customizations to follow .NET guidelines. --------- Co-authored-by: Sumedh Sandeep Parvatikar <sparvatikar@microsoft.com>

…2736) Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.4 to 4.1.5. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.5/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.5 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 4.1.4 to 4.1.5. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.5/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.5 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…zure#42738) Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.4 to 4.1.5. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.5/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.5 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…2739) Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 4.1.4 to 4.1.5. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.5/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.5 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…re#42774) Bumps the typespec-client-generator-cli group with 1 update in the / directory: [@azure-tools/typespec-client-generator-cli](https://github.com/Azure/azure-sdk-tools). Updates `@azure-tools/typespec-client-generator-cli` from 0.32.1 to 0.33.0 - [Release notes](https://github.com/Azure/azure-sdk-tools/releases) - [Commits](https://github.com/Azure/azure-sdk-tools/commits) --- updated-dependencies: - dependency-name: "@azure-tools/typespec-client-generator-cli" dependency-version: 0.33.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: typespec-client-generator-cli ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

@mikeharder

* Pin actionlint docker image to sha256 digest Agent-Logs-Url: https://github.com/Azure/azure-rest-api-specs/sessions/de091f51-8df0-4e27-9560-c21d7edec6e3 Co-authored-by: mikeharder <9459391+mikeharder@users.noreply.github.com> * Apply suggestion from @mikeharder --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: mikeharder <9459391+mikeharder@users.noreply.github.com> Co-authored-by: Mike Harder <mharder@microsoft.com>

…ure#42775) Bumps the typespec group with 1 update in the / directory: [@azure-tools/typespec-client-generator-core](https://github.com/Azure/typespec-azure). Updates `@azure-tools/typespec-client-generator-core` from 0.67.3 to 0.67.4 - [Release notes](https://github.com/Azure/typespec-azure/releases) - [Commits](https://github.com/Azure/typespec-azure/compare/@azure-tools/typespec-client-generator-core@0.67.3...@azure-tools/typespec-client-generator-core@0.67.4) --- updated-dependencies: - dependency-name: "@azure-tools/typespec-client-generator-core" dependency-version: 0.67.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: typespec ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…2806) * Add @@clientName decorators for PipelineGroups C# SDK naming

* Add FileShares 2026-06-01 examples and stable Add generated examples for Microsoft.FileShares/fileShares for API version 2026-06-01, including FileShareSnapshot (create/update/get/list/delete), FileShares (create/update/get/delete/list/listByParent/listBySubscription), limits, provisioning recommendation, usage data, name availability checks, private endpoint/PrivateLink resources, and operations examples. Also add stable copies under the stable/2026-06-01 path and a new stable fileshares.json, and update fileshares.tsp to include the new API surface. These examples provide test/usage payloads and responses for the new API version. * Update readme.md * add encryption in transit to nfsprotocolproperties * add added marker * add compiled json * add identity * Revert "add identity" This reverts commit 5ece48a. * Add encryptionInTransitRequired to 2026-06-01 FileShares examples * add identity, generate examples, lint, run validation (cherry picked from commit 216610a) * fixes to generated examples (cherry picked from commit b9d5f21) * Add patch models and restrict mutability for FileShare Introduce FileSharePatchProperties and FileShareSnapshotPatchProperties (TypeSpec + JSON definitions) and switch FileShare/FileShareSnapshot update operations to use these patch models. Adjust x-ms-mutability for several FileShare properties (provisionedStorageGiB, provisionedIOPerSec, provisionedThroughputMiBPerSec, nfsProtocolProperties, publicAccessProperties, publicNetworkAccess) and snapshot metadata to be update-only. Add suppress annotations for new patch models and update tspconfig.yaml to set azure-resource-provider-folder. Changes applied across preview and stable specs. * Revert "FileShares 2026-06-01 Identity" * fix initiatorId to Create + Read; add visibility to metadata * attempt 'post-generation patching' fix * Revert "attempt 'post-generation patching' fix" This reverts commit 9c8a487. * regenerated examples * tsp format * revert changes to examples; ONLY include initiatorId updates * remove new PrivateEndpointConnection and PrivateLinkResource files * add back PEC/PLR tests that were inadvertently removed --------- Co-authored-by: Stephanie Fong <stefong@microsoft.com> Co-authored-by: James Lindamood <jlindamood@microsoft.com> Co-authored-by: James Lindamood <jameslindamood@gmail.com>

* Define contract for Batch RuleSet feature * Update allow pattern for the rule name field * Remove redundant imports * Making the request body optional with handcraft typespec op * Updating default value for batchMode to null It will be treated as false * Versioning LRO for RuleSet Create/Update * Remove conditional readonly attribute name, rename it to ruleName * Setting batchMode as immutable * Retrigger validation pipeline * Fix format issue in readme.md file * add 2025-09-preview examples to 2025-12-01 * Merge 2025-09-01-preview back * Fallback old version of RuleSets_Create example * Address validation error * Address PR validation error * Seems like the version is mixing up with preview version in the typespec entity, try to address it * Fix preview version decorator * Rename ruleName to name for BatchRule, and remove deploymentStatus and provisioningState attributes. * Commit openapi.json * Do not use readonly property name, create a ruleName field * Correct the way we version the preview version * Fix the missing example issue from the pipeline * Commit all undetected change from preview version * Rename name the existing operation rather than create a new one for batch process * Fix LintDiff issue with ProvisioningStateMustBeReadOnly * Fix ProvisioningState reaonly issue * Make PUT request body not optional So it will be compliance with the ARM spec that requires the body. * Follow the advice from reviewer, to keep the request body optional. * Marking batchMode immutable * Marking ruleName and batchMode immutable * Supress warnings/errors from previous version * Improve suppress logic * Replace @OpenAPI.extension with @Identifiers decorator for BatchRuleProperties * Fix createV1 name --------- Co-authored-by: Deven Chen <devenchen@microsoft.com> Co-authored-by: Tianren Shen <tianrenshen@microsoft.com> Co-authored-by: Tianren Shen <1279011+Tianrens@users.noreply.github.com>

) * this is backwards compatible. new callers can explicitly add login-to-github and pass the authtoken parameter * Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * update to add fallback to login. will need to approve serviceConnection for the new builds, but other than that, no impact --------- Co-authored-by: Scott Beddall <scbedd@microsoft.com> Co-authored-by: Scott Beddall <45376673+scbedd@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…ude python (Azure#42857) BlobStorage and QueueStorage AccessPolicy.start/expiry are encoded as rfc3339-fixed-width (sub-second precision). Python's emitter loses precision when these are kept as utcDateTime, just as JavaScript does. Widen the existing 'javascript' alternateType scope to 'javascript, python' so the Python SDK receives them as strings, matching the treatment already used in FileStorage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

) * fix create-pull-request for source/target token utilization --------- Co-authored-by: Scott Beddall <scbedd@microsoft.com>

Co-authored-by: catalinaperalta <caperal@microsoft.com>

…zure#41670) * Adding API version 2026-04-01 for GA * fixing CI checks * nit: format * Changes suggested by copilot * Adding description for trigger and notification apis * Updated validationStatus in all examples * removing "unit: null" from examples related to server metrics * updated examples for pass fail criteria * updated list examples for mismatched parameters * removing null values for nextLink * nit: example update * Updated generated examples for specs * description for recurrence status * nit: improving operation id for list operations * fixing examples

* Add blockchain to latest profile * Add additional types * Update readme and copy files * Update tspconfig to emit only 2026-02-01-preview * Do not emit openapi3 * Update files * Update readmes * Update settings * Remove unneeded files * Fix version * Fix readme * Update files * Update files and remove unused version references * Update files * Copy files * Add suppressions yaml * Typespec cleanups and fixes * Formatting * Fix optionality of task status * Fix another optionality bug * Feedback and updates to conversation API * Remove 2025 reference * Update docs and small adjustments * Remove linked data assets API * Update suppressions.yaml * Update suppressions to use paths * Fix yaml formatting * Update description * Fix conversation naming * Fix task name validations * Fix inconsistencies * Fixes due to service discrepancies * Formatting fix * Fix service incompatibilities * Reintroduce :start and :stop discovery engine * Remove api-key * Fix optionality for investigation properties --------- Co-authored-by: Mark Cowlishaw <markcowl@microsoft.com>

…ually create the pullrequest with maintainer_can_modify unless the token has at least collaborator on BOTH repos. so this is just a gap identified by the token (Azure#42889) Co-authored-by: Scott Beddall <scbedd@microsoft.com>

* 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 (Azure#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>

…ion (Azure#43292) * Updated namespaces for sdk based on SDK team recommendation * nit: removed extra space * JS expect @azure-rest/ pattern in namespace

* Update client.tsp for SDK customizations * Update client.tsp SDK customizations * Update client.tsp customizations

… CognitiveServices.Management (Azure#43088) * remove api version pin * change just to retrigger build part 1 * change just to retrigger build part 2

Agent-Logs-Url: https://github.com/Azure/azure-rest-api-specs/sessions/d21f084a-4aab-4001-abd8-5cc366b0dcba Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: tejaswiMinnu <14865963+tejaswiMinnu@users.noreply.github.com>

* Added to codeowners * Updated account name

Co-authored-by: Praveen Kuttappan <prmarott@microsoft.com>

@route

* initial tsp * copilot routes and main definition completion * use templates, simplify, docs * fix copilot template updates * more template usage * fix templates * file op templates * add missing template * clean up createPermission * update error def * generate swagger * add auth * fix metadata header and shared quota optional header * standard op suppression and some header fixes * configure tspconfig.yaml * regen the swagger * clean up 200 status code * add docs * more docs * more docs * format * process more operation params * more agent fixes * namespace and other fixes * models clean up * more models clean up * routes.tsp updates * clean up and formatting * add examples dir * swagger checks * v2 structure * regen the swagger * sdk configs and suppressions * format * suppressions * cspell * comment out sdk configs until migration work * breaking changes check * address breaking changes * breaking changes check * make date header private * format * misc fixes * fix error def * fix file type param * header fixes * accuracy fixes * update constant * breaking changes check * fix template * fix enum * misc fixes * improve accuracy * add paging * remove shareName, directoryName, fileName * JS: customization * JS: enable emitter options * Add LeaseTimeResponseHeader and update routes to use it - rename leaseTime to leaseTimeInSeconds for JS * Add LeaseActionParameter and refactor code * Add client option for metadata headers and update metadata alias for multiple languages * Add experimental extensible enums option to JS emitter configuration * Add client name mapping for signedDelegatedUserTenantId in UserDelegationKey * rename "mode" => "fileMode" to match swagger * Add legacy pageable disabling for listHandles in Directory and File * Rename to match swagger client names fileCopyModeCopyMode => fileModeCopyMode fileCopyOwnerCopyMode => fileOwnerCopyMode * Remove client name mappings for HandleItem properties in FileStorage client * Rename numberOfHandlesFailed to numberOfHandlesFailedToClose in Directory and File interfaces * wip -revert * JS adjust renames * Add CopyStatus enum and update copyStatus type in File interface * Update fileLastWriteTime type to utcDateTime and add RFC 7231 encoding * Add AllowTrailingDotParameter to File interface * Rename sourceAllowTrailingDot to allowSourceTrailingDot in AllowTrailingDotParameter alias * Add LeaseActionParameter to Share interface operations * Renames based on x-ms-client-name in swagger * remove @route("?comp=copy") from startCopy operation the rest api doc doesn't have it and it causes mismatch with recordings. https://learn.microsoft.com/en-us/rest/api/storageservices/copy-file * Rename structuredBodyGet and structuredBodyPut to structuredBodyType in File interface to follow swagger client name customization * Undo incorrect JS renames of maxResults * rename contentMd5 => contentMD5 to follow client name customization in swagger. use `bytes` as input type * copy SignedIdentifiers code from Blob * remove lease action names from route path * remove `fromURL` from uploadRangeFromUrl route path * fix xml names - StorageServiceProperties.protocol - ShareProtocolSettings.{Nfs,Smb} * update getAccessPolicy request body to SignedIdentifiers * port renames - structuredBody => structuredBodyType to follow swgger client name - apiVersion => version expected by storage * update list files and directories response by following existing Blob pattern * JS: remove incorrect rename on FileProperty.lastAccessTime * update xml name for Range and ClearRange arrays * rename to match x-ms-client-name in swagger for headers - x-ms-share-max-burst-credits-for-iops - x-ms-share-next-allowed-quota-downgrade-time - x-ms-share-next-allowed-provisioned-iops-downgrade-time - x-ms-share-next-allowed-provisioned-bandwidth-downgrade-time - x-ms-share-provisioned-iops - x-ms-share-provisioned-bandwidth-mibps - x-ms-share-provisioned-ingress-mbps - x-ms-share-provisioned-egress-mbps * update *DowngradeTime data type to utcDatetime * update fileContentMD5 type from string to bytes * update abortCopy route to remove `&copyid` * update etag types and regen * clean up aliases * update range headers and regen swagger * clean up empty routes * update AccessPolicy definition * more AccessPolicy updates * add encoding for date time types * python -> omitSlashFromEmptyRoute * python -> generation * python -> datetime to str * file and upload page optional content_type, alternatetype string python * opt content-type for shareAcl * utcdatetime-> str python * forward to stg102 * reset original swagger * enable csharp generation (Azure#41852) * move inline params to aliases for maintainability * regen the swagger * add client.tsp suppressions and format * format * update readme * go first generation * go clients * csharp: more customizations (Azure#42134) * go customizations * more go renames * more go customizations * update content-type definition * regen the swagger * pytohn -> config * update data time types * increase type format specificity * fix ref and regen * clean up header defs * format * suppression * more header and param clean up * add fixed width encoding * move customization to client.tsp * etag -> python * update props to int32 * clean up customizations * csharp customizations for backcompat (Azure#42431) * add missing headers * rust customizations * update file interface ref * regen the swaggers * format * go customizations * more go customizations * format * make the new namespace opt in * clean up repeat headers * JS: use Dates in FileCreationTimeResponseHeader Co-authored-by: Copilot <copilot@github.com> * JS: namespaces is irrelevant so removing * datetime issue python * typo * fix FileProperty * fix lastmodified * File storage: update keyinfo start and expiry types for accuracy (Azure#42874) * accuracy fixes * add encoding for 7 digit precision * clean up --------- Co-authored-by: catalinaperalta <caperal@microsoft.com> * more type fixes * clean up comments * go time fixes * Go signedDelegatedUserTid * ProvisionedBandwidthMibps * fix doc * RequestID * optionalbody * fix download response headers * remove rust customizations * standardize comments with copilot --------- Co-authored-by: catalinaperalta <caperal@microsoft.com> Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com> Co-authored-by: Libba Lawrence <llawrence@microsoft.com> Co-authored-by: Jorge Rangel <102122018+jorgerangel-msft@users.noreply.github.com> Co-authored-by: gracewilcox <graceawilcox@gmail.com> Co-authored-by: Copilot <copilot@github.com>

…zure#41958) * Add MachineLearningServices preview API version 2026-03-15-preview swagger * Add Ray distribution type to MachineLearningServices 2026-03-15-preview (Azure#42127) * Expand LintDiff suppressions for 2026-03-15-preview tag The default tag shifted from preview (2026-01-15-preview) to stable (2026-03-01) after the stable merge. LintDiff now compares stable vs preview baseline, surfacing pre-existing violations that were previously masked by preview-to-preview comparison. All suppressed violations are verified pre-existing in the 2026-01-15-preview swagger. Global suppressions (matching stable tag approach): DeleteResponseCodes, ProvisioningStateMustBeReadOnly, GetCollectionOnlyHasValueAndNextLink, PostResponseCodes, PatchIdentityProperty, PatchBodyParametersSchema, PathForResourceAction, ResourceNameRestriction, CollectionObjectPropertiesNaming, ProvisioningStateSpecifiedForLROPut, PatchResponseCodes, PutResponseCodes, XmsPageableForListCalls. Targeted suppressions with WHERE clauses: - AvoidAdditionalProperties: 78 paths across 10 logical groups (dictionary types for env vars, job I/O, metadata, Spark config, monitoring signals, K8s infra, traffic routing, model registries, polymorphic models, and diagnostics) - XMSSecretInResponse: 7 paths (compute secrets, datastore creds) - GuidUsage: 1 path (Azure.Core.uuid TypeSpec built-in) - UnSupportedPatchProperties: 1 path (managedNetworks PATCH) * fix: revert default tag to stable package-2026-03-01 The default tag must remain the latest stable version. Preview tags exist as opt-in (--tag=package-preview-2026-03-15-preview). Changing the default to a preview tag caused Avocado MISSING_APIS_IN_DEFAULT_TAG (30 deprecated API paths not in preview spec) and LintDiff to report 527 false-positive new violations from cross-file comparison. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix ParametersSchemaAsTypeObject suppression paths to match violation jsonpath The suppression 'where' clauses were using dot notation (parameters.5) without the full path to the violation location. The Spectral validator reports violations at parameters[N].schema.type, so suppressions must use bracket notation with the full path (parameters[5].schema.type) to match correctly. This aligns with the working format used in older preview tags (2025-10-01-preview, 2025-07, etc.). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chore: empty commit to retrigger CI pipeline TypeSpec requirement check timed out — retriggering. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: ahyerman <10575616+ahyerman@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…-leases/pki/Microsoft.Pki/Pki/lease.yaml (Azure#43312)

…n dashboard in auto generated SDK pull request (Azure#43315) * Update release plan info to inlcude information about new release plan dashboardin auto generated SDK pull request

@Format

…zure#41963) * Add v2026-05-01-preview API version with dynamic threshold support Extends the CloudHealth API spec with a new version that introduces dynamic threshold evaluation for signal definitions. Changes include: - Dynamic operator added to SignalOperator enum - ThresholdRuleV2 threshold made optional for dynamic operators - New DynamicThresholdSensitivity enum (Low/Medium/High) - New lookBackWindow property for historical analysis window - v2026-05-01-preview examples and generated swagger Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add v2026-05-01-preview tag to readme.md and update default Fixes Avocado UNREFERENCED_JSON_FILE and LintDiff SpecModelError by referencing the new swagger in readme.md and setting the default tag to the latest API version. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * updates to doc comments * remove dimension * fix sample * Added TODO comments * Added new api contracts to tsp files for data annotations * ran prettier * removed @Format in main.tsp * ran tsp compile * updated lint errors * updated annotation properties name * Ran lint diff locally. added supression * updated examples * updtated correct examples for compile * Added pagination * removed pagination decorators * updating to reflect comments in pr of ahm * skip token approach * add getRecommendedSignals api * updates to msin tsp * fixing lint issue * Revert "fixing lint issue" This reverts commit 26609ca. * fixing error * fixing lint * rename * fmt * updating naming * updates to fix build lint issue * updating naming * updated getRecommendSignals * cloudhealth: tighten data annotation value length to 256 chars Mirror of HIP PR #15385901 review feedback: cap each value in DataAnnotationRequest.annotationDetails at 256 characters by introducing a string256 scalar and switching Record<string4096> -> Record<string256>. TypeSpec cannot express a max-entries constraint on Record, so the 10-entry cap is documented on the property and will be enforced server-side. * cloudhealth: simplify annotationDetails doc comment Trim the property documentation to the essentials (256-char value limit, 10-entry maximum per annotation) without the rationale text. * cloudhealth: add trailing period to annotationDetails doc * rename continuationToken * secret * fmt * secret * small updates * secret 4096 * typo * get history pagination * one annotation object * fix * update readme * feat: added resource health from availability status api changes * fix tsp errors * fix tsp * tsp compiled files * examples * small change * add missing default * fmt * rename recommendation api * missed one * Add ARH availability fields to AzureResourceHealthSignalStatus Extends the 2026-05-01-preview AzureResourceHealthSignalStatus model with four new read-only fields surfaced by Azure Resource Health: summary, reasonType, reasonChronicity, availabilityReportedTime. Also corrects the category doc-string to 'Whether the status changing event was planned or unplanned.' to match the AHM source TypeSpec. Updates Entities_Get example to demonstrate the new fields and regenerates the swagger via tsp compile. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Correctly name availability state (not status) Mirrors the AHM main.tsp rename: availabilityStatus -> availabilityState and ResourceHealthAvailabilityStatusSignalBehavior -> ResourceHealthAvailabilityStateSignalBehavior. Updates the Entities_Get example and the @doc descriptions to match the renamed property, and regenerates cloudhealth.json via tsp compile. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Apply tsp format to cloudhealth client.tsp Run `tsp format` (TypeSpec 1.12) to satisfy the spec-repo Format rule. Three `@@clientName` decorator blocks for DynamicThresholdSensitivity, GetDataAnnotationsRequest, and GetDataAnnotationsResponse now place the first argument on its own line, matching the formatter's output. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update doc strings for dynamic thresholds * remove secret from continuation token * Address PR Azure#41963 review feedback on v2026-05-01-preview Renames pagination cursor properties from continuationToken to nextMarker and applies the @continuationToken decorator. The new name avoids the XMSSecretInResponse linter rule (which matches on "token" in property names) while keeping pagination wiring intact via the semantic decorator. The property is new in 2026-05-01-preview so there is no compat impact. Reverts unconditional @doc rewrites that had propagated into the released 2025-05-01-preview and 2026-01-01-preview swaggers. The new wording referenced the Dynamic operator and pagination semantics that don't exist in those versions. Affected fields: ThresholdRuleV2 threshold and operator, EvaluationRule.degradedRule, ResourceMetric dimensionFilter, and the History request startAt/endAt. The Dynamic-operator constraint is restored on SignalOperator.Dynamic (already version-scoped); the pagination mutual-exclusion constraint is restored on the request-side nextMarker properties. Adds four extensible-enum unions for Azure Resource Health values (availability state, category, reason type, reason chronicity) and retypes the matching properties on AzureResourceHealthSignalStatus to those unions. Mirrors upstream Microsoft.ResourceHealth modelling. Makes DiscoveryRuleProperties.addResourceHealthSignal optional with default Enabled, matching the sibling AzureResourceHealthSignal.enabled pattern and avoiding a 400 for clients migrating from 2026-01-01-preview. Adds maxProperties: 10 to DataAnnotation.annotationDetails via @extension so the server-enforced cap is expressible in the schema. Retypes ThresholdRuleV2.lookBackWindow from string to duration so SDK generators produce strongly-typed timespan values. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Harmonize top schema-default encoding across paginated request models EntityHistoryRequest.top and SignalHistoryRequest.top now declare their default of 1000 in the schema rather than mentioning it only in the @doc; GetDataAnnotationsRequest.top already declared its default of 100 in the schema and now mentions it in @doc for consistency. All three paginated requests follow the same shape now. The older preview swaggers also pick up a small doc-text cleanup on dimensionFilter ("Must only be set if also Dimension is set" → "Must only be set if Dimension is set") that was pending in the TSP source. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Drop schema-enforced cap on annotationDetails entries The @extension("maxProperties", 10) decorator triggers the @azure-tools/typespec-azure-core/no-openapi lint rule, which the team treats as blocking. Other forms (@OpenAPI.extension, x-ms-maxProperties prefix) trigger the same rule, and the only repo precedent for the decorator (deviceupdate) tolerates it via a tspconfig-level rule disable justified by swagger-migration legacy — not a precedent that applies to a greenfield spec. The 10-entry cap remains documented in the @doc and is server-enforced. Clients exceeding it still get 400s; the schema just no longer declares the cap. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address PR Azure#41963 feedback on v2026-05-01-preview docs - Revert two uniform-versioning regressions in prior preview swaggers: EvaluationRule.unhealthyRule description and the dimensionFilter description on ResourceMetricSignalDefinitionProperties had drifted from the as-published wording; restored so 2025-05-01-preview and 2026-01-01-preview swaggers are byte-identical to main. - Clarify @doc strings in v2026-05-01-preview: - DataAnnotation.annotationDetails: qualify the 10-entry cap and 256-char value cap as service-enforced rather than schema-enforced. - SignalOperator.Dynamic: note the required sensitivity and lookBackWindow fields and that threshold is ignored. - DiscoveryRuleProperties.addResourceHealthSignal: name the Enabled default and explain the Disabled opt-out for migration. - Add @added(v2026-05-01-preview) to the ResourceHealthAvailabilityStateSignalBehavior union so the version contract is explicit (preventative — union currently only referenced from v2026-05-01-preview properties). - Delete orphan example HealthModels_GetSuggestedSignals.json — the operation it referenced was renamed and reshaped to HealthModels_GetSignalRecommendations and the orphan was unreachable from any x-ms-examples entry. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix lookBackWindow example values: PT7D is invalid ISO 8601 ISO 8601 duration syntax requires the `T` separator only before time-of-day components (H/M/S). `D` is a date component, so the correct form for "7 days" is `P7D`. The previous wording `PT7D` caused oav-runner to reject the lookBackWindow examples on three operations with "INVALID_FORMAT: Object didn't pass validation for format duration". Replace the value in all six example files (three under the TypeSpec source examples directory and three under the emitted resource-manager examples directory). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address PR Azure#41963 feedback on v2026-05-01-preview spec - Restrict lookBackWindow to a closed set {PT5M, PT15M, PT30M, PT1H} via a new named string union, replacing the unconstrained duration type - Rename SignalConfiguration.id to signalId with @minlength(1)/@maxlength(256) to avoid collision with the ARM resource id convention and to bring length constraints in line with sibling properties on the same model - Update @Identifiers decorators on the GetSignalRecommendationsResponse arrays from #["id"] to #["signalId"] to match the rename - Enrich GetSignalRecommendationsResponse docs to make explicit that recommendedSignals and recommendedConfigurations are independent suggestion streams (broadly-recommended-by-default vs opt-in with starting-point thresholds), restoring the semantic dropped when the prior tagged array was split - Add @added(v2026_05_01_preview) uniformly to all seven AzureResourceHealthSignalStatus fields; the parent derives via `is SignalStatus` (added in v2026_01_01_preview), so explicit field-level @added is required to keep the new fields out of the prior version swaggers - Update example payloads accordingly (P7D->PT1H, id->signalId) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Scope getSignalRecommendations to a per-entity action Move getSignalRecommendations from the HealthModels interface to Entities, so it is an action on a specific Entity rather than a generic catalog query parameterised by an arbitrary HealthModel + free-form resource type. The Entity itself encodes the resource type the recommendations apply to, so the request body is now void; the new path is /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName} /providers/Microsoft.CloudHealth/healthmodels/{healthModelName} /entities/{entityName}/getSignalRecommendations The change deletes the now-unused GetSignalRecommendationsRequest model and its resourceType property. The example file is renamed to match the new operationId (Entities_GetSignalRecommendations) and reshaped to use entityName as a path parameter with no request body. The GetSignalRecommendationsResponse model docs are updated to reflect that the resource type is implicit in the target Entity rather than supplied in the request body. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Tighten addDataAnnotation request shape and GetSignalRecommendations response Introduce a dedicated AddDataAnnotationRequest model carrying only the user-supplied annotationDetails and description fields, and use it as the body of the addDataAnnotation action. The action continues to return the full DataAnnotation, so server-assigned annotationId and createdAt remain on the response only. Mark recommendedSignals and recommendedConfigurations on GetSignalRecommendationsResponse as required arrays, matching the convention followed by the other collection-bearing action responses in this spec. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Extend AvoidAdditionalProperties suppression to AddDataAnnotationRequest The previous commit introduced AddDataAnnotationRequest as a dedicated request model for the addDataAnnotation action. Its annotationDetails property reuses the same dynamic key-value Record<string256> shape as DataAnnotation.annotationDetails, which carries an existing LintDiff suppression for the same approved scenario. Add the new model's JSONPath alongside it so LintDiff covers the request side as well as the domain-model side. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Matthew Hall <matthewhall@microsoft.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Sebastian Bader <sebader@microsoft.com> Co-authored-by: Megan Goode <megangoode@microsoft.com> Co-authored-by: Amy Richardson <amrichardson@microsoft.com> Co-authored-by: Sebastian <11445087+sebader@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Hansjoerg Scherer <hjscherer@users.noreply.github.com>

@visibility

* Add API version 2025-07-01 for Microsoft.Network (Azure#41904) * Add API version 2025-07-01 for Microsoft.Network * Add stable/2025-07-01 OpenAPI specs and examples * Fix tsp format indentation in main.tsp * Add cspell suppressions for stable/2025-07-01 spell check errors * Fixed some issues based on suggestions from Reviewer * Fixed some values in the examples folder --------- Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com> * [Ddos] Add ILPIP DCP in 2025-07-01 TypeSpec/Swagger (Azure#42075) * [Network] Add ILPIP DCP in 2025-07-01 TypeSpec/Swagger * Update DCP references and regenerate 2025-07-01 network swagger * Add version gates for DCP properties in 2025-07-01 * Revert "Add version gates for DCP properties in 2025-07-01" This reverts commit 8ffec04. * Fix: Reorder decorators to match file formatting standard - Move #suppress decorators before @visibility decorators - Fixes TypeSpec format validation (tsp format --check) - Both properties have camelCase naming from REST spec, suppress documents this * Update 2025-05-01 virtualNetwork.json * Regenerate vmssNetwork swagger for DDoS custom policy updates * Scope DCP changes to 2025-07 and revert non-target generated files * Add back-compat gates for DCP properties across Network and Vmss * Apply TypeSpec format updates for Network DCP compatibility * Fix shared/vmss compatibility gates for DCP compile --------- Co-authored-by: Venkata M <venm@microsoft.com> * Sync network from main (Azure#42251) * Replace Network/Common NameSpace (Azure#42225) * update * update * update * update client.tsp * format * replace * update client.tsp * add versions in common * compile * Add ddosSettingsProperty on loadbalancer's frontendIpConfiguration. Also all list command for DdosCustomPolicy resource (Azure#42054) * Add tsp changes * Add swagger changes * Add examples * remove supress for casing * remove missing example * address comments * fix avaocado MULTIPLE_API_VERSION rule * Supress Avacado MULTIPLE_API_VERSION * Revert "fix avaocado MULTIPLE_API_VERSION rule" This reverts commit c84ca6f. * Revert "Supress Avacado MULTIPLE_API_VERSION" This reverts commit f1f769f. * addall files generated * Add missing file * update examples folder * fix version * reset older changes * remove remaining * Add version check * add version check on DCP list and listAll too * fix tsp validation because of version check on common resource.Moved the check upstream * use new way * Update with checks after release rebase --------- Co-authored-by: Giri Bhatnagar <gibhatna@microsoft.com> * Add New Resource Network Manager Commit (Azure#42070) * Add New Resource Network Manager Commit Port changes from PR Azure#40919 to release-microsoft-network-2025-07-01 branch. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix references in networkManagerCommit.json Replace broken ./network.json refs with correct paths: - SubscriptionIdParameter/ApiVersionParameter -> common-types/v5 - CloudError/ChildResource/ProvisioningState -> ./common.json - SystemData -> common-types/v5/systemData - ConfigurationType -> ./common.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Merge networkManagerCommit.json into networkManager.json - Moved commit paths, definitions, and parameters into networkManager.json - Inlined parameters to match networkManager.json conventions - Added pattern validation on networkManagerName parameter - Removed separate networkManagerCommit.json file - Removed networkManagerCommit.json suppressions from readme.md - Removed networkManagerCommit.json from readme.md input-file list Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add Commits tag to networkManager.json tags list Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix Avocado and TypeSpec Validation failures - Revert networkManagerCommit.json merge into networkManager.json (networkManager.json is TypeSpec-generated, cannot be manually edited) - Keep networkManagerCommit.json as a separate swagger file - Add MULTIPLE_API_VERSION avocado suppression for vmssNetwork.json - Restore ResourceNameRestriction and SystemDataDefinitionsCommonTypes suppressions for networkManagerCommit.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add Commit resource via TypeSpec instead of separate swagger - Created Commit.tsp defining Commit as a child resource of NetworkManager with GET, PUT (async), DELETE (async), and List operations - Added @added(Versions.v2025_07_01) to scope Commit to 2025-07-01 only - Regenerated networkManager.json with tsp compile (includes Commit CRUD) - Removed separate networkManagerCommit.json (now generated via TypeSpec) - Removed networkManagerCommit.json suppressions from readme.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove MULTIPLE_API_VERSION suppression from readme.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update suppression reasons in Commit.tsp with explicit justifications Replace generic FIXME placeholders with specific reasons documenting why ChildResource pattern is used (consistency with all existing Network Manager child resources like ScopeConnection, AdminRuleCollection, ConnectivityConfiguration, etc.) rather than ProxyResource<T>. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address ravimeda's review feedback on Commit resource - Fix example resource IDs: add leading / to all id fields (EX-RESOURCE-ID) - Fix nextLink URL: managedNetworks -> networkManagers (EX-PAGINATION) - Add operationId to all example files for autorest emitter discovery - Copy examples to TypeSpec examples/2025-07-01/ folder - Regenerated swagger now includes x-ms-examples for all Commit ops - Fix forceUpdateTag description to clarify force-update semantics - Fix list operation description: 'Lists all commits for the specified network manager' instead of 'Lists the specified commit' Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Document rationale for omitting PATCH operation on Commits Commits are immutable deployment records where partial updates are not semantically meaningful, consistent with other Network Manager child resources (ScopeConnection, ConnectivityConfiguration, etc.). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix ModelValidation: add 200 response to Commits_Delete example The generated swagger includes a 200 response code for the delete operation but the example file only had 202/204. Added 200: {} to match, consistent with other Network Manager delete examples. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix Avocado, ModelValidation and LintDiff failures Avocado: Re-add MULTIPLE_API_VERSION suppression for vmssNetwork.json ModelValidation: - Fix nextLink URL: replace {baseurl} with https://management.azure.com - Fix PUT example: rename body param 'parameters' to 'resource' LintDiff: - Add @pattern to commitName parameter (ResourceNameRestriction) - Remove 200 from delete responses (DeleteResponseCodes: LRO delete must only have 202, 204 and default) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix nextLink: use relative path instead of absolute URL Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix ModelValidation: use full URI for nextLink, remove 200 from delete example - nextLink must be a valid URI (relative path fails format validation) - Delete example had stale 200 response not in swagger Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Run tsp format on Commit.tsp to fix TypeSpec Validation Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix Avocado MULTIPLE_API_VERSION suppression format Move suppression from 'suppressions' section (LintDiff format) to 'directive' section with 'suppress:' keyword (Avocado format). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix LintDiff: suppress ProvisioningStateMustBeReadOnly for Commit Add targeted suppressions for 3 new Commit-specific violations only. provisioningState IS readOnly in CommitProperties definition but the linter does not follow \ chains to verify in response schemas. Same pattern exists for all other NM resources (pre-existing). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix broken $ref pointers in networkManager.json (2025-07-01) Fix 5 unresolvable references in networkManager.json: - 4x CloudError -> Common.CloudError - 1x ProvisioningState -> Common.ProvisioningState These broken refs caused SemanticValidation, LintDiff, and SDK Validation CI failures. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add missing Common import to Commit.tsp Add import '../Common/main.tsp' and 'using Common' to resolve unknown identifier errors for ProvisioningState, Features, and CloudError. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add common useDependency 2025-07-01 in VMSS (Azure#42312) * update * remove @removed * Arjun/vna vnet changes 2025 07 01 (Azure#42049) * Update VNA and VNet properties: add PrivateIPAddressVersion and SummarizedGatewayPrefixes - bandwidthInGbps: string to float64 - Add privateIPAddressVersion property with VirtualNetworkApplianceIpVersionType enum (IPv4, DualStack) - Add summarizedGatewayPrefixes on VirtualNetworkPropertiesFormat - Add versioning decorators for v2025_07_01 API version changes - Update all VNA example files with new properties * Update swagger: add privateIPAddressVersion, VirtualNetworkApplianceIpVersionType, summarizedGatewayPrefixes, and fix bandwidthInGbps type * Fix TypeSpec compilation errors: suppress casing-style and remove Versions ref from Common * Add @@added versioning for summarizedGatewayPrefixes via augment decorator Use augment syntax from Network/models.tsp since Versions is not available in Common/main.tsp (shared with Vmss which only has v2018_10_01). * Align swagger with TypeSpec compiler output Accept tsp compile generated swagger: move VirtualNetworkApplianceIpVersionType to common.json, add format:double, fix ref path, revert example changes to match generated output. * Regenerate vmssNetwork swagger from TypeSpec * Fix lint: update enum descriptions to not match node names * Fix examples: bandwidthInGbps must be number not string * Fix source examples: bandwidthInGbps must be number not string * Address ARM review feedback for VNA VNet changes 2025-07-01 - Fix bandwidthInGbps type versioning: use @typeChangedFrom to keep string type in 2025-05-01 and change to float64 only in 2025-07-01 - Revert 2025-05-01 examples to use string value for bandwidthInGbps - Remove summarizedGatewayPrefixes from 2018-10-01 vmssNetwork.json (violates API version immutability) - Update summarizedGatewayPrefixes description to clarify it is configurable - Fix FIXME suppression placeholder for privateIPAddressVersion casing * Fix summarizedGatewayPrefixes leaking into 2018-10-01 Vmss output Add @@removed decorator in Vmss/back-compatible.tsp to prevent summarizedGatewayPrefixes from appearing in the 2018-10-01 vmssNetwork.json. The property is defined in Common/main.tsp (shared across projects) but should only appear in 2025-07-01+. The @@added gate in the Network project does not apply during Vmss compilation. * Fix ambiguous Versions reference in Vmss back-compatible.tsp Fully qualify as Microsoft.Compute.Versions.v2018_10_01 to resolve ambiguity between Microsoft.Compute.Versions and Microsoft.Network.Versions. * Add MULTIPLE_API_VERSION suppression for default tag The default tag includes 2018-10-01/vmssNetwork.json alongside 2025-07-01 files. This is expected since the Vmss APIs are a separate TypeSpec project (Microsoft.Compute) with only a 2018-10-01 version. * Fix MULTIPLE_API_VERSION suppression: use directive/suppress format The suppressions/code format doesn't work for this rule. Use the directive/suppress format as done in AlertsManagement Legacy readme. * undo suppression * Regenerate swagger JSON files from TypeSpec * Move @added decorator to Common/main.tsp and remove @@removed from Vmss/back-compatible.tsp per PR Azure#42054 pattern * remove whitespace * Users/anjbal/nat64 ts (Azure#42176) * Nat64 Changes * Auto generated code * Changed file * Description Fix * NIT Fix * Auto generate code * TypeSpec Validation * Add description * Description updated * Add Managed HSM support to Application Gateway for 2025-07-01 (Azure#42137) * Add Managed HSM support to Application Gateway for 2025-07-01 Add ApplicationGatewayManagedHsm type definition and hsm property to ApplicationGatewaySslCertificatePropertiesFormat in both TypeSpec source (models.tsp) and generated JSON (applicationGateway.json). Original PR: Azure/azure-rest-api-specs-pr#23831 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add @added(Versions.v2025_07_01) decorators to HSM model and property Mark ApplicationGatewayManagedHsm model and hsm property with version decorator to properly indicate they are new in the 2025-07-01 API version, following the same pattern as PR Azure#42054. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix TypeSpec validation: replace @Format with url scalar type Remove @Format("uri") decorator (forbidden by no-format rule) and use the built-in url scalar type instead. Also replace boilerplate suppression justification with a real one. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Regenerate applicationGateway.json from tsp compile Run tsp compile to regenerate JSON output matching the TypeSpec source. Fixes TypeSpec Validation CI check. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Srijani Sen <srijanisen@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add DisablePeeringRoute property to RouteTable TypeSpec for API version 2025-07-01 (Azure#42058) * Add DisablePeeringRoute property to RouteTable TypeSpec (2025-07-01) * Remove unnecessary TypeSpec.Versioning import from models.tsp * Retrigger CI checks * Fix Vmss compilation: use augment decorators for versioning and regenerate vmssNetwork swagger * Regenerate swagger after merging prerequisite PR Azure#42312 --------- Co-authored-by: Sonal Singh (from Dev Box) <sonalsingh@microsoft.com> * Add ECMP routing support for Network Route Tables. (typespec update) (Azure#42053) * NRP ECMP support. * Adding Examples and AVNM updates. * Resolved review comments from ravimeda. * Revert changes to 2018-10-01/vmssNetwork.json to fix lint/breaking-change checks * Revert "Revert changes to 2018-10-01/vmssNetwork.json to fix lint/breaking-change checks" This reverts commit 3f0ca7a. * Fix DescriptionMustNotBeNodeName lint error for None enum values * Adding Examples and AVNM updates. * Trigger CI * Fix duplicate ECMP example reference in virtualNetwork.json --------- Co-authored-by: nsiddabasapp <nsiddabasapp@microsoft.com> Co-authored-by: Sonal Singh (from Dev Box) <sonalsingh@microsoft.com> * Detail level parameter new (Azure#42056) * Added work necessary for detailLevelParameter Added work necessary for detailLevel parameter in Get LB call. * Prettier * Sku name fix on Scope examples * Add suppression * TSP changes * Suppression and examples * Compile tsp * Fix readme.md: remove duplicate tag section and correct suppression placement * Add MULTIPLE_API_VERSION suppression for pre-existing vmssNetwork.json in default tag * Address comments * Remove instructions file * Readme * fix: remove where clause from ParametersInPointGet suppression in readme.md The where clause used single-quoted JSONPath which is non-standard. Removing the where clause to use a simpler, proven suppression pattern (similar to DevTestLabs and other services). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: restore where clause to ParametersInPointGet suppression with correct JSONPath Two bugs in the original where clause: 1. Single quotes in JSONPath brackets (non-standard, evaluates to nothing) 2. Path ended at .get instead of .get.parameters (rule reports at parameters level) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Swagger changes for afc configuration (Azure#42245) * Swagger changes for afc control plane * Add afcControlPlaneConfiguration to Azure Firewall TypeSpec and generated swagger for 2025-07-01 * Renamed the response * Swap parameter order * [NSP] ResourceAssociable API - release swagger update (Azure#42403) * [NSP] ResourceAssociable API - release swagger update * Resolving Comments * Remving Custom Name for Enum for SDK * Removing Custom Property * Adding Custom Property * Add new properties to PerimeterAssociableResourceProperties via TypeSpec and regenerate swagger * TypeSpec Related Changes * Updating Descriptions * Updating TSP file to have correct description --------- Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn> * Add RoutingConfiguration property for hubBgpConnection and virtualNetworkGatewayConnection (Azure#42409) * Add RoutingConfiguration support for VirtualNetworkGatewayConnection and HubBgpConnection * push generated swagger files --------- Co-authored-by: Ira Ramtirth <irramtir@microsoft.com> * update the captcha expiration property (Azure#42106) * update the captcha expiration property * Regenerate Network swagger from TypeSpec * Make propagateStaticRoutes read/write (Azure#42616) Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com> * Swagger changes for Vwan Express Route Gateway Failover and Insights (Azure#42560) * swagger changes for vwan express route gateway apis * fixed errros * fixed errros * fixed errros * fixed errros * add suppression * Delete specification/network/resource-manager/Microsoft.Network/Network/sdk-suppressions.yaml * reverted back compatible.tsp --------- Co-authored-by: Shubhika Jain <shujai@microsoft.com> Co-authored-by: judy <1002946066@qq.com> Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn> Co-authored-by: Venu Sivanadham <56538710+venu-sivanadham@users.noreply.github.com> * Connection policy changes (Azure#42745) Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com> * Swagger changes for Circuit link failover APIs (Azure#42555) (Azure#42729) * link fialover swagger * fixed errors * added in readme * add suppression * update suppression * updated doc * reverted back-compatible changes * Merging Circuit link failover final cp 2 branch with latest pull (Azure#42690) * Make propagateStaticRoutes read/write (Azure#42616) * Swagger changes for Vwan Express Route Gateway Failover and Insights (Azure#42560) * swagger changes for vwan express route gateway apis * fixed errros * fixed errros * fixed errros * fixed errros * add suppression * Delete specification/network/resource-manager/Microsoft.Network/Network/sdk-suppressions.yaml * reverted back compatible.tsp --------- --------- * resolved merged conflicts:1 (Azure#42715) --------- Co-authored-by: Shubhika Jain <shujai@microsoft.com> Co-authored-by: judy <1002946066@qq.com> Co-authored-by: Venu Sivanadham <56538710+venu-sivanadham@users.noreply.github.com> Co-authored-by: Rajkumar Chepala <rchepala+github@microsoft.com> Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com> Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn> * Remove tags from DDoS protection plan properties (Azure#42850) Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com> * Added Private Endpoint Billing Sku Property in 2025-07-01 (Azure#42367) (Azure#42888) * Added PrivateEndpoints to 2025-07-01 * Added billing sku property to private endpoint * Update references in PrivateEndpoint to Common file and Update Readme with 2025-07-01 PrivateEndpoint * Reverted changes- Added BillingSku to PrivateEndpoint resource in VirtualNetwork file * Restored and Updated/Generated swagger change with TypeSpec * Removed extra line * added vmss for typespec validation * Default description * Descriptions * CP Add Microsoft.Network/InterconnectGroups TypeSpec for 2025-07-01 (Azure#42331) (Azure#42933) * Add Microsoft.Network/InterconnectGroups TypeSpec for 2025-07-01 - Add InterconnectGroup tracked resource with CRUD operations - Add Subgroup nested resource with Get and List operations - Add GetNodeAvailability async POST action - Models aligned with NRP source: InterconnectGroupScope, SubgroupProfile, SubgroupProperties (internalSubgroupId), InterconnectGroupNodeAvailability, SubgroupNodeAvailabilityEntry * Refactor Commit to use ProxyResource<T> per review feedback Switch Commit model from ChildResource to ProxyResource<CommitProperties> per markcowl's review: - Remove @Http.Private.includeInapplicableMetadataInPayload (unnecessary with ProxyResource) - Remove explicit systemData property (included by ProxyResource) - Remove no-private-usage, arm-custom-resource-usage-discourage, and composition-over-inheritance suppressions (no longer applicable) - Use 'is' instead of 'extends' for composition over inheritance Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert "Refactor Commit to use ProxyResource<T> per review feedback" This reverts commit 93949e3. * Addressing PR comments (Azure#43106) Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com> * Apply TypeSpec formatting fixes for Network validation (Azure#43251) Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com> --------- Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com> Co-authored-by: venkatasaimaram7 <venkatasaimaram7@gmail.com> Co-authored-by: Venkata M <venm@microsoft.com> Co-authored-by: mcgallan <88413158+mcgallan@users.noreply.github.com> Co-authored-by: Giri Bhatnagar <giri1gb@gmail.com> Co-authored-by: Giri Bhatnagar <gibhatna@microsoft.com> Co-authored-by: yanfa317 <53584318+yanfa317@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Arjun Patel <94936045+arjun-d-patel@users.noreply.github.com> Co-authored-by: anjbal <137822143+anjbal@users.noreply.github.com> Co-authored-by: srijanee <srijanee.titli@gmail.com> Co-authored-by: Srijani Sen <srijanisen@microsoft.com> Co-authored-by: Sonal Singh <sonalsingh+github@microsoft.com> Co-authored-by: Sonal Singh (from Dev Box) <sonalsingh@microsoft.com> Co-authored-by: nandakishores <32315808+nandakishores@users.noreply.github.com> Co-authored-by: nsiddabasapp <nsiddabasapp@microsoft.com> Co-authored-by: Eugenio Peña García <70240915+EugenioPena@users.noreply.github.com> Co-authored-by: Sai Sujith Reddy Mankala <samankal@microsoft.com> Co-authored-by: henumpa <99614325+henumpa@users.noreply.github.com> Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn> Co-authored-by: irramtir <irramtir+github@microsoft.com> Co-authored-by: Ira Ramtirth <irramtir@microsoft.com> Co-authored-by: Yaniv Sagron <yanivsag@gmail.com> Co-authored-by: Rajkumar Chepala <rchepala+github@microsoft.com> Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com> Co-authored-by: shubhika1795 <32219662+shubhika1795@users.noreply.github.com> Co-authored-by: Shubhika Jain <shujai@microsoft.com> Co-authored-by: judy <1002946066@qq.com> Co-authored-by: Venu Sivanadham <56538710+venu-sivanadham@users.noreply.github.com> Co-authored-by: chrisbrugal <138532458+chrisbrugal@users.noreply.github.com> Co-authored-by: jbouzarouata1 <152891406+jbouzarouata1@users.noreply.github.com> Co-authored-by: Fan Yang (AZURE) <yanfa@microsoft.com>

…child resource on firewalls (API version 2026-05-11-preview) (Azure#43261) * [PaloAltoNetworks] Add 2026-05-11-preview with customCaptureConfigurations resource Adds new ARM API version 2026-05-11-preview for PaloAltoNetworks.Cloudngfw introducing the customCaptureConfigurations sync proxy singleton resource under firewalls. Includes 4 new examples and bootstrapped 192 examples from 2026-01-26-preview (api-version updated). Schema: pcapFilter, pcapStages, durationInSec, storageAccountResourceId marked optional to match backend behavior during InProgress state. * [PaloAltoNetworks] Add 2026-05-11-preview with customCaptureConfigurations resource Adds new ARM API version 2026-05-11-preview for PaloAltoNetworks.Cloudngfw introducing the customCaptureConfigurations sync proxy singleton resource under firewalls. Includes 4 new examples and bootstrapped 192 examples from 2026-01-26-preview (api-version updated). Schema: pcapFilter, pcapStages, durationInSec, storageAccountResourceId marked optional to match backend behavior during InProgress state. * removing extra spaces * Suppress 3 LintDiff rules on customCaptureConfigurations (2026-05-11-preview) * custom capture list and delete operation added --------- Co-authored-by: Rohit Kumar <rohitkuma@microsoft.com> Co-authored-by: Tejaswi Salaigari <tsalaigari@microsoft.com>

* fix * compile * update * compile * format * format * fix parameter order * compile * update * Update client.tsp * Update client.tsp * Update client.tsp * update --------- Co-authored-by: kazrael2119 <98569699+kazrael2119@users.noreply.github.com> Co-authored-by: v-huizhu2 <v-huizhu2@microsoft.com>

* Rename App Configuration deleted stores list method Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Pin App Configuration C# generation API version Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Rename CognitiveServices deleted accounts list for C# Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Work around Policy duplicate C# methods Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Pin Policy C# generation API version Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Scope out Policy resource-level list methods for C# Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Reference Policy workaround tracking issue Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix DeploymentStacks what-if result C# resource name Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert "Fix DeploymentStacks what-if result C# resource name" This reverts commit 05667eb. * Rename AppConfiguration deleted stores list for C# Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Rename AppConfiguration deleted stores list for C# Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Mark Storage service lists pageable for C# Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * revert undesired changes in appconfig * update * add another api-version pin --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* update * Update TomcatWebApplications.tsp

…43332) * Mitigate Python SDK breaking changes for azure-mgmt-maintenance * format --------- Co-authored-by: msyyc <msyyc@example.com>

…zure#41821) * update * update * update * update * update * Update Project.tsp * update * update * Update ActivityLogAlertResource.tsp * update * fix * update * Update VirtualNetworkLink.tsp * update * fix * Update Project.tsp * Update Project.tsp * Update tspconfig.yaml * revert deviceregistry * update * update * update * update * update * update * update * update * update * update --------- Co-authored-by: Jiao Di (MSFT) <80496810+v-jiaodi@users.noreply.github.com> Co-authored-by: Pan Shao <97225342+pshao25@users.noreply.github.com>

* Add etag property to AzureMonitorWorkspaceResource * Fix Issue alert/resource descriptions in TypeSpec (Add or update alerts/resources associated with an issue) * Fix example etag values to use proper RFC 7232 quoted format --------- Co-authored-by: GokulPrasad KrishnaSwamy <gokulpk@microsoft.com>

Co-authored-by: Nicola Camillucci <ncamillucci@microsoft.com>

…re#43351) * [BlobStorage] JS: rename FilteredBlobResponse.blobItems => blobs * fix formatting

* [TextTranslation] Add API version 2026-06-06 * Adding new version to main.tsp * Update readme * Reordering readme * Removing version field * Unifying tag block formats after removing version config * Adding in auth specification * Adding in autogenerated specs for v3 and v4-preview as directed by API review board * Fixing formatting in main.tsp * Removing supression * Add NoAuth to service-level auth, remove grade, convert tone/gender to enums for 2026-06-06 * remove NoAuth, update TextTranslation general doc * Clean up readme.md: reorder releases newest-to-oldest * add NoAuth and suppress unsupported-auth warning * text translation: add java client name customizations * Fix TypeSpec formatting for v1.12.0 compatibility --------- Co-authored-by: Jiarui Guo <jiarguo@microsoft.com> Co-authored-by: Mike Harder <mharder@microsoft.com>

Co-authored-by: Arber Hila <ahila@microsoft.com>

This reverts commit 1942da2.

github-actions · 2026-05-19T20:39:14Z

Next Steps to Merge

⌛ Please wait. Next steps to merge this PR are being evaluated by automation. ⌛

Comment generated by summarize-checks workflow run.

@added

…icrosoft.ComputeBulkActions (Azure#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 Azure#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>

kbhardw4-microsoft and others added 30 commits April 30, 2026 15:05

Add @@clientName decorators for PipelineGroups C# SDK naming (Azure#4…

8e93a7d

…2806) * Add @@clientName decorators for PipelineGroups C# SDK naming

Microsoft.Monitor/pipelineGroup keep dce as string (Azure#42829)

7e192f8

Scripts to generate ARM lease files (Azure#41592)

0a38843

Sync eng/common directory with azure-sdk-tools for PR 15454 (Azure#42864

3d52403

) * fix create-pull-request for source/target token utilization --------- Co-authored-by: Scott Beddall <scbedd@microsoft.com>

update keyinfo start and expiry types for accuracy (Azure#42876)

429070c

Co-authored-by: catalinaperalta <caperal@microsoft.com>

Add Azure Linux 4.0 image aliases (Azure#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 (Azure#42870

f6c1438

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

Pass Npm Config to CSpell (Azure#42910)

f127e37

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

Himanshu49 and others added 27 commits May 18, 2026 15:22

[Playwright] Updated namespaces for sdk based on SDK team recommendat…

61d61ea

…ion (Azure#43292) * Updated namespaces for sdk based on SDK team recommendation * nit: removed extra space * JS expect @azure-rest/ pattern in namespace

Mpcpro/client update for sdk (Azure#43089)

9fd0992

* Update client.tsp for SDK customizations * Update client.tsp SDK customizations * Update client.tsp customizations

feat: remove api-version pin to 2026-01-15-preview for Java and C# in…

71b6871

… CognitiveServices.Management (Azure#43088) * remove api version pin * change just to retrigger build part 1 * change just to retrigger build part 2

Added to codeowners (Azure#43216)

44729a4

* Added to codeowners * Updated account name

Add Release Plan ID in get release plan fields (Azure#43314)

d498419

Co-authored-by: Praveen Kuttappan <prmarott@microsoft.com>

Rename .github/arm-leases/pki/Microsoft.Pki/lease.yaml to .github/arm…

d0f0a2c

…-leases/pki/Microsoft.Pki/Pki/lease.yaml (Azure#43312)

go StorageErrorCode (Azure#43319)

2a41e22

Update release plan info to inlcude information about new release pla…

00b39ba

…n dashboard in auto generated SDK pull request (Azure#43315) * Update release plan info to inlcude information about new release plan dashboardin auto generated SDK pull request

[offazure] Fix for TomcatWebApplicationsController.update (Azure#43296)

7503859

* update * Update TomcatWebApplications.tsp

[Python] Mitigate breaking changes for azure-mgmt-maintenance (Azure#…

6299a04

…43332) * Mitigate Python SDK breaking changes for azure-mgmt-maintenance * format --------- Co-authored-by: msyyc <msyyc@example.com>

Removed basic setup from SecurityDomain SDK (Azure#43347)

827e576

Co-authored-by: Nicola Camillucci <ncamillucci@microsoft.com>

[BlobStorage] JS: rename FilteredBlobResponse.blobItems => blobs (Azu…

781f4b9

…re#43351) * [BlobStorage] JS: rename FilteredBlobResponse.blobItems => blobs * fix formatting

Update documentation (Azure#43144)

e31266e

Co-authored-by: Arber Hila <ahila@microsoft.com>

Merge branch 'main' into nasc/updateV20260401

eabef2f

Revert "Add immutable backups"

f3e1ea0

This reverts commit 1942da2.

update mvu pvc examples

b659f41

nasc17 merged commit 5000244 into nehrao1:nehrao/swaggerUpdateV04012026 May 19, 2026
18 of 31 checks passed

Navigation Menu

Repository navigation

Merge latest code, remove immutable backups, update examples for mvu pvc - #1

Merge latest code, remove immutable backups, update examples for mvu pvc#1
nasc17 merged 222 commits into
nehrao1:nehrao/swaggerUpdateV04012026from
nasc17:nasc/updateV20260401

nasc17 commented May 19, 2026

Uh oh!

Uh oh!

github-actions Bot commented May 19, 2026 •

edited

Loading

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

Conversation

nasc17 commented May 19, 2026

Choose a PR Template

Uh oh!

Uh oh!

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

Uh oh!

Next Steps to Merge

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

github-actions Bot commented May 19, 2026 •

edited

Loading