Replace legacy build pipeline with PowerShell SDP build pipeline (Mic…

…rosoftDocs#6257)

* Replace legacy build pipeline with PowerShell SDP build pipeline

* Fix build warnings

* update docfx author metadata

Co-authored-by: Sean Wheeler <[email protected]>

.openpublishing.publish.config.json

@@ -3,16 +3,11 @@
     "branches_to_filter": [],
     "build_entry_point": "docs",
     "contribution_branch_mappings": {},
-    "dependent_packages": [{
-            "id": "opbuild.templates.azurecli",
-            "nuget_feed": "https://www.myget.org/F/op/api/v2",
-            "path_to_root": "_dependentPackages/azurecli.plugins",
-            "version": "latest"
-        },
+    "dependent_packages": [
         {
-            "id": "Microsoft.OpenPublishing.CommonPlugins",
+            "id": "Microsoft.DocAsCode.MAML2Yaml",
             "nuget_feed": "https://www.myget.org/F/op/api/v2",
-            "path_to_root": "_dependentPackages/CommonPlugins",
+            "path_to_root": "_dependentPackages/MAML2Yaml",
             "target_framework": "net45",
             "version": "latest"
         }
@@ -36,12 +31,9 @@
         "build_source_folder": "reference",
         "customized_tasks": {
             "docset_prebuild": [
-                "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1"
+                "_dependentPackages/MAML2Yaml/tools/Run.ps1"
             ]
         },
-        "customized_template_paths": [
-            "_dependentPackages/azurecli.plugins/azurecli"
-        ],
         "docset_name": "PowerShell_PowerShell-docs_reference",
         "locale": "en-us",
         "monikerPath": [
@@ -52,10 +44,9 @@
         "open_to_public_contributors": true,
         "template_folder": "_themes",
         "type_mapping": {
-            "AzurePSModulePage": "Content",
-            "Conceptual": "Content",
-            "ManagedReference": "Content",
-            "RestApi": "Content"
+            "PowershellModule": "Content",
+            "PowershellCmdlet": "Content",
+            "Conceptual": "Content"
         },
         "xref_query_tags": ["/dotnet", "/uwp/api"],
         "version": 0

reference/5.1/Microsoft.PowerShell.Core/About/about_Alias_Provider.md

@@ -39,23 +39,23 @@ The aliases have no child items.
 The **Alias** provider supports the following cmdlets, which are covered
 in this article.
 
-- [Get-Location](../../Microsoft.PowerShell.Management/Get-Location.md)
-- [Set-Location](../../Microsoft.PowerShell.Management/Set-Location.md)
-- [Get-Item](../../Microsoft.PowerShell.Management/Get-Item.md)
-- [New-Item](../../Microsoft.PowerShell.Management/New-Item.md)
-- [Remove-Item](../../Microsoft.PowerShell.Management/Remove-Item.md)
-- [Clear-Item](../../Microsoft.PowerShell.Management/Clear-Item.md)
+- [Get-Location](xref:Microsoft.PowerShell.Management.Get-Location)
+- [Set-Location](xref:Microsoft.PowerShell.Management.Set-Location)
+- [Get-Item](xref:Microsoft.PowerShell.Management.Get-Item)
+- [New-Item](xref:Microsoft.PowerShell.Management.New-Item)
+- [Remove-Item](xref:Microsoft.PowerShell.Management.Remove-Item)
+- [Clear-Item](xref:Microsoft.PowerShell.Management.Clear-Item)
 
 PowerShell includes a set of cmdlets that are designed to view and to change
 aliases. When you use **Alias** cmdlets, you do not need to specify the
 `Alias:` drive in the name. This article does not cover working with **Alias**
 cmdlets.
 
-- [Export-Alias](../../Microsoft.PowerShell.Utility/Export-Alias.md)
-- [Get-Alias](../../Microsoft.PowerShell.Utility/Get-Alias.md)
-- [Import-Alias](../../Microsoft.PowerShell.Utility/Import-Alias.md)
-- [New-Alias](../../Microsoft.PowerShell.Utility/New-Alias.md)
-- [Set-Alias](../../Microsoft.PowerShell.Utility/Set-Alias.md)
+- [Export-Alias](xref:Microsoft.PowerShell.Utility.Export-Alias)
+- [Get-Alias](xref:Microsoft.PowerShell.Utility.Get-Alias)
+- [Import-Alias](xref:Microsoft.PowerShell.Utility.Import-Alias)
+- [New-Alias](xref:Microsoft.PowerShell.Utility.New-Alias)
+- [Set-Alias](xref:Microsoft.PowerShell.Utility.Set-Alias)
 
 ## Types exposed by this provider
 
@@ -85,9 +85,9 @@ path.
 > [!NOTE]
 > PowerShell uses aliases to allow you a familiar way to work with provider
 > paths. Commands such as `dir` and `ls` are now aliases for
-> [Get-ChildItem](../../Microsoft.PowerShell.Management/Get-ChildItem.md),
-> `cd` is an alias for [Set-Location](../../Microsoft.PowerShell.Management/Set-Location.md). and `pwd` is
-> an alias for [Get-Location](../../Microsoft.PowerShell.Management/Get-Location.md).
+> [Get-ChildItem](xref:Microsoft.PowerShell.Management.Get-ChildItem),
+> `cd` is an alias for [Set-Location](xref:Microsoft.PowerShell.Management.Set-Location). and `pwd` is
+> an alias for [Get-Location](xref:Microsoft.PowerShell.Management.Get-Location).
 
 ### Displaying the Contents of the Alias: drive
 
@@ -290,8 +290,8 @@ Determines the value of the **Options** property of an alias.
 
 #### Cmdlets supported
 
-- [New-Item](../../Microsoft.PowerShell.Management/New-Item.md)
-- [Set-Item](../../Microsoft.PowerShell.Management/Set-Item.md)
+- [New-Item](xref:Microsoft.PowerShell.Management.New-Item)
+- [Set-Item](xref:Microsoft.PowerShell.Management.Set-Item)
 
 ## Using the pipeline
 
@@ -306,8 +306,8 @@ Beginning in Windows PowerShell 3.0, you can get customized help topics for
 provider cmdlets that explain how those cmdlets behave in a file system drive.
 
 To get the help topics that are customized for the file system drive, run a
-[Get-Help](../Get-Help.md) command in a file system drive or use the `-Path`
-parameter of [Get-Help](../Get-Help.md) to specify a file system drive.
+[Get-Help](xref:Microsoft.PowerShell.Core.Get-Help) command in a file system drive or use the `-Path`
+parameter of [Get-Help](xref:Microsoft.PowerShell.Core.Get-Help) to specify a file system drive.
 
 ```powershell
 Get-Help Get-ChildItem

reference/5.1/Microsoft.PowerShell.Core/About/about_Aliases.md

@@ -259,13 +259,13 @@ Get-Help Alias
 
 ## SEE ALSO
 
-- [New-Alias](../../Microsoft.PowerShell.Utility/New-Alias.md)
-- [Get-Alias](../../Microsoft.PowerShell.Utility/Get-Alias.md)
-- [Set-Alias](../../Microsoft.PowerShell.Utility/Set-Alias.md)
-- [Export-Alias](../../Microsoft.PowerShell.Utility/Export-Alias.md)
-- [Import-Alias](../../Microsoft.PowerShell.Utility/Import-Alias.md)
-- [Get-PSProvider](../../Microsoft.PowerShell.Management/Get-PSProvider.md)
-- [Get-PSDrive](../../Microsoft.PowerShell.Management/Get-PSDrive.md)
+- [New-Alias](xref:Microsoft.PowerShell.Utility.New-Alias)
+- [Get-Alias](xref:Microsoft.PowerShell.Utility.Get-Alias)
+- [Set-Alias](xref:Microsoft.PowerShell.Utility.Set-Alias)
+- [Export-Alias](xref:Microsoft.PowerShell.Utility.Export-Alias)
+- [Import-Alias](xref:Microsoft.PowerShell.Utility.Import-Alias)
+- [Get-PSProvider](xref:Microsoft.PowerShell.Management.Get-PSProvider)
+- [Get-PSDrive](xref:Microsoft.PowerShell.Management.Get-PSDrive)
 - [about_functions](about_functions.md)
 - [about_profiles](about_profiles.md)
 - [about_providers](about_providers.md)

reference/5.1/Microsoft.PowerShell.Core/About/about_Arithmetic_Operators.md

@@ -529,5 +529,5 @@ right operand determine how many bits of the left operand are shifted.
 * [about_hash_tables](about_Hash_Tables.md)
 * [about_operators](about_Operators.md)
 * [about_variables](about_Variables.md)
-* [Get-Date](../../Microsoft.PowerShell.Utility/Get-Date.md)
-* [New-TimeSpan](../../Microsoft.PowerShell.Utility/New-TimeSpan.md)
+* [Get-Date](xref:Microsoft.PowerShell.Utility.Get-Date)
+* [New-TimeSpan](xref:Microsoft.PowerShell.Utility.New-TimeSpan)

reference/5.1/Microsoft.PowerShell.Core/About/about_Assignment_Operators.md

@@ -334,8 +334,8 @@ $a
 
 You cannot use the `-=` operator to delete the values of a variable. To delete
 all the values that are assigned to a variable, use the
-[Clear-Item](../../Microsoft.PowerShell.Management/Clear-Item.md) or
-[Clear-Variable](../../Microsoft.PowerShell.Utility/Clear-Variable.md) cmdlets
+[Clear-Item](xref:Microsoft.PowerShell.Management.Clear-Item) or
+[Clear-Variable](xref:Microsoft.PowerShell.Utility.Clear-Variable) cmdlets
 to assign a value of `$null` or `""` to the variable.
 
 ```powershell
@@ -368,7 +368,7 @@ $a
 ```
 
 To delete a variable, use the
-[Remove-Variable](../../Microsoft.PowerShell.Utility/Remove-Variable.md)
+[Remove-Variable](xref:Microsoft.PowerShell.Utility.Remove-Variable)
 cmdlet. This method is useful when the variable is explicitly cast to a
 particular data type, and you want an untyped variable. The following command
 deletes the `$a` variable:
@@ -847,7 +847,7 @@ $a = $b = $c = $d = "three"
 
 In addition to using an assignment operation to set a variable value, you
 can also use the
-[Set-Variable](../../Microsoft.PowerShell.Utility/Set-Variable.md) cmdlet. For
+[Set-Variable](xref:Microsoft.PowerShell.Utility.Set-Variable) cmdlet. For
 example, the following command uses `Set-Variable` to assign an array of 1,
 2, 3 to the `$a` variable.
 
@@ -863,8 +863,8 @@ Set-Variable -Name a -Value 1, 2, 3
 
 [about_Variables](about_Variables.md)
 
-[Clear-Variable](../../Microsoft.PowerShell.Utility/Clear-Variable.md)
+[Clear-Variable](xref:Microsoft.PowerShell.Utility.Clear-Variable)
 
-[Remove-Variable](../../Microsoft.PowerShell.Utility/Remove-Variable.md)
+[Remove-Variable](xref:Microsoft.PowerShell.Utility.Remove-Variable)
 
-[Set-Variable](../../Microsoft.PowerShell.Utility/Set-Variable.md)
+[Set-Variable](xref:Microsoft.PowerShell.Utility.Set-Variable)

reference/5.1/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md

@@ -568,7 +568,7 @@ the enumerator has passed the end of the collection.
 > [!NOTE]
 > The **Boolean** value returned my **MoveNext** is sent to the output stream.
 > You can suppress the output by typecasting it to `[void]` or piping it to
-> [Out-Null](../Out-Null.md).
+> [Out-Null](xref:Microsoft.PowerShell.Core.Out-Null).
 >
 > ```powershell
 > $input.MoveNext() | Out-Null

reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md

@@ -64,6 +64,6 @@ understand the **ThrottleLimit**.
 
 ## SEE ALSO
 
-[New-CimSession](../../CimCmdlets/New-CimSession.md)
+[New-CimSession](xref:CimCmdlets.New-CimSession)
 
 [about_PSSessions](about_PSSessions.md)

reference/5.1/Microsoft.PowerShell.Core/About/about_Command_Precedence.md

@@ -160,13 +160,13 @@ accessible.
 
 ### Finding hidden commands
 
-The **All** parameter of the [Get-Command](../../Microsoft.PowerShell.Core/Get-Command.md)
+The **All** parameter of the [Get-Command](xref:Microsoft.PowerShell.Core.Get-Command)
 cmdlet gets all commands with the specified name, even if they are hidden
 or replaced. Beginning in PowerShell 3.0, by default, `Get-Command`
 gets only the commands that run when you type the command name.
 
 In the following examples, the session includes a `Get-Date` function and a
-[Get-Date](../../Microsoft.PowerShell.Utility/Get-Date.md) cmdlet.
+[Get-Date](xref:Microsoft.PowerShell.Utility.Get-Date) cmdlet.
 
 The following command gets the `Get-Date` command that runs when you type
 `Get-Date`.
@@ -251,9 +251,9 @@ Microsoft.PowerShell.Utility
 #### Call operator
 
 You can also use the `Call` operator `&` to run hidden commands by combining
-it with a call to [Get-ChildItem](../../Microsoft.PowerShell.Management/Get-ChildItem.md)
+it with a call to [Get-ChildItem](xref:Microsoft.PowerShell.Management.Get-ChildItem)
 (the alias is "dir"), `Get-Command` or
-[Get-Module](../../Microsoft.PowerShell.Core/Get-Module.md).
+[Get-Module](xref:Microsoft.PowerShell.Core.Get-Module).
 
 The call operator executes strings and script blocks in a child scope. For more information, see [about_Operators](about_Operators.md).
 
@@ -301,9 +301,9 @@ name acronym to the nouns in your commands.
 
 Also, when you import commands into your session from a PowerShell
 module or from another session, use the `Prefix` parameter of the
-[Import-Module](../../Microsoft.PowerShell.Core/Import-Module.md) or
+[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) or
 
-[Import-PSSession](../../Microsoft.PowerShell.Utility/Import-PSSession.md)
+[Import-PSSession](xref:Microsoft.PowerShell.Utility.Import-PSSession)
 cmdlet to add a prefix to the nouns in the names of commands.
 
 For example, the following command avoids any conflict with the `Get-Date`
@@ -323,6 +323,6 @@ For more information, see `Import-Module` and `Import-PSSession` below.
 - [about_Functions](about_Functions.md)
 - [Alias-Provider](../../Microsoft.PowerShell.Core/About/about_Alias_Provider.md)
 - [Function-Provider](../../Microsoft.PowerShell.Core/About/about_Function_Provider.md)
-- [Get-Command](../../Microsoft.PowerShell.Core/Get-Command.md)
-- [Import-Module](../../Microsoft.PowerShell.Core/Import-Module.md)
-- [Import-PSSession](../../Microsoft.PowerShell.Utility/Import-PSSession.md)
+- [Get-Command](xref:Microsoft.PowerShell.Core.Get-Command)
+- [Import-Module](xref:Microsoft.PowerShell.Core.Import-Module)
+- [Import-PSSession](xref:Microsoft.PowerShell.Utility.Import-PSSession)

reference/5.1/Microsoft.PowerShell.Core/About/about_Command_Syntax.md

@@ -14,8 +14,8 @@ Describes the syntax diagrams that are used in PowerShell.
 
 ## LONG DESCRIPTION
 
-The [Get-Help](../../Microsoft.PowerShell.Core/Get-Help.md) and
-[Get-Command](../../Microsoft.PowerShell.Core/Get-Command.md) cmdlets display
+The [Get-Help](xref:Microsoft.PowerShell.Core.Get-Help) and
+[Get-Command](xref:Microsoft.PowerShell.Core.Get-Command) cmdlets display
 syntax diagrams to help you construct commands correctly. This topic
 explains how to interpret the syntax diagrams.
 
@@ -36,7 +36,7 @@ PowerShell uses the following notation for syntax diagrams.
 [-<Optional Parameter Name>] <Required Parameter Value>
 ```
 
-The following is the syntax for the [New-Alias](../../Microsoft.PowerShell.Utility/New-Alias.md)
+The following is the syntax for the [New-Alias](xref:Microsoft.PowerShell.Utility.New-Alias)
 cmdlet.
 
 ```powershell
@@ -136,7 +136,7 @@ the format of a valid command. A parameter set includes only parameters that
 can be used together in a command. If parameters cannot be used in the same
 command, they appear in separate parameter sets.
 
-For example, the [Get-Random](../../Microsoft.PowerShell.Utility/Get-Random.md)
+For example, the [Get-Random](xref:Microsoft.PowerShell.Utility.Get-Random)
 cmdlet has the following parameter sets:
 
 ```powershell
@@ -222,7 +222,7 @@ The syntax diagrams use the following symbols:
 
   For example, the **Name** parameter of the `New-Alias` cmdlet takes only
   one string, but the **Name** parameter of
-  [Get-Process](../../Microsoft.PowerShell.Management/Get-Process.md) can take
+  [Get-Process](xref:Microsoft.PowerShell.Management.Get-Process) can take
   one or many strings.
 
   ```powershell
@@ -314,5 +314,5 @@ optional.
 ## SEE ALSO
 
 - [about_Parameters](about_Parameters.md)
-- [Get-Command](../../Microsoft.PowerShell.Core/Get-Command.md)
-- [Get-Help](../../Microsoft.PowerShell.Core/Get-Help.md)
+- [Get-Command](xref:Microsoft.PowerShell.Core.Get-Command)
+- [Get-Help](xref:Microsoft.PowerShell.Core.Get-Help)

reference/5.1/Microsoft.PowerShell.Core/About/about_Comment_Based_Help.md

@@ -15,7 +15,7 @@ Describes how to write comment-based help topics for functions and scripts.
 You can write comment-based help topics for functions and scripts by using
 special help comment keywords.
 
-The [Get-Help](../Get-Help.md) cmdlet displays comment-based help in the same
+The [Get-Help](xref:Microsoft.PowerShell.Core.Get-Help) cmdlet displays comment-based help in the same
 format in which it displays the cmdlet help topics that are generated from XML
 files. Users can use all of the parameters of `Get-Help`, such as
 **Detailed**, **Full**, **Examples**, and **Online**, to display the contents
@@ -28,9 +28,9 @@ cannot find XML-based help topics for functions or scripts.
 
 This topic explains how to write help topics for functions and scripts. For
 information about how to display help topics for functions and scripts, see
-[Get-Help](../Get-Help.md).
+[Get-Help](xref:Microsoft.PowerShell.Core.Get-Help).
 
-The [Update-Help](../Update-Help.md) and [Save-Help](../Save-Help.md) cmdlets
+The [Update-Help](xref:Microsoft.PowerShell.Core.Update-Help) and [Save-Help](xref:Microsoft.PowerShell.Core.Save-Help) cmdlets
 work only on XML files. Updatable Help does not support comment-based help
 topics.
 
@@ -322,7 +322,7 @@ this keyword to avoid conflicts when there are commands with the same name.
 
 Specifies a session that contains the help topic. Enter a variable that
 contains a **PSSession** object. This keyword is used by the
-[Export-PSSession](../../Microsoft.PowerShell.Utility/Export-PSSession.md)
+[Export-PSSession](xref:Microsoft.PowerShell.Utility.Export-PSSession)
 cmdlet to find the help topics for the exported commands.
 
 ```powershell

reference/5.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md

@@ -690,10 +690,10 @@ about_Common_Parameters
 
 [about_Preference_Variables](about_Preference_Variables.md)
 
-[Write-Debug](../../Microsoft.PowerShell.Utility/Write-Debug.md)
+[Write-Debug](xref:Microsoft.PowerShell.Utility.Write-Debug)
 
-[Write-Warning](../../Microsoft.PowerShell.Utility/Write-Warning.md)
+[Write-Warning](xref:Microsoft.PowerShell.Utility.Write-Warning)
 
-[Write-Error](../../Microsoft.PowerShell.Utility/Write-Error.md)
+[Write-Error](xref:Microsoft.PowerShell.Utility.Write-Error)
 
-[Write-Verbose](../../Microsoft.PowerShell.Utility/Write-Verbose.md)
+[Write-Verbose](xref:Microsoft.PowerShell.Utility.Write-Verbose)

reference/5.1/Microsoft.PowerShell.Core/About/about_Comparison_Operators.md

@@ -700,6 +700,6 @@ True
 - [about_Operators](about_Operators.md)
 - [about_Regular_Expressions](about_Regular_Expressions.md)
 - [about_Wildcards](about_Wildcards.md)
-- [Compare-Object](../../Microsoft.PowerShell.Utility/Compare-Object.md)
-- [Foreach-Object](../ForEach-Object.md)
-- [Where-Object](../Where-Object.md)
+- [Compare-Object](xref:Microsoft.PowerShell.Utility.Compare-Object)
+- [Foreach-Object](xref:Microsoft.PowerShell.Core.ForEach-Object)
+- [Where-Object](xref:Microsoft.PowerShell.Core.Where-Object)

reference/5.1/Microsoft.PowerShell.Core/About/about_Data_Sections.md

@@ -214,6 +214,6 @@ DATA -supportedCommand Format-XML {
 
 [about_Script_Internationalization](about_Script_Internationalization.md)
 
-[ConvertFrom-StringData](../../Microsoft.PowerShell.Utility/ConvertFrom-StringData.md)
+[ConvertFrom-StringData](xref:Microsoft.PowerShell.Utility.ConvertFrom-StringData)
 
-[Import-LocalizedData](../../Microsoft.PowerShell.Utility/Import-LocalizedData.md)
+[Import-LocalizedData](xref:Microsoft.PowerShell.Utility.Import-LocalizedData)

reference/5.1/Microsoft.PowerShell.Core/About/about_Debuggers.md

@@ -850,11 +850,11 @@ features that you can use to debug scripts and functions.
 
 ## SEE ALSO
 
-- [Disable-PSBreakpoint](../../Microsoft.PowerShell.Utility/Disable-PsBreakpoint.md)
-- [Enable-PSBreakpoint](../../Microsoft.PowerShell.Utility/Enable-PsBreakpoint.md)
-- [Get-PSBreakpoint](../../Microsoft.PowerShell.Utility/Get-PsBreakpoint.md)
-- [Get-PSCallStack](../../Microsoft.PowerShell.Utility/Get-PsCallStack.md)
-- [Remove-PSBreakpoint](../../Microsoft.PowerShell.Utility/Remove-PsBreakpoint.md)
-- [Set-PSBreakpoint](../../Microsoft.PowerShell.Utility/Set-PSBreakpoint.md)
-- [Write-Debug](../../Microsoft.PowerShell.Utility/Write-Debug.md)
-- [Write-Verbose](../../Microsoft.PowerShell.Utility/Write-Verbose.md)
+- [Disable-PSBreakpoint](xref:Microsoft.PowerShell.Utility.Disable-PSBreakpoint)
+- [Enable-PSBreakpoint](xref:Microsoft.PowerShell.Utility.Enable-PSBreakpoint)
+- [Get-PSBreakpoint](xref:Microsoft.PowerShell.Utility.Get-PSBreakpoint)
+- [Get-PSCallStack](xref:Microsoft.PowerShell.Utility.Get-PSCallStack)
+- [Remove-PSBreakpoint](xref:Microsoft.PowerShell.Utility.Remove-PSBreakpoint)
+- [Set-PSBreakpoint](xref:Microsoft.PowerShell.Utility.Set-PSBreakpoint)
+- [Write-Debug](xref:Microsoft.PowerShell.Utility.Write-Debug)
+- [Write-Verbose](xref:Microsoft.PowerShell.Utility.Write-Verbose)