Enable ARM to the Private Link connection Cmdlets

[Vishakha-Git]

Description

Enabling Microsoft.Authorization/resourceManagementPrivateLinks owned by the Azure Resource Manager team to the Private Link Common Cmdlets

Follow-up for Onboarding PR #15858

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• [ X] The title of the PR is clear and informative
• [ x] The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• [ x] The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • {Please put the link here}
  • the markdown help files have been regenerated using the commands listed here

[BethanyZhou]

So the cmdlet works even swagger didn't contain the API? @Vishakha-Git

[BethanyZhou]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Vishakha-Git]

So the cmdlet works even swagger didn't contain the API? @Vishakha-Git

So the cmdlet works even swagger didn't contain the API? @Vishakha-Git

Yes they worked

[Vishakha-Git]

So the cmdlet works even swagger didn't contain the API? @Vishakha-Git

So the cmdlet works even swagger didn't contain the API? @Vishakha-Git

Yes they worked

[Vishakha-Git]

So the cmdlet works even swagger didn't contain the API? @Vishakha-Git

So the cmdlet works even swagger didn't contain the API? @Vishakha-Git

Yes they worked

Any suggestion @BethanyZhou not sure why the test are failing on Windows and MacOS. Also from other PRs enabling providerConfig for private links haven't checked-in any testcase. RegisterConfiguration;

Should I remove the testcases in this PR?

[BethanyZhou]

The failure in windows is thrown by Batch Tests and others are caused by timeout @VeryEarly , could you have a look?
[xUnit.net 00:00:03.78] Microsoft.Azure.Commands.Batch.Test.ScenarioTests.BatchAccountTests.TestGetBatchSupportedImages [FAIL]

@Vishakha-Git ,our test framework does not support testing data-plane. if your feature is in data-plane, please mark it as Category.LiveOnly. If not, I think it's great to have a test.

[Vishakha-Git]

The failure in windows is thrown by Batch Tests and others are caused by timeout @VeryEarly , could you have a look? [xUnit.net 00:00:03.78] Microsoft.Azure.Commands.Batch.Test.ScenarioTests.BatchAccountTests.TestGetBatchSupportedImages [FAIL]

@Vishakha-Git ,our test framework does not support testing data-plane. if your feature is in data-plane, please mark it as Category.LiveOnly. If not, I think it's great to have a test.

Got it Thanks.

[Vishakha-Git]

Are we waiting for a fix for the Batch Test that is timing out?

[VeryEarly]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[VeryEarly]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).