| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| Microsoft.PowerShell.Core | About Parameter Sets (5.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Parameter_Sets.md | --- description: Describes how to define and use parameter sets in advanced functions. Locale: en-US Previously updated : 09/20/2021 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameter_sets?view=powershell-5.1&WT.mc_id=ps-gethelp Title: about Parameter Sets --- PowerShell uses parameter sets to enable you to write a single function that can do different actions for different scenarios. Parameter sets enable you to expose different parameters to the user. And, to return different information based on the parameters specified by the user. You can only use one parameter-at a time. +set at a time. ## Parameter set requirements The following requirements apply to all parameter sets. +- If no parameter set is specified for a parameter, the parameter belongs to + all parameter sets. + - Each parameter set must have a unique combination of parameters. If possible,- at least one of the unique parameters should be a mandatory parameter. + at least one of the unique parameters should be a mandatory parameter. - A parameter set that contains multiple positional parameters must define unique positions for each parameter. No two positional parameters can specify The following requirements apply to all parameter sets. a value of `true`. Multiple parameters can define the `ValueFromPipelineByPropertyName` keyword with a value of `true`. -- If no parameter set is specified for a parameter, the parameter belongs to- all parameter sets. - > [!NOTE] > There is a limit of 32 parameter sets. |
| Microsoft.PowerShell.Core | About Preference Variables (5.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Preference_Variables.md | --- description: Variables that customize the behavior of PowerShell. Locale: en-US Previously updated : 02/09/2022 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Preference Variables cmdlet. ## \$PSModuleAutoloadingPreference Enables and disables automatic importing of modules in the session. **All** is-the default. Regardless of the variable's value, you can use -[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a module. +the default. To import a module, get or use any command in the module. For +example, use `Get-Command`. The `$PSModuleAutoloadingPreference` variable does +not exist by default. The default behavior when the variable is not defined is +the same as `$PSModuleAutoloadingPreference = 'All'`. ++Regardless of the variable's value, you can use +[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a +module. The `$PSModuleAutoloadingPreference` variable takes one of the [`PSModuleAutoLoadingPreference`](/dotnet/api/system.management.automation.psmoduleautoloadingpreference) enumeration values: Valid values are: -- **All**: Modules are imported automatically on first-use. To import a module,- get or use any command in the module. For example, use `Get-Command`. +- **All**: Modules are imported automatically on first-use. - **ModuleQualified**: Modules are imported automatically only when a user uses the module-qualified name of a command in the module. For example, if the user types `MyModule\MyCommand`, PowerShell imports the **MyModule** module. |
| Microsoft.PowerShell.Core | About Parameter Sets (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Parameter_Sets.md | --- description: Describes how to define and use parameter sets in advanced functions. Locale: en-US Previously updated : 09/20/2021 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameter_sets?view=powershell-7&WT.mc_id=ps-gethelp Title: about Parameter Sets --- PowerShell uses parameter sets to enable you to write a single function that can do different actions for different scenarios. Parameter sets enable you to expose different parameters to the user. And, to return different information based on the parameters specified by the user. You can only use one parameter-at a time. +set at a time. ## Parameter set requirements The following requirements apply to all parameter sets. +- If no parameter set is specified for a parameter, the parameter belongs to + all parameter sets. + - Each parameter set must have a unique combination of parameters. If possible,- at least one of the unique parameters should be a mandatory parameter. + at least one of the unique parameters should be a mandatory parameter. - A parameter set that contains multiple positional parameters must define unique positions for each parameter. No two positional parameters can specify The following requirements apply to all parameter sets. a value of `true`. Multiple parameters can define the `ValueFromPipelineByPropertyName` keyword with a value of `true`. -- If no parameter set is specified for a parameter, the parameter belongs to- all parameter sets. - > [!NOTE] > There is a limit of 32 parameter sets. |
| Microsoft.PowerShell.Core | About Preference Variables (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Preference_Variables.md | --- description: Variables that customize the behavior of PowerShell. Locale: en-US Previously updated : 02/09/2022 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Preference Variables cmdlet. ## \$PSModuleAutoloadingPreference Enables and disables automatic importing of modules in the session. **All** is-the default. Regardless of the variable's value, you can use -[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a module. +the default. To import a module, get or use any command in the module. For +example, use `Get-Command`. The `$PSModuleAutoloadingPreference` variable does +not exist by default. The default behavior when the variable is not defined is +the same as `$PSModuleAutoloadingPreference = 'All'`. ++Regardless of the variable's value, you can use +[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a +module. The `$PSModuleAutoloadingPreference` variable takes one of the [`PSModuleAutoLoadingPreference`](/dotnet/api/system.management.automation.psmoduleautoloadingpreference) enumeration values: Valid values are: -- **All**: Modules are imported automatically on first-use. To import a module,- get or use any command in the module. For example, use `Get-Command`. +- **All**: Modules are imported automatically on first-use. - **ModuleQualified**: Modules are imported automatically only when a user uses the module-qualified name of a command in the module. For example, if the user types `MyModule\MyCommand`, PowerShell imports the **MyModule** module. |
| Microsoft.PowerShell.Core | About Parameter Sets (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Parameter_Sets.md | --- description: Describes how to define and use parameter sets in advanced functions. Locale: en-US Previously updated : 09/20/2021 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameter_sets?view=powershell-7.1&WT.mc_id=ps-gethelp Title: about Parameter Sets --- Describes how to define and use parameter sets in advanced functions. PowerShell uses parameter sets to enable you to write a single function that can do different actions for different scenarios. Parameter sets enable you to expose different parameters to the user. And, to return different information-based on the parameters specified by the user. +based on the parameters specified by the user. You can only use one parameter +set at a time. ## Parameter set requirements The following requirements apply to all parameter sets. +- If no parameter set is specified for a parameter, the parameter belongs to + all parameter sets. + - Each parameter set must have a unique combination of parameters. If possible,- at least one of the unique parameters should be a mandatory parameter. + at least one of the unique parameters should be a mandatory parameter. - A parameter set that contains multiple positional parameters must define unique positions for each parameter. No two positional parameters can specify The following requirements apply to all parameter sets. a value of `true`. Multiple parameters can define the `ValueFromPipelineByPropertyName` keyword with a value of `true`. -- If no parameter set is specified for a parameter, the parameter belongs to- all parameter sets. - > [!NOTE] > There is a limit of 32 parameter sets. |
| Microsoft.PowerShell.Core | About Preference Variables (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Preference_Variables.md | --- description: Variables that customize the behavior of PowerShell. Locale: en-US Previously updated : 02/09/2022 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Preference Variables cmdlet. ### \$PSModuleAutoloadingPreference Enables and disables automatic importing of modules in the session. **All** is-the default. Regardless of the variable's value, you can use -[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a module. +the default. To import a module, get or use any command in the module. For +example, use `Get-Command`. The `$PSModuleAutoloadingPreference` variable does +not exist by default. The default behavior when the variable is not defined is +the same as `$PSModuleAutoloadingPreference = 'All'`. ++Regardless of the variable's value, you can use +[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a +module. The `$PSModuleAutoloadingPreference` variable takes one of the [`PSModuleAutoLoadingPreference`](/dotnet/api/system.management.automation.psmoduleautoloadingpreference) enumeration values: Valid values are: -- **All**: Modules are imported automatically on first-use. To import a module,- get or use any command in the module. For example, use `Get-Command`. +- **All**: Modules are imported automatically on first-use. - **ModuleQualified**: Modules are imported automatically only when a user uses the module-qualified name of a command in the module. For example, if the user types `MyModule\MyCommand`, PowerShell imports the **MyModule** module. |
| Microsoft.PowerShell.Core | About Parameter Sets (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Parameter_Sets.md | --- description: Describes how to define and use parameter sets in advanced functions. Locale: en-US Previously updated : 09/20/2021 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameter_sets?view=powershell-7.2&WT.mc_id=ps-gethelp Title: about Parameter Sets --- PowerShell uses parameter sets to enable you to write a single function that can do different actions for different scenarios. Parameter sets enable you to expose different parameters to the user. And, to return different information based on the parameters specified by the user. You can only use one parameter-at a time. +set at a time. ## Parameter set requirements The following requirements apply to all parameter sets. +- If no parameter set is specified for a parameter, the parameter belongs to + all parameter sets. + - Each parameter set must have a unique combination of parameters. If possible,- at least one of the unique parameters should be a mandatory parameter. + at least one of the unique parameters should be a mandatory parameter. - A parameter set that contains multiple positional parameters must define unique positions for each parameter. No two positional parameters can specify The following requirements apply to all parameter sets. a value of `true`. Multiple parameters can define the `ValueFromPipelineByPropertyName` keyword with a value of `true`. -- If no parameter set is specified for a parameter, the parameter belongs to- all parameter sets. - > [!NOTE] > There is a limit of 32 parameter sets. |
| Microsoft.PowerShell.Core | About Preference Variables (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Preference_Variables.md | --- description: Variables that customize the behavior of PowerShell. Locale: en-US Previously updated : 02/09/2022 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Preference Variables cmdlet. ## \$PSModuleAutoloadingPreference Enables and disables automatic importing of modules in the session. **All** is-the default. Regardless of the variable's value, you can use -[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a module. +the default. To import a module, get or use any command in the module. For +example, use `Get-Command`. The `$PSModuleAutoloadingPreference` variable does +not exist by default. The default behavior when the variable is not defined is +the same as `$PSModuleAutoloadingPreference = 'All'`. ++Regardless of the variable's value, you can use +[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a +module. The `$PSModuleAutoloadingPreference` variable takes one of the [`PSModuleAutoLoadingPreference`](/dotnet/api/system.management.automation.psmoduleautoloadingpreference) enumeration values: Valid values are: -- **All**: Modules are imported automatically on first-use. To import a module,- get or use any command in the module. For example, use `Get-Command`. +- **All**: Modules are imported automatically on first-use. - **ModuleQualified**: Modules are imported automatically only when a user uses the module-qualified name of a command in the module. For example, if the user types `MyModule\MyCommand`, PowerShell imports the **MyModule** module. |
| Microsoft.PowerShell.Core | About Parameter Sets (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Parameter_Sets.md | --- description: Describes how to define and use parameter sets in advanced functions. Locale: en-US Previously updated : 09/20/2021 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameter_sets?view=powershell-7.3&WT.mc_id=ps-gethelp Title: about Parameter Sets --- PowerShell uses parameter sets to enable you to write a single function that can do different actions for different scenarios. Parameter sets enable you to expose different parameters to the user. And, to return different information based on the parameters specified by the user. You can only use one parameter-at a time. +set at a time. ## Parameter set requirements The following requirements apply to all parameter sets. +- If no parameter set is specified for a parameter, the parameter belongs to + all parameter sets. + - Each parameter set must have a unique combination of parameters. If possible,- at least one of the unique parameters should be a mandatory parameter. + at least one of the unique parameters should be a mandatory parameter. - A parameter set that contains multiple positional parameters must define unique positions for each parameter. No two positional parameters can specify The following requirements apply to all parameter sets. a value of `true`. Multiple parameters can define the `ValueFromPipelineByPropertyName` keyword with a value of `true`. -- If no parameter set is specified for a parameter, the parameter belongs to- all parameter sets. - > [!NOTE] > There is a limit of 32 parameter sets. |
| Microsoft.PowerShell.Core | About Preference Variables (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Preference_Variables.md | --- description: Variables that customize the behavior of PowerShell. Locale: en-US Previously updated : 02/09/2022 Last updated : 03/11/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Preference Variables cmdlet. ## \$PSModuleAutoloadingPreference Enables and disables automatic importing of modules in the session. **All** is-the default. Regardless of the variable's value, you can use -[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a module. +the default. To import a module, get or use any command in the module. For +example, use `Get-Command`. The `$PSModuleAutoloadingPreference` variable does +not exist by default. The default behavior when the variable is not defined is +the same as `$PSModuleAutoloadingPreference = 'All'`. ++Regardless of the variable's value, you can use +[Import-Module](xref:Microsoft.PowerShell.Core.Import-Module) to import a +module. The `$PSModuleAutoloadingPreference` variable takes one of the [`PSModuleAutoLoadingPreference`](/dotnet/api/system.management.automation.psmoduleautoloadingpreference) enumeration values: Valid values are: -- **All**: Modules are imported automatically on first-use. To import a module,- get or use any command in the module. For example, use `Get-Command`. +- **All**: Modules are imported automatically on first-use. - **ModuleQualified**: Modules are imported automatically only when a user uses the module-qualified name of a command in the module. For example, if the user types `MyModule\MyCommand`, PowerShell imports the **MyModule** module. |
| install | Powershell Support Lifecycle | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/install/PowerShell-Support-Lifecycle.md | --- description: Details the policies governing support for PowerShell Previously updated : 11/08/2021 Last updated : 03/10/2022 Title: PowerShell Support Lifecycle --- # PowerShell Support Lifecycle used. The following table contains a timeline of the major releases of PowerShell. This table is provided for historical reference. It is not intended for use to determine the support lifecycle. -| Version | Release Date | Note | -| ---------------------------- | :----------: | -------------------------------------------------------------------------------- | -| PowerShell 7.2 (LTS-current) | Nov-2024 | Built on .NET 6.0 (LTS-current). | -| PowerShell 7.1 | Nov-2020 | Built on .NET 5.0. | -| PowerShell 7.0 (LTS) | Mar-2020 | Built on .NET Core 3.1 (LTS). | -| PowerShell 6.2 | Mar-2019 | | -| PowerShell 6.1 | Sep-2018 | Built on .NET Core 2.1. | -| PowerShell 6.0 | Jan-2018 | First release, built on .NET Core 2.0. Installable on Windows, Linux, and macOS. | -| Windows PowerShell 5.1 | Aug-2016 | Released in Windows 10 Anniversary Update and Windows Server 2016, WMF 5.1 | -| Windows PowerShell 5.0 | Feb-2016 | Released in Windows Management Framework (WMF) 5.0 | -| Windows PowerShell 4.0 | Oct-2013 | Integrated in Windows 8.1 and with Windows Server 2012 R2, WMF 4.0 | -| Windows PowerShell 3.0 | Oct-2012 | Integrated in Windows 8 and with Windows Server 2012 WMF 3.0 | -| Windows PowerShell 2.0 | Jul-2009 | Integrated in Windows 7 and Windows Server 2008 R2, WMF 2.0 | -| Windows PowerShell 1.0 | Nov-2006 | Optional component of Windows Server 2008 | +| Version | Release Date | Note | +| ---------------------------- | :----------: | ------------------------------------------------------------------------------- | +| PowerShell 7.3 (preview) | Jan-2022 | Built on .NET 7.0 (preview) | +| PowerShell 7.2 (LTS-current) | Nov-2021 | Built on .NET 6.0 (LTS-current) | +| PowerShell 7.1 | Nov-2020 | Built on .NET 5.0 | +| PowerShell 7.0 (LTS) | Mar-2020 | Built on .NET Core 3.1 (LTS) | +| PowerShell 6.2 | Mar-2019 | | +| PowerShell 6.1 | Sep-2018 | Built on .NET Core 2.1 | +| PowerShell 6.0 | Jan-2018 | First release, built on .NET Core 2.0. Installable on Windows, Linux, and macOS | +| Windows PowerShell 5.1 | Aug-2016 | Released in Windows 10 Anniversary Update and Windows Server 2016, WMF 5.1 | +| Windows PowerShell 5.0 | Feb-2016 | Released in Windows Management Framework (WMF) 5.0 | +| Windows PowerShell 4.0 | Oct-2013 | Integrated in Windows 8.1 and with Windows Server 2012 R2, WMF 4.0 | +| Windows PowerShell 3.0 | Oct-2012 | Integrated in Windows 8 and with Windows Server 2012 WMF 3.0 | +| Windows PowerShell 2.0 | Jul-2009 | Integrated in Windows 7 and Windows Server 2008 R2, WMF 2.0 | +| Windows PowerShell 1.0 | Nov-2006 | Optional component of Windows Server 2008 | <!-- hyperlink references --> |
| includes | Alpine Support | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/includes/alpine-support.md | --- Previously updated : 01/19/2022 Last updated : 03/10/2022 ms.prod: powershell --- supported on. These versions are supported until either the version of | Alpine | 7.0 (LTS) | 7.1 | 7.2 (LTS-current) | 7.3 (preview) | | ------------- | :-------: | :-------: | :---------------: | :-----------: |-| ✅ 3.12 | ✅ | ✅ | ❌ | ❌ | -| ✅ 3.11 | ✅ | ✅ | ❌ | ❌ | +| ✅ 3.14 | ❌ | ❌ | ✅ | ✅ | +| ✅ 3.13 | ❌ | ✅ | ✅ | ✅ | +| ✅ 3.12 | ✅ | ✅ | ✅ | ✅ | +| ✅ 3.11 | ❌ | 🟡 | ❌ | ❌ | | ❌ 3.10 | 🟡 | 🟡 | ❌ | ❌ | | ❌ 3.9 | 🟡 | 🟡 | ❌ | ❌ | -PowerShell has not been tested on Alpine versions 3.13 and 3.14. +PowerShell has not been tested on Alpine 3.15. > [!NOTE] > CIM, PowerShell Remoting, and DSC are not supported on Alpine. |
| includes | Centos Support | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/includes/centos-support.md | --- Previously updated : 01/19/2022 Last updated : 03/10/2022 ms.prod: powershell --- |
| includes | Debian Support | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/includes/debian-support.md | --- Previously updated : 01/19/2022 Last updated : 03/10/2022 ms.prod: powershell --- they're supported on. These versions remain supported until either the version o | Debian | 7.0 (LTS) | 7.1 | 7.2 (LTS-current) | 7.3 (preview) | | ----------- | :-------: | :------: | :---------------: | :-----------: |-| ✅ 11 | ❌ | ❌ | ✅ | ✅ | +| ✅ 11 | ✅ | ✅ | ✅ | ✅ | | ✅ 10 | ✅ | ✅ | ✅ | ✅ |-| ✅ 9 | ✅ | ✅ | ❌ | ❌ | +| ✅ 9 | ✅ | ✅ | ✅ | ✅ | | ❌ 8 | 🟡 | ❌ | ❌ | ❌ | PowerShell is supported on Debian for the following processor architectures. |
| includes | Fedora Support | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/includes/fedora-support.md | --- Previously updated : 01/19/2022 Last updated : 03/10/2022 ms.prod: powershell --- supported on. These versions are supported until either the version of | Fedora | 7.0 (LTS) | 7.1 (current) | 7.2 (LTS-current) | 7.3 (preview) | | ----------- | :-------: | :-----------: | :---------------: | :-----------: |-| ✅ 32 | 🟡 | 🟡 | ❌ | ❌ | -| ❌ 31 | 🟡 | 🟡 | ❌ | ❌ | -| ❌ 30 | 🟡 | 🟡 | ❌ | ❌ | +| ✅ 34 | ❌ | ❌ | ✅ | ✅ | +| ❌ 33 | ❌ | ❌ | ❌ | ❌ | +| ❌ 32 | ❌ | 🟡 | 🟡 | ❌ | +| ❌ 31 | ❌ | ❌ | ❌ | ❌ | +| ❌ 30 | 🟡 | ❌ | ❌ | ❌ | -PowerShell has not been tested on Fedora versions 33 and 34. +PowerShell has not been tested on Fedora version 35. PowerShell is supported on Fedora for the following processor architectures. |
| includes | Rhel Support | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/includes/rhel-support.md | --- Previously updated : 01/19/2022 Last updated : 03/10/2022 ms.prod: powershell --- |
| includes | Ubuntu Support | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/includes/ubuntu-support.md | --- Previously updated : 01/19/2022 Last updated : 03/10/2022 ms.prod: powershell --- |