AddAzureRMLogProfile - Angshuman patch 2

[angshumannayak]

Description

---

This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

• I have read the contribution guidelines.
• If changes were made to any cmdlet, the XML help was regenerated using the platyPSHelp module.
• If any large changes are made to a service, they are reflected in the respective change log.

General Guidelines

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
• The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

• Pull request includes test coverage for the included changes.
• PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

• New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
• Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

• Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
• Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
• Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

[msftclas]

@angshumannayak,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

[azuresdkci]

Can one of the admins verify this patch?

[cormacpayne]

@azuresdkci add to whitelist

[cormacpayne]

@angshumannayak a couple comments, otherwise LGTM

[cormacpayne]

@angshumannayak please remove this extra ```yaml block. It will affect how platyPS generates the MAML from this markdown. You can keep the command you have in the block, but the ```yaml text string (and closing ```) will need to be removed.

[cormacpayne]

@angshumannayak same comment

[angshumannayak]

@cormacpayne if I have removed the yaml from around the block, but if I remove the ``` then command doesn't get into a block. Also I haven't added these blocks, these were present in the original version. I am just adding content to them as it's mostly empty.

[cormacpayne]

@angshumannayak if the yaml block you added is not removed, then platyPS will throw an error when it tries to convert this markdown file in MAML, which affects the resulting help the user sees when Get-Help is ran. The content you have added can remain, it just cannot exist within a yaml block.

[markcowl]

@azuresdkci add to whitelist

[angshumannayak]

Removed the ```yaml as suggested by cormacpayne