Add .NET emitter config and trigger SDK generation for ResourceConnector TypeSpec

[Copilot]

ARM (Control Plane) API Specification Update Pull Request

Tip

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

PR review workflow diagram

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

Purpose of this PR

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

• New resource provider.
• New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• Update existing version to fix OpenAPI spec quality issues in S360.
• Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• Other, please clarify:
  • SDK generation configuration update and pipeline execution for ResourceConnector TypeSpec project (API version 2025-03-01-preview)

Summary

SDK generation for ResourceConnector TypeSpec project per issue request. Added missing .NET emitter configuration to tspconfig.yaml and triggered SDK generation pipelines for all five languages.

Changes

• Configuration: Added @azure-typespec/http-client-csharp-mgmt emitter block to tspconfig.yaml with namespace Azure.ResourceManager.ResourceConnector

SDK Generation Results

Language	Status	SDK Pull Request	Pipeline
Python	✅	azure-sdk-for-python#44142	Build 5601535
JavaScript	✅	azure-sdk-for-js#36720	Build 5601551
Go	⚠️	azure-sdk-for-go#25652	Build 5601545
Java	✅	azure-sdk-for-java#47353	Build 5601547
.NET	❌	N/A	Build 5601546 - Failed

All SDK details and PRs linked to Release Plan 2015 / Work Item 29473.

.NET pipeline failure requires investigation. Review failed build logs for root cause.

Due diligence checklist

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

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

Additional information

Viewing API changes

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

Suppressing failures

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

Getting help

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

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[TypeSpec] Generate SDK for TypeSpec project specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/ResourceConnector</issue_title>
<issue_description>## SDK generate request for TypeSpec project specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/ResourceConnector

Request to generate SDK by Copilot. Do not release SDK
SDK will be released later by service owner.

Release Plan: 2015
TypeSpec project path: specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/ResourceConnector
API spec pull request link: #38905
SDK release type: Beta
API spec version: 2025-03-01-preview
Spec Type: TypeSpec
Language: Python,JavaScript,.NET,Go,Java
Release plan work item ID: 29473

Contacts:
markdrobnak

Comments:
Generate SDK using Github copilot

Generate SDK for the TypeSpec project and update the generated SDK details in the release plan using release plan work item. Generate a summary and update it back in the linked GitHub issue once SDK pull requests are generated.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [TypeSpec] Generate SDK for TypeSpec project specification/resourceconnector/resource-manager/Microsoft.ResourceConnector/ResourceConnector #38937

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[github-actions]

Next Steps to Merge

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

Comment generated by summarize-checks workflow run.