Skip to content

Add moveIpConfigurations API to 2025-09-01 (port of #42941) - #44735

Merged
rajanalavarnitha-wq merged 3 commits into
Vslokar/release-microsoft-network-2025-09-01from
srajanala/moveipconfigurations-2025-09-01
Jul 22, 2026
Merged

rajanalavarnitha-wq merged 3 commits into
Vslokar/release-microsoft-network-2025-09-01from
srajanala/moveipconfigurations-2025-09-01

Conversation

@rajanalavarnitha-wq

Copy link
Copy Markdown
Contributor

Ports the moveIpConfigurations API from #42941 into the 2025-09-01 API version.

Adapted to @added(Versions.v2025_09_01) and emitted under stable/2025-09-01. Adds the operation (VirtualNetwork.tsp), request/item/reference models (models.tsp), suppressions (readme.md), swagger path + definitions (virtualNetwork.json), and example files.

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

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 3941f2ed-0c8d-482c-b028-6b8d89a5a03e
@github-actions

github-actions Bot commented Jul 16, 2026 •

Copy link
Copy Markdown

Next Steps to Merge

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
If you still want to proceed merging this PR without addressing the above failures, refer to step 4 in the PR workflow diagram.

Comment generated by summarize-checks workflow run.

@github-actions github-actions Bot added ARMReview resource-manager SuppressionReviewRequired TypeSpec Authored with TypeSpec WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jul 16, 2026
@github-actions

github-actions Bot commented Jul 16, 2026 •

Copy link
Copy Markdown

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
TypeSpec Microsoft.Network
Go sdk/resourcemanager/network/armnetwork
Java com.azure.resourcemanager:azure-resourcemanager-network
Python azure-mgmt-network
C# Azure.ResourceManager.Network

Comment generated by After APIView workflow run.

@github-actions github-actions Bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 17, 2026
rajanalavarnitha-wq and others added 2 commits July 17, 2026 12:39
…new moveIpConfigurations op

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 3941f2ed-0c8d-482c-b028-6b8d89a5a03e
LintDiff confirmed the suppression is required: without it, the new LRO POST operation triggers PostResponseCodes (200 with no schema). Reverts experimental removal.
@rajanalavarnitha-wq rajanalavarnitha-wq added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required and removed ARMChangesRequested labels Jul 17, 2026
@sandipsh Sandip Shahane (sandipsh) added Approved-Suppression ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jul 21, 2026
@rajanalavarnitha-wq
rajanalavarnitha-wq merged commit bf9fcb1 into Vslokar/release-microsoft-network-2025-09-01 Jul 22, 2026
114 of 118 checks passed
@rajanalavarnitha-wq
rajanalavarnitha-wq deleted the srajanala/moveipconfigurations-2025-09-01 branch July 22, 2026 00:46
santoshgh317 added a commit that referenced this pull request Aug 10, 2026
* Add API version 2025-09-01 for Microsoft.Network (#44613)

Adds new stable API version 2025-09-01 for Microsoft.Network, following the pattern of PR #41904 and the stable-after-stable versioning guide (https://azure.github.io/typespec-azure/docs/howtos/versioning/05-stable-after-stable/).

Changes:

- Common/main.tsp: add v2025_09_01 enum entry

- Network/main.tsp: add v2025_09_01 with @useDependency(Common.Versions.v2025_09_01)

- Vmss/main.tsp: bump @useDependency to Common.Versions.v2025_09_01

- readme.md: add package-2025-09-01 tag and set as default

- cspell.yaml: add overrides for new stable/2025-09-01 files

- examples/2025-09-01/: 890 example JSONs (copied from 2025-07-01, api-version rewritten)

- stable/2025-09-01/: 17 swagger files + 890 examples (generated via tsp compile)

Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com>

* AFC Managed Firewall Policy (#44867)

* afc managed fp

* More examples

* Add LoadBalancer mode and frontend enableConnectionTracking (2025-09-01) (#44808)

* Add LoadBalancer mode and frontend enableConnectionTracking (2025-09-01)

Add two customer-facing properties gated to API version 2025-09-01:
- mode (LoadBalancerPropertiesFormat), backed by new LoadBalancerMode enum (Advanced),
  modeled create-only via x-ms-mutability [read, create].
- enableConnectionTracking (FrontendIPConfigurationPropertiesFormat); the per-rule setting
  is not supported, configure connection tracking at the frontend level.
Adds a LoadBalancerCreateWithAdvancedMode example demonstrating both.

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

* Update enableConnectionTracking descriptions (frontend + rule level)

Clarify UDP flow tracking semantics: the frontend IP configuration setting applies to all
associated rules and takes precedence; the rule-level property is retained for compatibility.
The rule-level description is ungated, so 2025-05-01/2025-07-01 loadBalancer.json are also
regenerated.

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

* Regenerate vmssNetwork.json (VMSS 2018-10-01) after Common changes

The Vmss TypeSpec project pins @useDependency(Common.Versions.v2025_09_01), so its
2018-10-01 output is generated against the latest Common models. Regenerate to include
the mode/LoadBalancerMode and enableConnectionTracking changes, fixing TypeSpec Validation
drift. Follows the standard release workflow.

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

---------

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

* Add moveIpConfigurations API to 2025-09-01 (port of #42941) (#44735)

* Add moveIpConfigurations API to 2025-09-01 (port of #42941)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 3941f2ed-0c8d-482c-b028-6b8d89a5a03e

* Experiment: remove PostResponseCodes suppression to test LintDiff on new moveIpConfigurations op

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 3941f2ed-0c8d-482c-b028-6b8d89a5a03e

* Restore PostResponseCodes suppression for moveIpConfigurations

LintDiff confirmed the suppression is required: without it, the new LRO POST operation triggers PostResponseCodes (200 with no schema). Reverts experimental removal.

---------

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

* Adding DisableDefaultServerHeaderInResponse Property under Global Con… (#44796)

* Adding DisableDefaultServerHeaderInResponse Property under Global Configuration

Adding DisableDefaultServerHeaderInResponse Property under Global Configuration

* Add disableDefaultServerHeaderInResponse to TypeSpec source (v2025-09-01)

Add the property to ApplicationGatewayGlobalConfiguration in the Network
TypeSpec source, scoped to the 2025-09-01 version via @added, so the
generated applicationGateway.json matches tsp compile output.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 5fb2028c-25e5-4870-919c-801e61db0d0c

---------

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

* Add ExpressRouteLag resource for Microsoft.Network 2025-09-01 (#44799)

* Add ExpressRouteLag resource for Microsoft.Network 2025-09-01

Introduces the ExpressRouteLag resource type with CRUD operations,
links, members, and LOA generation support.


---------

Co-authored-by: Meera Shrimankar <mshrimankar@microsoft.com>

* Added multi cloud circuit sku (#44798)

Co-authored-by: Meera Shrimankar <mshrimankar@microsoft.com>

* Managed NVA Ipv6 Swagger changes (#44811)

* IPv6 NVA Swagger changes

* Made swagger changes based on the API review board comments

* Adding fix for Spelling error raised by PR bot

* Fixing merge validation errors

* Fix for validation error

* Fix merge validation errors

* Resolved ARM Reviewer's comments

* Added Connection analyzer and its example files (#44839)

* Added Connection analyzer and its example files

* Address review nits: 201 LRO example headers, document result payload,
Regenerate swagger from tsp; add expiryInDays minValue and readOnly id

* Nva migration swagger api changes (#44815)

* Added in Swagger changes for NVA Migration

* Updated to conform to review standards

* Cleared up POST response errors

* Updated to fix Typescript errors and conform the examples to the expected response codes

* Updated to fix generic suppression message

---------

Co-authored-by: Jordan Graves <jordangraves@microsoft.com>

* Add AddressPrefixSet TypeSpec definition for 2025-09-01 (#44737)

* Base commit from target branch

* Add AddressPrefixSet.tsp

* Add AddressPrefixSetCreate.json

* Add AddressPrefixSetDelete.json

* Add AddressPrefixSetGet.json

* Add AddressPrefixSetList.json

* Add AddressPrefixSetCreate.json

* Add AddressPrefixSetDelete.json

* Add AddressPrefixSetGet.json

* Add AddressPrefixSetList.json

* Update main.tsp for AddressPrefixSet

* Update readme.md for AddressPrefixSet

* Update virtualNetwork.json for AddressPrefixSet

* fix: add @minItems(1) to addressPrefixes array

* fix: clean readme.md - remove unrelated changes, keep only AddressPrefixSet suppression

* fix: add minItems:1 to addressPrefixes in virtualNetwork.json

* fix: clean Network/main.tsp - keep only AddressPrefixSet import and v2025_09_01 version

* fix: clean Common/main.tsp - only add v2025_09_01 version

* fix: remove unrelated firstPartyServiceTagId from IpTag in virtualNetwork.json

* fix: add package-2025-09-01 tag to readme with all swagger input-files

* regenerate: applicationGateway.json from tsp compile

* regenerate: azureWebCategory.json from tsp compile

* regenerate: common.json from tsp compile

* regenerate: expressRoute.json from tsp compile

* regenerate: firewall.json from tsp compile

* regenerate: firewallPolicy.json from tsp compile

* regenerate: interconnectGroup.json from tsp compile

* regenerate: loadBalancer.json from tsp compile

* regenerate: networkGateway.json from tsp compile

* regenerate: networkingOperations.json from tsp compile

* regenerate: networkManager.json from tsp compile

* regenerate: networkSecurityPerimeter.json from tsp compile

* regenerate: networkWatcher.json from tsp compile

* regenerate: serviceGateway.json from tsp compile

* regenerate: virtualNetwork.json from tsp compile

* regenerate: virtualNetworkAppliance.json from tsp compile

* regenerate: virtualWan.json from tsp compile

* fix: use release branch readme as base + AddressPrefixSet suppression - remove firstPartyServiceTag

* revert: reset applicationGateway.json to release branch version

* revert: reset azureWebCategory.json to release branch version

* revert: reset common.json to release branch version

* revert: reset expressRoute.json to release branch version

* revert: reset firewall.json to release branch version

* revert: reset firewallPolicy.json to release branch version

* revert: reset interconnectGroup.json to release branch version

* revert: reset loadBalancer.json to release branch version

* revert: reset networkGateway.json to release branch version

* revert: reset networkingOperations.json to release branch version

* revert: reset networkManager.json to release branch version

* revert: reset networkSecurityPerimeter.json to release branch version

* revert: reset networkWatcher.json to release branch version

* revert: reset serviceGateway.json to release branch version

* revert: reset virtualNetworkAppliance.json to release branch version

* revert: reset virtualWan.json to release branch version

* regenerate: virtualNetwork.json from tsp compile (with examples, only AddressPrefixSet changes)

* fix: restore full readme from release branch + AddressPrefixSet suppression

* fix: add ResourceNameRestriction suppression for applicationSecurityGroupName

* fix: use path-level ResourceNameRestriction suppression for both AddressPrefixSet paths

* refactor: use ProxyResource instead of SubResourceModel for AddressPrefixSet

* regenerate virtualNetwork.json with ProxyResource-based AddressPrefixSet

* fix: use previous passing swagger + only change AddressPrefixSet to ProxyResource ref

* regenerate swagger from TypeSpec compile (ProxyResource)

Re-adds AddressPrefixSet import in main.tsp and full regenerated
virtualNetwork.json to fix TypeSpec Validation CI.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 158d4d5e-d3cb-435c-b868-0f75cd8518e4

* fix: add trailing newline to all AddressPrefixSet files (tsp format)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 158d4d5e-d3cb-435c-b868-0f75cd8518e4

* fix: add missing '- code: ProvisioningStateMustBeReadOnly' for expressRoute suppression

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 158d4d5e-d3cb-435c-b868-0f75cd8518e4

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 158d4d5e-d3cb-435c-b868-0f75cd8518e4

* Add Microsoft.Network/FirstPartyServiceTags TypeSpec for 2025-09-01 and update Microsoft.Network/PublicIpAddress and Microsoft.Network/PublicIpPrefix TypeSpec for 2025-09-01 (#44870)

* Port Network 2025-09-01 FirstPartyServiceTags TypeSpec from private PR #28751

Ports the TypeSpec source (Common/main.tsp, Network/main.tsp,
FirstPartyServiceTag.tsp), readme.md tag config, cspell overrides and the
8 example inputs from Azure/azure-rest-api-specs-pr#28751, then regenerates
the swagger for 2025-05-01, 2025-07-01 and 2025-09-01 via tsp compile.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 021fef56-c735-4428-b5bf-4171afabb106

* Regenerate vmssNetwork.json (2018-10-01) for firstPartyServiceTagId on shared IpTag

The Common/main.tsp IpTag model change ripples into the Vmss TypeSpec
project, whose output stable/2018-10-01/vmssNetwork.json must be
regenerated. Fixes TypeSpec Validation (tsv) failure on the Vmss project.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 021fef56-c735-4428-b5bf-4171afabb106

* Replace placeholder suppression reason with real justification for CombineClient

The inconsistent-multiple-service-dependency suppression on CombineClient
previously carried a placeholder reason (temporarily suppressing). Replace
it with a real justification: CombineClient intentionally merges the
Microsoft.Network and Microsoft.Compute (VMSS) services into a single SDK
client surface via autoMergeService, so the multiple-service dependency is
by design. Addresses reviewer cleanup request on PR #44870.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 021fef56-c735-4428-b5bf-4171afabb106

* Document VMSS 2018-10-01 captured-schema exception in Network readme

Add a short note to the Network readme explaining that stable/2018-10-01/
vmssNetwork.json is an intentional, long-standing exception to the
same-version captured-schema rule: VMSS pins the 2018-10-01 api-version but
returns the latest NetworkInterface/PublicIPAddress types, so additive
shared Common changes (e.g. firstPartyServiceTagId) ripple into 2018-10-01
by design and may trip OAD 1041. Includes precedent links (2025-01-01 and
2024-10-01 vmssNetworkInterface.json, PR #42717, and the VMSS network
schema-change report). Addresses reviewer follow-up on PR #44870.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 021fef56-c735-4428-b5bf-4171afabb106

* Revert Network @service title to WebApplicationFirewallManagement

The port had changed the Microsoft.Network @service title to
"NetworkManagementClient", which is identical to the VMSS (Microsoft.Compute)
service title. Because client.tsp merges both services into one Python SDK
namespace, the two ARM common-types "Resource" models collided, causing the
Python SDK validation error: duplicate-client-name "Resource".

Reverting the title to the released value (matches 2025-05-01/2025-07-01)
restores a distinct title from VMSS and fixes the Python check. Regenerated
2025-05/07/09 swagger info.title accordingly. The meaningful-title rename
requested by the reviewer will be handled in a separate PR after reviewer
confirmation. Service description change is retained (approved).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 021fef56-c735-4428-b5bf-4171afabb106

* Fix Python SDK duplicate-client-name: FirstPartyServiceTag extends Common.Resource

FirstPartyServiceTag was the only Network resource declared with the ARM
standard 'is TrackedResource<>' template, which pulls ARM common-types
Resource into Microsoft.Network. Because client.tsp CombineClient merges
Network + Compute/VMSS into the flat azure.mgmt.network Python namespace
(which already surfaces ARM Resource via VMSS), this produced two Resource
models in one namespace -> duplicate-client-name and Python SDK generation
failure. Every other Network resource extends the local Common.Resource
custom resource, which does not surface ARM Resource.

Rewrite FirstPartyServiceTag to extend Common.Resource (matching the
ApplicationGateway convention) with an explicit properties member and the
standard Legacy suppressions. Resource remains regional (location/tags
preserved). Regenerated swagger now references ./common.json#/Common.Resource
instead of ARM TrackedResource. Verified Python TCGC emitter now exits 0.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 021fef56-c735-4428-b5bf-4171afabb106

* Fix LintDiff RequiredPropertiesMissingInResourceModel: inline readOnly id/type on FirstPartyServiceTag

The spectral RequiredPropertiesMissingInResourceModel rule does not traverse
the custom Common.Resource allOf, so id/type must be declared inline on the
resource model (matching the ExpressRouteLag convention). Added inline
@visibility(Lifecycle.Read) id? and type?; regenerated swagger.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 021fef56-c735-4428-b5bf-4171afabb106

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 021fef56-c735-4428-b5bf-4171afabb106

* Add upgradedToV2 to PublicIPAddress and PublicIPPrefix (2025-09-01) (#44807)

* Add upgradedToV2 to PublicIPAddress and PublicIPPrefix (2025-09-01)

Add read-only boolean property upgradedToV2 to PublicIPAddressPropertiesFormat and
PublicIPPrefixPropertiesFormat, gated to API version 2025-09-01. Indicates whether the
SKU has been upgraded from Standard to StandardV2. Updates the StandardV2 SKU Get
examples to demonstrate the property.

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

* Regenerate vmssNetwork.json (VMSS 2018-10-01) after Common changes

The Vmss TypeSpec project pins @useDependency(Common.Versions.v2025_09_01), so its
2018-10-01 output is generated against the latest Common models. Regenerate to include
the upgradedToV2 property, fixing TypeSpec Validation drift. Follows the standard release
workflow.

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

---------

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

* Updated the response code for the Service Gateway API and added a new SKU for the Load Balancer. (#44745)

* Response code update & Added new enum service

* FIx

* Fix RESPONSE_BODY_NOT_IN_EXAMPLE errors in ServiceGateway 2025-09-01 examples

Add `body: {}` to the 200 responses in three example files for ServiceGateway
operations that were changed from async (202/204) to synchronous (200) in PR #44745.

The swagger spec defines an empty object schema for the 200 response, so oav
requires a body field in the example even though the body is empty.

Fixes:
- ServiceGatewayFullUpdateAddressLocationsRequest.json
- ServiceGatewayPartialUpdateAddressLocationsRequest.json
- ServiceGatewayUpdateServicesRequest.json

Co-authored-by: anjbal <137822143+anjbal@users.noreply.github.com>

* fix: resolve network ServiceGateway typespec validation failure

Co-authored-by: anjbal <137822143+anjbal@users.noreply.github.com>

* style: apply required typespec formatting

Co-authored-by: anjbal <137822143+anjbal@users.noreply.github.com>

* network: add status property to ServiceGatewayActionOkResponseBody and regenerate swaggers

* network: fix ServiceGateway example responses from 202/204 to 200 for sync operations

* network: fix ServiceGateway example responses from 202/204 to 200 for sync operations (2025-05-01, 2025-07-01)

* Previous example change

* Examples

* Added explanation

* Response code

* specification/network/resource-manager/Microsoft.Network/Network/Network/ServiceGateway.tsp

* Added @Action

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

* kube selector groups (#44865)

* kube selector groups

* delete fix

* updated reason for the supression

* Removed supression

* Reason for the supression

* Virtual Hub IPv6 and enableOnlyIPv6Peering changes (#44955)

Co-authored-by: Caren Lim <carenlim@microsoft.com>

* [VPN] Add new POST API for VPN Get EffectiveRoutes (#45005)

* [VPN] Add new POST API for VPN Get EffectiveRoutes

* Remove version attribute

---------

Co-authored-by: Akshat Kale <akale@microsoft.com>

* [VPN] Effective Routes API - formatting fix (#45053)

* Add version attribute

* format + recompile

* PR comments

* update post format and recompile

---------

Co-authored-by: Akshat Kale <akale@microsoft.com>

* Address comments on release PR (#45082)

* Fix merge conflicts with main and add LintDiff suppressions for network 2025-09-01 release (#45223)

* Add csharp customizations for Education migration (#44428)

* Enable BotService provisioning emitter (#44380)

* Update tspconfig.yaml

* Update client.tsp

* Update client.tsp

* Update client.tsp

* Update client.tsp

* Update client.tsp

* Update client.tsp (#44633)

* [servicefabricmanagedclusters] Update renaming for csharp (#44632)

* Update client.tsp

* Update tspconfig.yaml

* Update client.tsp

* Enable ServiceFabric provisioning emitter (#44533)

* Update tspconfig.yaml

* Update tspconfig.yaml

* Prepare specs for no-url-suffix lint rule (#43818)

* Prepare specs for no-url-suffix lint rule

Add #suppress directives and @@clientName URL-to-Uri customizations across affected TypeSpec specs in preparation for the no-url-suffix lint rule. Squashed rebase of PR #43818 onto latest main; resolved the liftrmongodb client.tsp conflict by keeping both the Project/Cluster renames from main and the redirectUrl->redirectUri rename.

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

* Remove duplicate csharp-no-url-suffix suppressions

Each flagged property had the identical #suppress line written twice. Collapse the 32 exact-duplicate suppressions (across 16 files) to a single suppression per property.

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

* Remove non-adjacent duplicate csharp-no-url-suffix suppressions

6 properties (botservice x4, cost-management x2) had csharp-no-url-suffix suppressed twice with a pre-existing casing-style suppress between the two, so they were non-adjacent and missed by the first dedup pass. Collapse to a single csharp-no-url-suffix suppression per property.

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

* Move no-url-suffix to client-sdk ruleset: extend it for client-SDK specs, drop suppressions elsewhere

Step 2 of the no-url-suffix rollout. The csharp-no-url-suffix rule now lives in the new client-sdk ruleset (typespec-azure #4541), so: (1) add the client-sdk ruleset to linter.extends in all 349 tspconfigs configured to emit a client SDK, (2) remove the 60 now-dead suppressions from 25 non-client projects, (3) refresh the @4541 lockfile pin to build .1516 which contains the moved rule.

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

* Pin typespec-azure deps to immutable commit URL (fix npm ci EINTEGRITY)

The @4541 pkg.pr.new moving tag repacks with a new hash on each fetch, so npm ci fails with EINTEGRITY (lockfile integrity != freshly downloaded tarball). Pin both @azure-tools/typespec-azure-rulesets and @azure-tools/typespec-client-generator-core to the immutable commit-specific URL @97378df6, which serves a byte-stable tarball. Integrity values are unchanged (they already match the commit artifact).

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

* Restore suppressions for shared sub-models consumed by client-SDK parents; fix cloudhealth tspconfig format

Step 2 removed csharp-no-url-suffix suppressions from sub-projects whose own tspconfig is non-client, but whose models are compiled by a client-SDK parent (applicationinsights, compute/Compute, monitor/Insights, network/Network). With client-sdk added to those parents, the rule fired on the now-unsuppressed *Url properties (50 TSV errors). Restore the 25 suppressions in the 7 shared model files. Also convert cloudhealth linter.extends from inline array to block list (prettier/tsv Format rule).

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

* Bump typespec-azure deps to @4541 build .1525 (includes #4730 override fix)

Repin to the immutable commit URL @30de6998 (build 0.70.0-pr-4541.1525), which includes tadelesh's #4730 @override regression fix. With #4730, the override-parameters-mismatch errors drop to 37 (the genuine 'override param dropped @path' cases across 11 projects); the false-positive regressions are fixed. Demonstrates #4730 reduces but does not fully clear the override errors without spec-side @path additions.

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

* Use released 0.69.2 for tcgc/rulesets/resource-manager (drop pkg.pr.new pin)

Now that @azure-tools/typespec-client-generator-core, typespec-azure-rulesets,
and typespec-azure-resource-manager 0.69.2 are published (with the client-sdk
ruleset and the #4730 override fix), switch off the pkg.pr.new build pins.
Also drop the legacy-peer-deps=true .npmrc workaround since 0.69.2 peers resolve
cleanly.

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

* Keep resource-manager at 0.69.1; suppress 11 url-suffix violations unmasked by 0.69.2

Revert typespec-azure-resource-manager to 0.69.1 (keep tcgc + rulesets at
0.69.2). resource-manager 0.69.2 changes CommonTypes emission (external \
-> inlined definitions), which regenerates swagger for RM projects (e.g.
devcenter, maps) and is unrelated to the url-suffix rule. The rulesets 0.69.2
peer on resource-manager ^0.69.2 is only an npm warning.

Add csharp-no-url-suffix suppressions for 11 properties in cognitiveservices,
policyinsights, and security. These were previously hidden because those
projects had compile-blocking override-parameters-mismatch errors; 0.69.2's
override fix unmasked them.

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

* Add npm override so rulesets 0.69.2 accepts resource-manager 0.69.1

npm ci uses strict peer resolution and errored with ERESOLVE because
typespec-azure-rulesets@0.69.2 has a peer of resource-manager@^0.69.2 while we
deliberately keep resource-manager at 0.69.1 (to avoid CommonTypes swagger
regeneration). A surgical overrides entry satisfies the peer without adding
legacy-peer-deps to .npmrc. The resolved tree is unchanged (rm stays 0.69.1),
so package-lock.json needs no update. Verified
pm ci no longer ERESOLVEs.

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

* Bump typespec-azure-resource-manager to 0.69.2 and regenerate affected swagger

Drop the npm override and bump resource-manager 0.69.1 -> 0.69.2 so rulesets
0.69.2's peer is satisfied directly. rm 0.69.2 includes typespec-azure#4627,
which emits the CustomerManagedKeyEncryption and Encryption common-types inline
instead of as external \s. Regenerated the impacted swagger accordingly:
devcenter DevCenterRP.json (3 API versions) and maps maps-management.json.

This is the alternative to keeping rm at 0.69.1 behind an override; posting it so
we can decide whether to take the rm 0.69.2 bump (with this swagger change) or
revert to the override.

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

* Suppress 5 url-suffix violations in developerhub (surfaced after merge)

The latest main merge brought developerhub changes with authURL/prURL/
workflowRunURL properties. Add csharp-no-url-suffix suppressions so the
client-sdk ruleset passes TSV.

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

* Remove client-sdk ruleset from 7 legacy-emitter data-plane services

These services generate their .NET SDK with the legacy @azure-tools/typespec-csharp
emitter, which pins typespec-azure-rulesets 0.61.0 and therefore lacks the client-sdk
ruleset - causing 'unknown-rule-set: client-sdk' in .NET SDK Validation. Remove
client-sdk from their linter.extends until each migrates to the
@azure-typespec/http-client-csharp emitter (rulesets 0.69.2), at which point it can be
re-enabled per-service.

Services: attestation, confidentialledger (ConfidentialLedger + ConfidentialLedgerIdentity),
containerregistry, loadtestservice/playwright, webpubsub, apicenter.

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

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Razvan Badea <156206747+razvanbadea-msft@users.noreply.github.com>

* Add client.tsp to rename ConfidentialLedger models for .NET SDK (AZC0012/AZC0030) (#44615)

Rename generated model/enum types for the C# SDK only via @clientName so the
Azure.Security.ConfidentialLedger library follows Azure SDK for .NET naming
guidelines, removing the need to suppress analyzers AZC0012 and AZC0030.
Scope is limited to "csharp" so the REST/wire contract and the already
generated JavaScript, Python and Java SDKs are unchanged.

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

* Bump SDK config api-version to 2026-05-01 (#44537)

* Adding new API version 2026-05-01

* Adding changes to API version 2026-05-01 and 2026-05-15-preview

* Format tsp files

* Added rename tag for usageThreshold20250901

* Added rename tag for sizeOld on capacity pool tsp

* Added rename tag for usageThreshold in VolumeProperties

* Remove unintended decorators for usageThreshold in VolumeProperties

* Update tags for updatePrevious in NetappAccount.tsp

* Update tags for sizeOld in PoolPatchProperties

* Adding Deprecation message for subvolumes related models and properties

* Update version in tspconfig.yaml

* Correct versioning issue with NetAppAccountPatchStable

* Update TypeSpec config emitter version (#44649)

* fix: handle renamed tspconfig files in namespace detection (#44619)

* Sync .github/skills directory with azure-sdk-tools for PR 16300 (#44653)

* Update pipeline troubleshooting skill and vally fixtures

* Split pipeline troubleshooting into analysis + fixer skills, added Vally eval suite.

* Fixed project name resolution for untrusted DevOps pipelines. Removed unnecessary evaluation files and fixtures for pipeline analysis and fixing. Updated and added skills files for pipeline analysis and fixing.

* Fixes to PipelineIdentifierHelper Updated skills/tools descriptions. Deleted redundant eval in prompt-to-tool-pipeline.eval.yaml

* Changed skills formatting and updated Vally README to have absolute paths.

* Updated to align with review comments.

* Updated failure patterns to use "az account show"

* Prettier formatting.

---------

Co-authored-by: ReilleyMilne <reilleymilne@gmail.com>
Co-authored-by: ReilleyMilne <91291100+ReilleyMilne@users.noreply.github.com>

* Added presteps support to auto-release template (#44661)

Co-authored-by: Ray Chen <raychen@microsoft.com>

* Sync eng/common directory with azure-sdk-tools for PR 16330 (#44657)

* Convert eval CI glue scripts from .js to .ts (Node type stripping)

Rename the 7 source + 4 test modules under eng/common/scripts/eval to .ts and rewrite relative import specifiers to .ts (Node native type erasure, no build step). Pipeline node invocations and the npm test script gain --experimental-strip-types --disable-warning=ExperimentalWarning so they run on Node 22.6-22.17 (local) and unflagged on 22.18+ (CI). engines bumped to >=22.6. Addresses Mike Harder feedback to prefer .ts with type erasure over .js.

* Reuse azure-rest-api-specs exec primitives in eval git sync

Vendor .github/shared/src/exec.js from azure-rest-api-specs (@ef7dd74) as lib/exec.ts (TS port, erasable syntax) under eng/common so it syncs into the language repos. Rewire sync-eval-git-repo invokeGit onto the async execFile helper (no-shell child_process.execFile, git stderr surfaced only on failure); syncRepo and init-eval-git-fixtures main become async accordingly. README documents the vendored file and provenance. Addresses Mike Harder feedback to reuse the shared exec primitives; see #16296.

* Polish: keep vendored exec.ts faithful to upstream; note shard spawnSync rationale

* Drop --disable-warning=ExperimentalWarning; keep only --experimental-strip-types

---------

Co-authored-by: helen229 <gaoh@microsoft.com>

* Updated to align with review comments. (#44652)

Co-authored-by: ReilleyMilne <reilleymilne@gmail.com>

* Update release pending status and pipeline URL in release plan (#44660)

Update release pending status and pipeline URL in release plan

Missing comma

Apply suggestion from @praveenkuttappan

Add test and resovle review comment

Update eng/common/scripts/Resolve-AutoReleasePackages.ps1

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

* [TSP Migration][monitor] Migrate Monitor Insights Diagnostic Settings, Tenant Action Groups, and VM Insights Onboarding to TypeSpec (#44471)

* TypeSpec migrated from swagger

* suppress warnings

* remove operationid decorators

* remove old swagger

* update readme

* run prettier check

* run prettier check

* update namespace

* update

* update

* update

* update

* Update suppressions.yaml

* update

* mitigate go breaking

* remove unexpected change

* fix js breakings

* Update client.tsp

* update

* Extend JS duplicate-model client customizations to Python (#44554)

Python, like JavaScript, flattens all models into a single module, so the
same cross-namespace model name collisions occur. Apply the existing JS
@@alternateType / @@clientName customizations to the python scope as well:

- Group A (TenantActionGroups vs ActionGroupsApi): 6 identical models merged,
  4 differing models renamed; ReceiverStatus is auto-orphaned.
- Group B (DiagnosticsSettings vs ServiceDiagnosticsSettingsApi): redirect
  MetricSettings/LogSettings to DiagnosticsSettings for python (as JS does)
  instead of the local model, which still collided.

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

* move shared ActionGroup models to Common and rename Diagnostics settings models

* Add java scope to Monitor client customizations for SDK generation

- Add java to the 4 TenantActionGroups model renames (were javascript,python only), fixing duplicate-client-name collisions with ActionGroupsApi in the Java SDK.
- Make the newer 2021-05-01-preview DiagnosticsSettings MetricSettings/LogSettings canonical for java; ServiceDiagnosticsSettingsApi (2016-09-01) redirects to them via @@alternateType, so its own copies are not emitted.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: fd20eebe-bc90-4f75-958d-b69c05dcc624

* Update client.tsp

* Update client.tsp

---------

Co-authored-by: kazrael2119 <98569699+kazrael2119@users.noreply.github.com>
Co-authored-by: ZiWei Chen <v-ziweichen@microsoft.com>
Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Weidong Xu <weidxu@microsoft.com>

* Add Redis provisioning emitter config (#44644)

* Add Redis provisioning emitter config

* Add Redis provisioning RBAC role

* Fix Redis TypeSpec validation formatting

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

* Revert release plan file mode change

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

---------

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

* Rename IpAddressType to ServiceBusIPAddressType for C# clients (#44670)

* Rename IpAddressType to ServiceBusIPAddressType for C# clients

* Rename IpAddressType to ServiceBusIPAddressType for C# clients

* Add OperationalInsights C# provisioning emitter (#44645)

* Add OperationalInsights provisioning emitter

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: e86767a6-c0f8-4720-a7e0-ca89fd0de938

* Preserve OperationalInsights C# property types

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

Copilot-Session: e86767a6-c0f8-4720-a7e0-ca89fd0de938

---------

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

* Add Redis provisioning name constraints (#44671)

* Add Redis provisioning name constraints

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

* Format Redis provisioning constraints

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

---------

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

* Generate SDK pull request for management plane automatically (#44587)

* Generate SDK pull request for management plane automatically

* update autorelease resolve step as authenticated step (#44692)

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

* Storage STG 103/104 Typespec (#44500)

* Paginated File Get Ranges (TypeSpec) (#44194)

* NFS List V2 Files and Directories (TypeSpec) (#44195)

* Photon (TypeSpec) (#44283)

* Photon (TypeSpec)

* edited xml comment

* Removed xml comment

* Chnages for CI

* More CI fixes

* Populated readme

* Changed wording of xml comments

* Changed formatting

* Add Blob Access Tier to Get Blob Response (TypeSpec) (#44364)

* Add Blob Access Tier to Get Blob Response (TypeSpec)

* updated api-version

* fixed tag

* removed extra space

* tsp compile

* MD5/CRC64 Combined Return (TypeSpec Changes) (#44367)

* MD5/CRC64 Combined Return (TypeSpec Changes)

* updated api-version

* tsp compile

* Photon TypeSpec uri fix (#44539)

* addressed comments

* reordered request params

* passed content-type to param in template

---------

Co-authored-by: Nick Liu <nicliu@microsoft.com>
Co-authored-by: vincenttran-msft <101599632+vincenttran-msft@users.noreply.github.com>

* Sync eng/common directory with azure-sdk-tools for PR 16342 (#44697)

* make prefix check optional

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Marcos Salamanca <masalama@microsoft.com>
Co-authored-by: msalaman <Marcossalamanca97@hotmail.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Added new API version 2026-06-02-preview (#44698)

* VoiceLive: C# client naming fixes for 2026-07-15 (#44665)

* VoiceLive: C# client naming fixes via @clientName

Address .NET SDK review comments (wire contract unchanged, csharp scope only): voice 	ype->Kind, parallel_tool_calls->AllowParallelToolCalls, �xpires_at->ExpiresOn.

* VoiceLive: revert voice type->Kind client rename

Keep only parallel_tool_calls->AllowParallelToolCalls and expires_at->ExpiresOn C# renames.

* VoiceLive: use Kind suffix for AzureRealtimeNativeVoice.type (C#)

Not-yet-GA'd property; avoids System.Type confusion per .NET SDK review. Wire field unchanged.

* Skip SDK generation stage when there is no release plan (#44691)

* Skip SDK generation stage when there is no release plan

* Added step to emit auto-release label (#44695)

* Upgrade typespec compiler 1.14.0 and format (#44688)

* Bump actions/checkout from 6 to 7 (#44258)

Bumps [actions/checkout](https://github.com/actions/checkout) from 6 to 7.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v6...v7)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* bump js-yaml to 3.15.0 (#44711)

* Add 'go' to supported languages in client.tsp (#44672)

* [compute/bulkactions] Update namespace and output directory for Python (#44635)

* [compute/bulkactions] Update namespace and output directory for Python SDK

* Update tspconfig.yaml

* Update client.tsp (#44713)

* containerservice/preparedimagespecification: shorten SDK package names for Windows path limit (#44338)

* Shorten preparedimagespecification SDK package names to fix Windows path length

Rename package names from 'preparedimagespecification' to 'preparedimgspec'
across service-dir, .NET namespace, Go/Python/JS package names, and
emitter-output-dirs. Matches the existing Java 'preparedimgspec'
abbreviation and the 'nodecustom' precedent under Microsoft.ContainerService.

Fixes 'Filename too long' failures on Windows CI (git checkout in Java PR,
path-length analyzer in .NET PR) where generated file paths exceeded 260
characters. Longest Java model path drops from ~262 to 239.

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

* Java: group under sdk/containerservice per package layout convention

* Add preparedimgspec words to cspell dictionary

* Revert "Add preparedimgspec words to cspell dictionary"

This reverts commit 9fc673d59a8461d8bb08b26cde01e25b7eb4733b.

* Allow preparedimgspec compound words in containerservice cspell dictionary

* add client.tsp to shorten some java name

* add client.tsp to shorten some java name

* rerun ci

* fix(preparedimgspec): match approved Java namespace/package-dir

Align Java tspconfig with namespace approval in Azure/azure-sdk#10095:
- namespace: com.azure.resourcemanager.containerservicepreparedimgspec
- package-dir: azure-resourcemanager-containerservicepreparedimgspec

Addresses ArthurMa1978 review feedback on PR #44338.

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

---------

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

* [confluent] Use exact() for python enum client names of ConnectorClass (#44719)

* [confluent] Use exact() for python enum client names of ConnectorClass

Replace the plain @clientName overrides for ConnectorClass.AZURECOSMOSV2SINK
and AZURECOSMOSV2SOURCE with exact() so the Python emitter preserves the enum
keys exactly without applying its usual casing normalization, keeping the
generated enum keys as before.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 0c3488aa-fe5b-4316-99d0-e75fde154caa

* Update client.tsp

---------

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

* Fix C# failover property naming in client.tsp (#44722)

* Fix C# failover property naming in client.tsp

* updats

* Api version updates (#44725)

* Api version updates

* Api version updates

* added instructions about ProvisioningStateMustBeReadOnly (#44724)

* Upgrade typespec libs to 1.14 (#44707)

* [Microsoft.Mission] Rename SDK packages VirtualEnclaves -> Enclave (tspconfig.yaml) (#44659)

* [Microsoft.Mission] Rename SDK packages VirtualEnclaves -> Enclave (tspconfig.yaml)

Renames per-language SDK package/namespace identifiers from VirtualEnclaves/virtualenclaves to Enclave/enclave (product renamed to "Azure Enclave"). Config-only change: REST API surface, the virtualEnclaves ARM resource type, and all .tsp models/client names are unchanged.

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

* [Microsoft.Mission] Java service-name: Enclave -> Azure Enclave (per review)

Addresses review feedback that the Java service-name should be the full product name "Azure Enclave" rather than "Enclave".

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

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com>

* [Azure Search] Resource Provider 2026-09-01-Preview (#44173)

* RP 2026-09-01-Preview: Spec baseline

* Change offerings route and name for ARM compliance and add default re… (#44591)

* Change offerings route and name for ARM compliance and add default region to the API response.

* Fix LintDiff OperationIdNounVerb and Avocado MISSING_APIS_IN_DEFAULT_TAG

Rename Offerings.fetchOfferings to fetch (operationId Offerings_Fetch) to
satisfy the Noun_Verb convention while keeping the fetchOfferings URL action.
Suppress Swagger Avocado MISSING_APIS_IN_DEFAULT_TAG for 2026-03-01-preview,
whose /offerings path was intentionally removed from the default tag.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: c484df78-3193-4d52-9c5e-06e2adeb4350

---------

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

* Leonardogal/rp 2026 09 01 preview/deterministic names (#44623)

* Adding example

* Adding enum to SearchService properties

* Linking example

* Ran prettier

* Fix tsp file

* Allow nullable

* Add example for Deterministic Names

---------

Co-authored-by: Leonardo Galindo Sanchez <leonardogal@microsoft.com>

* Azure Search / 2026-09-01-preview / Update mutability for autoGeneratedDomainNameLabelScope (#44693)

* Update mutability

* Update suppression message

---------

Co-authored-by: Leonardo Galindo Sanchez <leonardogal@microsoft.com>

* Remove Swagger Avocado suppression

* remove empty line

* Update FIXME suppression description as a concise justifaction

* Update FIXME comment

* Fix spellcheck error

---------

Co-authored-by: Chang Lu <58885471+Draconicida@users.noreply.github.com>
Co-authored-by: Chang Lu <luchang@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: GSLeonardo <61255738+GSLeonardo@users.noreply.github.com>
Co-authored-by: Leonardo Galindo Sanchez <leonardogal@microsoft.com>

* Move Vally eval suite to repo-root azsdk-evals (#44729)

Co-authored-by: helen229 <gaoh@microsoft.com>

* fix: Go and Python namespace extraction/validation (#44699) (#44730)

* Bump js-yaml from 4.1.0 to 4.3.0 (#44741)

* Expose Batch data-plane LRO option models as public in Python client (#44738)

* Add 2026-03-02/04-02/05-02-preview API versions to preparedimagespecification (#43870)

* Add 2026-03-02/04-02/05-02-preview API versions to preparedimagespecification TypeSpec

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

* Add source examples for new preparedimagespecification preview versions

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

* Regenerate swagger for new preparedimagespecification preview versions

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

* Fix prepared image spec readme formatting

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

* Suppress prepared image TypeSpec requirement false positives

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

---------

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

* Add TrustedHostSubscription APIs in new 2026-07-30 stable version for… (#44710)

* Add TrustedHostSubscription APIs in new 2026-07-30 stable version for Microsoft.ComputeLimit

Introduces trustedHostSubscriptions proxy resource (PUT/DELETE/list) gated to the new 2026-07-30 API version via @added. Existing stable versions are unchanged.

* Fix TrustedHostSubscription TypeSpec formatting

* Add ComputeLimit 2026-07-30 AutoRest tag

* Rename ComputeLimit API version to 2026-07-31

* Fix TrustedHostSubscription CI: add operations list entries and align common-types to v5

- Add trustedHostSubscriptions read/write/delete to Operations_List example (per reviewer)
- Change 2026-07-31 armCommonTypesVersion from v6 to v5 to match prior versions and clear cross-version breaking changes

* Add instance GET to TrustedHostSubscription and align list with sibling resources

- Add get (ArmResourceRead) required by ARM (RPC-Get-V1-04); this also resolves NestedResourcesMustHaveListOperation, which the linter reported because the resource lacked an instance GET to anchor it
- Switch listByParent (ArmResourceListByParent) to list (ArmResourceListAtScope) to match the 5 sibling resources under SubscriptionLocationResource
- Add TrustedHostSubscriptions_Get example and update list example operationId

---------

Co-authored-by: Xiaodi Lu (SHE/HER) <xiaodilu@microsoft.com>

* Refactor(healthbot): migrate to unified folder structure (#44385)

* refactor folder healthbot

* update

* Refactor(billingbenefits): migrate to unified folder structure (#44412)

* update

* update

* update

* update (#44449)

* Refactor(connectedvmware): migrate to unified folder structure (#44453)

* update

* update

* update

* update (#44470)

* Refactor(ews): migrate to unified folder structure (#44520)

* update

* update

* update (#44534)

* Refactor hybridkubernetes folder structure to comply with Azure Guidelines (#44530)

* Add python client name for Microsoft.Mission (#44756)

* Refactor storagemover folder structure to comply with Azure Guidelines (#44494)

* Refactor(liftrqumulo): migrate to unified folder structure (#44491)

* Refactor liftrqumulo folder structure to comply with Azure Guidelines

* fix ci error

* Refactor liftrhyperexecute folder structure to comply with Azure Guidelines (#44488)

* Refactor(oracle): migrate to unified folder structure (#44429)

* update

* update

* update

* Merge branch 'refactor-folder-oracle' of https://github.com/v-jiaodi/azure-rest-api-specs into refactor-folder-oracle

* update

* update (#44487)

Co-authored-by: ChenxiJiang333 <119990644+ChenxiJiang333@users.noreply.github.com>

* Refactor(paloaltonetworks): migrate to unified folder structure (#44518)

* update

* update

* Refactor(iotoperations): migrate to unified folder structure (#44531)

* Refactor iotoperations folder structure to comply with Azure Guidelines

* Update

* Update path in openapi-script.sh

* Refactor(azuredependencymap): migrate to unified folder structure (#44348)

* Refactor azuredependencymap folder structure to comply with Azure Guidelines

* Remove duplicate openapi-type and openapi-subtype

---------

Co-authored-by: ChenxiJiang333 <119990644+ChenxiJiang333@users.noreply.github.com>

* update (#44411)

* Refactor confluent folder structure to comply with Azure Guidelines (#44493)

* Move lease.yaml path (#44712)

* Move lease.yaml path (#44761)

* Authenticate to python DevOps feed (#44767)

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

* Removed NFSv2 from STG103/104 TypeSpec & Swagger (#44742)

* Removed NFSv2 from STG103/104

* reverted swagger changes

* Rename resourcePercentage, adjust progress range (#44568)

* Rename resourcePercentage, adjust progress range

* Regenerate openapi.json for 2026-07-01

* Merging Foundry feature branch for the 6/30 release. (#44285)

* Add threshold field to EvaluatorMetric model (#42167)

* Add threshold field to EvaluatorMetric model

Add optional float32 threshold property to EvaluatorMetric TypeSpec model.
This enables evaluator authors to specify a default pass/fail threshold
per metric, used instead of computing from min/max midpoint.

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

* Simplify evaluator threshold description

---------

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

* Remove operations related to Code Agent from v1, as they are not ready for PuPr (#42184)

* Move patch_agent_object from root Agnets to Beta Agents subclient (#42194)

* Change skills package format from gzip to zip (#42156)

* Remove startPendingUpload and getCredentials from Evaluators in v1 (#42237)

* Remove startPendingUpload and getCredentials from Evaluators in v1

Add @removed(Versions.v1) to startPendingUpload and getCredentials
operations in the Evaluators interface. These upload-related APIs
are being removed from the v1 GA surface.

- Added using TypeSpec.Versioning to routes.tsp
- Regenerated openapi3/v1 spec (195 lines removed)

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

* Remove startPendingUpload and getCredentials from relocate-beta-operations

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

---------

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

* Make AgentSessionFiles.uploadSessionFile internal for Python

* Remove blueprints (#42263)

* Expect upload session file returned 201 (#42329)

* merge session:logstream after functional confirmation

* Revert or this become a breaking change (#42407)

* Rename listSessionFiles to getSessionFiles (#42417)

* rename patc agent func for python only (#42406)

* unremove status from AgentVersionsObject (#42425)

* Change status to optional in agent model (#42436)

* rename skill and toolbox name param (#42421)

* rename skill and toolbox name param

* update

* [Foundry] TelemetryConfig and TelemetryEndpoint for HostedAgents (#41845)

* feat: Add TelemetryConfig and TelemetryEndpoint models to HostedAgentDefinition (#40784)

Cherry-picked from feature/foundry-staging (c5d69eb7b1).
OpenAPI will be regenerated after all telemetry changes are applied.

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

* Hosted Agents: Exclude telemetry types from v1 using @removed(Versions.v1) (#41361)

Cherry-picked from feature/foundry-staging (a3325b9ce0).
Added @removed(Versions.v1) to all telemetry models/unions and telemetry_config property.

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

* Regenerate OpenAPI JSON via npx tsp compile .

Telemetry types correctly excluded from v1, present in virtual-public-preview.

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

---------

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

* Add new paths to Agents. (#42186)

* Add new paths to Agents.

* Renaming

* Fix import

* Hide feature-foundry methods

* Fix skills

* Fix agent patching

* Fix agent patching

* Adopt changes from new openAI specs

* Fix session file operations: rename session_id to agent_session_id, align modified_time encoding (#42490)

- Rename session_id to agent_session_id in all 4 session file operations
  (upload, download, list, delete) for consistency with the rest of the
  agent session API surface
- Change modified_time encoding from rfc3339 to unixTimestamp (int64) to
  be consistent with created_at, last_accessed_at, and expires_at in
  AgentSessionResource

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

* feat(agents): restore x-agent-session-id response header on proxy endpoints (#42491)

Add x-agent-session-id response header to:
- Invocation protocol: GET and Cancel endpoints (POST already had it)
- Responses protocol: create, createStream, get, getStream, delete,
  cancel, and listInputItems

Also rename sessionId -> agentSessionId for consistency.

For invocations (hosted-only endpoints), the header is required.
For responses (serves both hosted and non-hosted), the header is optional.

listResponses and compactResponseConversation are not session-scoped,
so they do not include this header.

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

* Remove isolation key fields from HeaderIsolationKeySource (#42522)

Removed user and chat isolation key definitions from HeaderIsolationKeySource model.

* Add read-only content_hash to hosted agent CodeConfiguration (#42575)

Adds a content_hash property to CodeConfiguration (used inside
HostedAgentDefinition.code_configuration) marked with
@visibility(Lifecycle.Read). The service populates this value from
the x-ms-code-zip-sha256 request header; clients receive it in
responses but cannot set it via request payloads.

- src/agents/models.tsp: add read-only content_hash property
- openapi3/v1 and openapi3/virtual-public-preview: add readOnly
  content_hash to CodeConfiguration schema
- examples/2025-11-15-preview: include content_hash in response
  examples for Create/CreateVersion/Update AgentFromCode

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

* Add Operation-Id header support for idempotent job creation (#42573)

Add optional Operation-Id request header to postJob and postJobPreview
templates for idempotent retry support per foundrysdk_specs PR #107.
Remove accidental foundry-data-generation-jobs.tsp sample file.

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

* Add FabricIQ Preview tool to type spec (#42320)

* Add FabricIQ Preview tool to type spec

* syntax

* type spec update

* Rename job status to 'cancelled' (#42637)

* Wire servicepatterns.tsp into sdk-service-agents-contracts profile (#42673)

The sdk-service-agents-contracts SDK profile was missing the wiring for
the top-level servicepatterns.tsp file:

- main.tsp did not import ../servicepatterns.tsp
- tspconfig.yaml had no @azure-tools/typespec-client-generator-cli
  additionalDirectories block, so tsp-client never synced
  servicepatterns.tsp (or any sibling directories) to downstream SDK
  consumers.

This forced downstream consumers to manually fetch servicepatterns.tsp
at the pinned commit and inject the import into the synced main.tsp.
Adding the import plus additionalDirectories list (modeled on
sdk-projects-agents/tspconfig.yaml) retires that workaround.

Also adds an explicit import "../servicepatterns.tsp" to four sibling
routes.tsp files (agents-containers, memory-stores, skills, toolboxes)
that use servicepatterns symbols (FoundryDataPlaneOperation,
AgentDefinitionOptInKeys) but only resolved them today via transitive
load order.

No model or operation surface changes.

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

* Update openapi3 files

* Adding ToolboxSearchPreviewTool (#42740)

* adding ToolboxSearchPreviewTool

* Adding compiled JSON files

* Adaptive Evals: add EvaluatorGenerationJob LRO, JobSource (Prompt/Dataset/Traces), and RubricsEvaluatorDefinition (#42264)

* adapt /feature/foundry with v2 folder structure

* move generated openapi3 folder into Foundry data plane folder

* git add tspconfig.yaml

* introduce src folder

* update additionalDirectories per 39560

* Update specification/ai-foundry/data-plane/Foundry/client.csharp.tsp

Co-authored-by: Jose Alvarez <jpalvarezl@users.noreply.github.com>

* updates

* fixes

* more updates

* Extracting Namespace definition to importable file under `common` (#39644)

* Trying out namespace extraction to its own file

* File rename

* update generated specs

* Removed api version pinning for Java code gen

* [Foundry branch-to-branch] client.tsp updates for new ingestion .NET support (#39696)

* .net client.tsp support for new spec structure

* tsp format

* (minor) comment cleanup

* recompile to reflect small non-client.tsp changes

* client.tsp workaround for itemresource

* port cspell updates with path snap

* comprehensive cspell update

* removal of legacy 'readonly' folder

* introduce interim suppression guidance

* Revert "Removed api version pinning for Java code gen"

This reverts commit 7d98e6e72f82ba744b04670d16ea2366b528e3f3.

* Make fixes for evaluators and generate code (#39720)

* [Foundry] Moving updates from old branch. (#39792)

* [Foundry] Moving updates from old branch.

* cleanup

* cspell

* cspell

* cspell

* cspell

* Refreshing spec + cleanup,

* Minor corrections to tsp-config and forcing emission of IncludeEnum (#39802)

* Use "Tool" or "PreviewTool" as a suffix for Azure Tools (#39815)

* Update OpenAPI3.0 files

* Rename MemorySearchTool to MemorySearchPreviewTool

* Updating item type for the memory store search  parameters. (#39878)

* Fix input item type for Update Memory operation (#39888)

* Update allowed types for TextResponseFormatJsonSchema (#39884)

* [Agents-V2] Add tool_choice_mode for prompt agents and Resolve created_by field conflicts in ItemResources (#39882)

* [Agents-V2] Add tool_choice_mode for prompt agnts and Resolve created_by field conflicts in ItemResources

* Add versing to deprecate old fields

* PR feedack

* review comments

* Fix comments

* Fix the evaluator creation time type. (#39916)

* Fix the evaluator creation time type.

* Fix

* Making `CodeInterpreterTool`'s `container` property optional. (#39927)

* update (#39932)

* Suppressing emission for duplicate types exposed by Stainless SDK (#39906)

* Supressing unnecessary types

* Added more supressions

* Removing unnecessary renames

* Revert "Removing unnecessary renames"

This reverts commit fab93d6e619d41a6896445eb404602c6e079631f.

* Rename OpenAI namespace fo fix xref in the generated code. (#39938)

* [Foundry branch-to-branch] 'v1' versioning w/preview designations (#39854)

* initial and incomplete: draft 'v1' versioning updates

* adjust openai-based operation pattern

* minor: adjust suppressions and superficial folder structure for Agents+OpenAI ops

* refresh with most (not yet all) removed(v1) excised

* include finetuning, insights in v1

* remove in-situ _preview qualifiers from agents and introduce OAS extension-based tracking

* supply deprecated pre-GA memorysearchtool copy

* revert overapplied blanket preview treatment of openai-evals

* restore /evaluations to PuPr pseudo-version; make openai-eval traces source preview

* Adjusting broken import from responses and converstaion folder rename

* use Record<unknown> for OpenAPI tool 'spec'

* Update OpenAPI files

* Replace 'unknown' with 'Record<unknown>' (#39992)

* Rename folder /src/finetuning to /src/openai-finetuning (#40041)

And update its route to /openai/v1/fine_tuning (added /v1 and fixed to use underscore instead of dash).

Now all OpenAI routes are defined by TypeSpec files in folders that start with "openai-":
openai-conversations
openai-evaluations
openai-finetuning
openai-responses

* Add Synthetic data generation eval models for public preview (#40003)

* Add Synthetic data generation eval models for public preview

* comment

* fix

* fix: lingering and mismatched memory_search_preview_call

* remove conditional memory stores header use from agents operations

* remove agent preview header from delete ops

* remove duplicate discriminator `kind` on parent `AgentDefinition` (#40063)

* remove duplicate discriminator

* update openapi

* Added missing @list for paged op (#40057)

* Added missing @list for paged op

* Removing OpenAI.ToolChoiceParam from code gen tree

* Forcing emission of missed enum

* Removed duplicate line

* Removing rename for inexistent class

* Forcing emission of FoundryPreviewOptInKeys for Java

* Cleanup client.tsp used by Python and JS emitters (#40090)

There is no functional change associated with this PR, just cleanup.

Remove anything related to C# or Java, as those emitters do not use this client.tsp file.

Also move some lines around for better grouping under "sub-client" section.

Tested by re-emitting the Python SDK and seeing that there are no changes.

* Schedule parameter rename (#40113)

* Restore input variable name "schedule" (instead of "resource") in emitted Python/JS Schedules operations (#40094)

* add operation for compact

* post-merge spec compile

* [Foundry branch-to-branch] Add a service contract library target to facilitate ingestion (#40065)

* service contract target for lib generation

* refactor imports to facilitate compatible view ingestion

* revert branch-local package.json changes (development only)

* .net openai: use client emitter view

* .net client sdk only: adjust naming for types

* sequence_number in parent ResponseStreamEvent

* trial: required sequence_number on parent for easier emission

* access/usage for '1' suffixes

* updates for customtoolcalloutput to appear

* post-merge spec compile

* Updates to opt-in headers. Extend OpenAI.OutputItem for Azure defined Responses models.  (#40114)

* Make sure opt-in flag values can be any string, for extensibility purposes (while still documenting the current supported value) (#40175)

* Do no emit streamAgentContainerLogs operation for Python and JS

* Cleanup in client.tsp

* Build fix + namespace + object type enum. (#40184)

* Adding object type union + fixing compilation error.

* updating target namespace.

* rest of the unions.

* More cleanup in Python/JS client.tsp. Do not emit AgentReference

* Restoring original way of defining opt-in flags (#40214)

* [Agents-V2] Minor updates for service contracts

* Fix typo

* Update client.tsp to not include main.tsp

* Remove evaluations from client.tsp

* Minor update to client.tsp

* Create Beta sub-clients for emitted Python and JS SDKs (#40254)

* service contract: make conversation message id, status optional for reuse

* Fix typo and minor cleanup in client.tsp

* [Agents-V2] Minor updates to make models more extensible (#40269)

* Make Id in OutputItem mandatory

* Make it optional

* Make ID mandatory again

* Make Id optional again

* Move Container Agent Operations to a separate routes.tsp file, excluded from client*.tsp used by SDK emitters. (#40259)

* sdk-projects-openai-only: client.tsp refresh (+format folder)

* Save copy of Foundry Features flag summary on preview operations

* [Agents-V2] Update OutputItemRemoteToolCall model to include the full payload (#40281)

* Fix OutputItemRemoteToolCall schema

* Add OutputItemRemoteToolCallOutput

* Fix Remote tool output item type

* Fix typo

* Remove args from remote tool call output

* Remove language specification from client names (#40264)

* Remove Python client name mappings for containers (#40298)

Removed client name mapping for AgentContainerObject and AgentContainerOperationObject in Python.

* Fix opt-in preview flags (Part 1) (#40308)

* no function change: tsp format, re-emit .json/.yaml

* Fix RemoteToolArgument scheme

* update OpenAPI3 files

* Fix opt-in preview flags (Part 2) (#40315)

* [Agents-V2 Fix RemoteToolArgument schema

* Allow renaming an SDK property on the Schedules createOrUpdate operations

* Use alias isntead of Model for Schedules createOrUpdate parameters, so it does not get emitted as a class

* Fix the schedules name (#40097)

* Fix the schedules name

* Fix

* Fix renamings

* Rollback

---------

Co-authored-by: Nikolay Rovinskiy <nirovins@microsoft.com>

* Use "word1-word2" format everywhere in folder names (and one file name) (#40379)

* Remove the experimental header from evaluation rules. (#40383)

Co-authored-by: Nikolay Rovinskiy <nirovins@microsoft.com>

* Make HumanEvaluationRuleAction  -> HumanEvaluationPreviewRuleAction (#40413)

* Make HumanEvaluationRuleAction  -> HumanEvaluationPreviewRuleAction

* Add optional headers

* Add csv file source. (#40460)

* Update OpenAPI3 files, following `npx tsp compile .`

* Remove "humanEvaluation" as type discriminator from v1. Python/JS emitters use more unique name for OpenAI "Error" class. (#40495)

* Update "Foundry-Features" HTTP request header report (#40502)

* Additional updates to foundry-features-flag-summary.md

* Removed OpenAI prefix for Evals (#40484)

* Opt-in flag only required for createOrUpdate in Evaluation Rules (#40513)

* error rename (#40531)

* Do not emit Agent Create/Update operations for JS and Python (#40539)

* Fix Python emitted enum values (#40576)

* Temporary local fix for "type" discriminator in OpenAI's WebSearchApproximateLocation (#40594)

* Add tool call item models for grounding tools (Foundry v2) (#40491)

* Add …
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-Suppression ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review Network resource-manager SuppressionReviewRequired TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants