[Insights] Using SDK 20.1-preview with some fixes. Fixing reported issues with the Diagnostic Settings cmdlets #6998

[markcowl]

Description

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate change log has been updated
• 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:
  • the changes have gone through a cmdlet design review
  • the cmdlet markdown files were generated using the platyPS module

[maddieclayton]

Needs an issue filed against Insights

[scottpazelt]

I downloaded the latest 5.1.1 version of azurerm.insights from PSGallery and I'm still receiving the error below.

Get-AzureRmDiagnosticSetting : Operation returned an invalid status code 'NotFound'
At line:1 char:1

• Get-AzureRmDiagnosticSetting -ResourceId "/subscriptions/f3816459-420 ...

•   + CategoryInfo          : CloseError: (:) [Get-AzureRmDiagnosticSetting], ErrorResponseException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Insights.Diagnostics.GetAzureRmDiagnosticSettingCommand
  

[acroftslalom]

@scottpazelt It looks like the v.5.1.1 that is "released to customers" is still old; you can compare the cmdlet bits to the commits for this change and see that it's still using old code/referenced libraries.

I believe this gets officially released 8/28:

https://github.com/Azure/azure-powershell/milestone/54

It looks like it's available in CloudShell today however.

[acroftslalom]

FYI I was able to go to:

https://shell.azure.com

And install the module "AzureRM.NetCore" (not regular AzureRM, it does not work in Linux), and successfully run the "Set-AzureRmDiagnosticSetting" command that was failing.

[scottpazelt]

Thanks @acroftslalom