Skip to content

Add support for software categorization, vulnerabilities and machine pending updates | Microsoft.OffAzure RP#1

Open
hsurana06 wants to merge 3 commits intosantoshatmicrosoft:AddArcScopeSupportToServerSitesAndSqlSitesfrom
hsurana06:AddSupportForSecurityInsightsSoftwareClassificationToSI
Open

Add support for software categorization, vulnerabilities and machine pending updates | Microsoft.OffAzure RP#1
hsurana06 wants to merge 3 commits intosantoshatmicrosoft:AddArcScopeSupportToServerSitesAndSqlSitesfrom
hsurana06:AddSupportForSecurityInsightsSoftwareClassificationToSI

Conversation

@hsurana06
Copy link

@hsurana06 hsurana06 commented May 14, 2025

ARM (Control Plane) API Specification Update Pull Request

Added new APIs for Microsoft.OffAzure to support software categorization, vulnerabilities and machine vulnerabilities, pending updates |

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.

spec_pr_review_workflow_diagram

Purpose of this PR

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

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

Due diligence checklist

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

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

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.

@hsurana06
Copy link
Author

/azp run

skywing918 pushed a commit that referenced this pull request Jun 12, 2025
…uestionAnswering.Authoring spec (Azure#33855)

* Add Language.QuestionAnswering spec

* Add question answering authoring typespec

* run prettier + fix spelling

* add tsv validation fixes

* remove unused common.json specs + remove csharp emitter since its not used

* more changes for lint and model validation

* revert defining auth models

* add pattern for projectName path param

* ProjectMetadata.projectname change visibility to lifecycle read

* address review comments #1

* address review comments #2

* revert change

* more fixes

* minor fixes

* fix examples

* remove FIXME comments

* add custom patch op defintion

* minor fix for custom patch operation

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant