PowerShell Team

Automating the world one-liner at a time…

Announcing General Availability of the Windows Compatibility Module 1.0.0

Announcing General Availability of the Windows Compatibility Module 1.0.0 The Windows Compatibility module () is a PowerShell module that lets PowerShell Core 6 scripts access Windows PowerShell modules that are not yet natively available on PowerShell Core. (Note: the list of unavailable commands is getting smaller with each new release of...

Announcing General Availability of the Windows Compatibility Module 1.0.0

The Windows Compatibility module () is a PowerShell module that lets PowerShell Core 6 scripts access Windows PowerShell modules that are not yet natively available on PowerShell Core. (Note: the list of unavailable commands is getting smaller with each new release of PowerShell Core. This module is just for things aren't natively supported ...

Desired State Configuration (DSC) Planning Update – September 2018

2018 has been the most active year ever for the DSC community. We are taking on major new areas of work in Azure, and have made significant progress in development of the new DSC platform. In this Planning Update for DSC, I want to cover these topics in detail and share major changes to the timing of our Open Source plans for the DSC platform.

PowerShell Module Function Export in Constrained Language

PowerShell Module Exporting Functions in Constrained Language PowerShell offers a number of ways to expose functions in a script module. But some options have serious performance or security drawbacks. In this blog I describe these issues and provide simple guidance for creating performant and secure script modules. Look for a module soon in ...

PowerShell Standard Library: Build single module that works across Windows PowerShell and PowerShell Core

This is the first of a series of blog posts that will help you take advantage of a new NuGet package PowerShellStandard Library 5.1.0. This package allows developers to create modules that are portable between Windows PowerShell 5.1 and PowerShell Core 6.0. This means that you can create PowerShell modules that run on Windows, Linux, and ...

PowerShell Injection Hunter: Security Auditing for PowerShell Scripts

At the DEFCON security conference last year, we presented the session: "Get $pwnd: Attacking Battle Hardened Windows Server". In this talk, we went through some of the incredibly powerful ways that administrators can secure their high-value systems (for example, Just Enough Administration) and also dove into some of the mistakes that administrators sometimes make when exposing their PowerShell code to an attacker. The most common form of mistake is script injection, where a script author takes a parameter value (supplied by an attacker) and runs it in a trusted context (such as a function exposed in a Just Enough Administration endpoint).