✅ Validation status: passed

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@naminakao - I am just wondering if the parameter shows up in the code though. If you run PlatyPS do you see the parameter in output? Look at this article: https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/repo_docs/NEW_CMDLETS.md on how to run PlatyPS.

The PlatyPS tool is an open source tool that stubs out the articles based on what it can see in the code. If that parameter is there but not being used then we need to document it is not used.

If we just remove it then it will show up again next time PlatyPS is run and it will show as a 'new' parameter.

Same for the other Pull Request.

Similar: #1580 (comment)

@kenwith
Here is the result of PlatyPS.

external help file: tmp_b3ja2k5m.qsu-help.xml
Module Name: tmp_b3ja2k5m.qsu
online version:
schema: 2.0.0

New-CsTeamsMeetingPolicy

SYNOPSIS

SYNTAX

DESCRIPTION

{{Fill in the Description}}

EXAMPLES

Example 1

PS C:\> {{ Add example code here }}

{{ Add example description here }}

PARAMETERS

CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).

INPUTS

None

OUTPUTS

System.Object

NOTES

RELATED LINKS

It doesn't show up - we renamed the parameter and I hid it from the per parameter documentation but missed it in the schema. If you can remove it that would be great, otherwise I'll do it.

@naminakao - thanks for putting the PR together. Merged. Much appreciated!