Skip to content

Commit 15b8342

Browse files
authored
Minor editorial updates (#11093)
1 parent c638925 commit 15b8342

1 file changed

Lines changed: 36 additions & 38 deletions

File tree

reference/docs-conceptual/install/PowerShell-Support-Lifecycle.md

Lines changed: 36 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -8,36 +8,52 @@ title: PowerShell Support Lifecycle
88

99
> [!NOTE]
1010
> This document is about support for PowerShell. Windows PowerShell (1.0 - 5.1) is a component of
11-
> the Windows operating system. Components receive the same support as their parent product or
12-
> platform. For more information, see [Product and Services Lifecycle Information][03].
11+
> the Windows operating system. For more information, see
12+
> [Product and Services Lifecycle Information][03].
1313
14-
PowerShell is supported under the [Microsoft Modern Lifecycle Policy][02], but support dates are
15-
linked to [.NET and .NET Core Support Policy][06]. In this servicing approach, customers can choose
16-
Long Term Support (LTS) releases or current releases.
14+
PowerShell follows the [Microsoft Modern Lifecycle Policy][02]. Support dates follow the
15+
[.NET Support Policy][06]. In this servicing approach, customers can choose Long Term Support (LTS)
16+
releases or current releases.
1717

18-
An **LTS** release of PowerShell is built on an LTS release of .NET. Updates to an LTS release only
19-
contain critical security updates and servicing fixes that are designed to minimize impact on
20-
existing workloads. LTS releases of PowerShell are supported until the end-of-support for .NET.
18+
An **LTS** release of PowerShell is built on an **LTS** release of .NET. Updates to an **LTS**
19+
release only contain critical security updates and servicing fixes that are designed to minimize
20+
impact on existing workloads.
2121

22-
A **current** release is a release that occurs between LTS releases. Current releases can contain
23-
critical fixes, innovations, and new features. A current release is supported for six months after
24-
the next release (current or LTS).
22+
A **current** release is a release that occurs between **LTS** releases. Current releases can
23+
contain critical fixes, innovations, and new features. Microsoft supports a **current** release for
24+
six months after the next **LTS** release.
2525

26-
> [!IMPORTANT]
27-
> You must have the latest patch update installed to qualify for support. For example, if you're
28-
> running PowerShell 7.4.0 and 7.4.2 has been released, you must update to 7.4.2 to qualify for
29-
> support.
26+
Both **LTS** and **current** versions of PowerShell receive security updates and bug fixes.
27+
Microsoft only supports the latest update version of a release.
28+
29+
## Getting support
30+
31+
Microsoft provides support for PowerShell on a best-effort basis. Support for Windows PowerShell 5.1
32+
is provided through Windows support channels. You can use the standard paid support channels to get
33+
support for PowerShell.
34+
35+
- [Support for business][18]
36+
- [Contact support][17]
37+
38+
There are many free support options available from the PowerShell community. The most active
39+
community support channels are available through **Discord** or **Slack**. The discussion channels
40+
are mirrored on both platforms, so you can choose the platform that you prefer. These channels can
41+
help you troubleshoot issues, answer questions, and provide guidance on how to use PowerShell.
42+
43+
If you think that you found a bug, you can file an issue on [GitHub][16]. The PowerShell team can't
44+
provide support through GitHub, but they welcome bug reports. The [community support][04] page
45+
provides links to the most popular community support channels.
3046

3147
## Supported platforms
3248

33-
PowerShell runs on multiple operating systems (OS) and processor architectures. For support, the
49+
PowerShell runs on multiple operating systems (OS) and processor architecture platforms. The
3450
platform must meet the following criteria:
3551

3652
- The target platform (OS version and processor architecture) is supported by .NET.
53+
- Microsoft has tested and approved PowerShell on the target platform.
3754
- The OS version is supported by the distributor for at least one year.
3855
- The OS version isn't an interim release or equivalent.
3956
- The OS version is currently supported by the distributor.
40-
- Microsoft has tested and approved PowerShell on the target platform.
4157

4258
Support for PowerShell ends when either of the following conditions are met:
4359

@@ -72,13 +88,13 @@ continue receiving updates and support.
7288

7389
[!INCLUDE [Ubuntu support](../../includes/ubuntu-support.md)]
7490

75-
## Windows PowerShell Compatibility
91+
### Support for PowerShell modules
7692

7793
The support lifecycle for PowerShell doesn't cover modules that ship outside of the PowerShell
7894
release package. For example, using the `ActiveDirectory` module that ships as part of Windows
7995
Server is supported under the [Windows Support Lifecycle][01].
8096

81-
## Experimental features
97+
## Support for experimental features
8298

8399
[Experimental features][05] aren't intended to be used in production environments. We appreciate
84100
feedback on experimental features and we provide best-effort support for them.
@@ -89,27 +105,9 @@ PowerShell is released under the [MIT license][15]. Under this license, and with
89105
agreement, users are limited to [community support][04]. With community support, Microsoft makes no
90106
guarantees of responsiveness or fixes.
91107

92-
## Getting support
93-
94-
Support for PowerShell is provided on a best-effort basis. Support for Windows PowerShell 5.1 is
95-
provided through Windows support channels. You can use the standard paid support channels to get
96-
support for PowerShell.
97-
98-
- [Support for business][18]
99-
- [Contact support][17]
100-
101-
There are many free support options available from the PowerShell community. The most active
102-
community support channels are available through **Discord** or **Slack**. The discussion channels
103-
are mirrored on both platforms, so you can choose the platform that you prefer. These channels can
104-
help you troubleshoot issues, answer questions, and provide guidance on how to use PowerShell.
105-
106-
If you think that you found a bug, you can file an issue on [GitHub][16]. The PowerShell team can't
107-
provide support through GitHub, but they welcome bug reports. The [community support][04] page
108-
provides links to the most popular community support channels.
109-
110108
## PowerShell end-of-support dates
111109

112-
The PowerShell support lifecycle is tied to the [support lifecycle of .NET][06]. The following table
110+
The PowerShell support lifecycle follows the [support lifecycle of .NET][06]. The following table
113111
lists the end-of-support dates for the current versions of PowerShell:
114112

115113
| Version | Release Date | End-of-support |

0 commit comments

Comments
 (0)