The Power of Community

Since the early days of Windows PowerShell, the community around the product has grown to a large and active user base. In this article, we will look at how the community can influence future releases.

Windows PowerShell is software. Any software, in general, will always have bugs as well as the need for new features and improvements. Microsoft has a feedback channel called Microsoft Connect where customers can report bugs and provide suggestions for feedback to their software. There is a dedicated Connect website for Windows PowerShell: 


In addition to submitting your own items, you can also vote for items posted by others. Here is an example:


Another feedback opportunity you should know about Windows PowerShell is regarding the help system. Since version 3, the help system is updatable (Update-Help), which makes it possible for Microsoft to update the help files with more information as well as correcting errors on a regular basis. To report errors or suggestions for the help system, you can use the e-mail alias write-help (at) microsoft (dot) com.


There are also other feedback channels available for PowerShell-related technologies such as Azure Automation and Service Management Automation (SMA). Microsoft Azure is using UserVoice, a software-as-a-service provider of customer support tools. Here is a few categories from the Azure channel at UserVoice relevant to PowerShell:


ISESteroids is another product leveraging UserVoice. I recently submitted an idea for a new feature in ISESteroids regarding region expansion, and I was positively surprised when I saw the feature implemented in the latest preview only 2 days later.


There are also a number of Microsoft projects on GitHub. OneGet–a unified package management module to be released in PowerShell 5.0–is a great example. In the OneGet project on GitHub, we can submit issues and pull requests among other things.

Another example is the Hardware Management Module, a PowerShell module for managing hardware out-of-band via the WS-Man protocol, which was released on GitHub a few months ago.


The last feedback channel to mention in this article is going to conferences where you can meet and talk directly to product team members in order to provide feedback. Microsoft TechEd (rebranded to Microsoft Ignite going forward) and the PowerShell Summit are great examples of such conferences.

About the author: Jan Egil Ring

Jan Egil works as a Lead Architect at Crayon, Norway. He mainly works with automation, and has a strong passion for PowerShell. He has been working with Microsoft infrastructure products such as Windows Server & System Center since the early 2000s. In the recent years the focus has been more and more related to cloud technologies in Microsoft Azure and hybrid environments. He is a multiple-year recipient of Microsoft Most Valuable Professional Award for his contributions in the Windows PowerShell and Cloud & Datacenter Management technical communities. He speaks regularly at user groups and conferences, such as Nordic Infrastructure Conference (NIC), PowerShell Conference Europe and PowerShell Summit. He is a co-organizer of Azure User Group Norway as well as the MTUG (Microsoft Technology User Group) Script Club which focuses mainly on PowerShell. You can follow him on Twitter @JanEgilRing.

Related Posts