PSResourceGet is evolving toward secure-by-default enterprise package management for PowerShell. Key best practices include treating PowerShell Gallery as an untrusted discovery source, using Microsoft Artifact Registry (MAR) for Microsoft-owned modules, and routing all production installs through a private, vetted enterprise feed. PSResourceGet 1.3-preview1 is now available with MAR as a default registered repository, concurrent (parallel) install support, and DSC V3 resource integration. The roadmap also includes ORAS library support for broader OCI registry compatibility, cross-repository dependency handling, and dropping Windows PowerShell support to reduce complexity and enable new features.
Table of contents
PSResourceGet Best Practices Copy linkExample Enterprise Package Flow Copy linkRoadmap for PSResourceGet 1.3 (vNext) Copy linkWhy This Matters Copy linkSort: