Chris Stackhouse

@Kencdk - Please fix the checks, set your PR to Open, and apply the WaitForARMFeedback label if/when you are ready for ARM review. If you no longer need this PR,...

@pranavi-dandu - Please fix the checks, set your PR to Open, and apply the WaitForARMFeedback label if/when you are ready for ARM review. If you no longer need this PR,...

@yashjain4 - Please fix the checks, set your PR to Open, and apply the WaitForARMFeedback label if/when you are ready for ARM review. If you no longer need this PR,...

@malincrist - I added a couple of comments, plus there are a couple of questions/comments remaining from @visingla-ms that you haven't responded to. Note, this PR was not on ARM...

@IndraneelPal - Your PR isn’t correctly labelled because you haven’t filled out the submission form. This is critical for subsequent handling of your PR.

New API version with no API changes, so no ARM feedback needed.

@utsrkr - I changed the label to get this PR off our radar until breaking change review is complete. When you are ready for ARM review, just remove the ARMChangesRequested...

> "additionalProperties": { ARM recommends against the use of the additionalProperties/empty/unschematized object pattern. ARM favors stronger typing wherever possible because it allows all consumers of your API to reason about...

> "additionalProperties": { It looks like I misread this property as being added to an existing resource type, but I see it is only in the request body of the...

@stuti-1807 - Thank-you for updating the PR format: much appreciated. It looks like your PR is getting flagged for breaking change review due to making some properties required that were...