PowerShell Universal Community Call - July 2026

Meeting Notes

• I talked about the 2026.2.2 and the upcoming 2026.2.3 a bit.
• I did a demo of the WinForms to PSU App AI Skill

Pester Support

• Attendee described environment of 300+ scripts with a small team and heavy reliance on Pester
• Desires something like a CI\CD pipeline environment without using GitHub Actions
• Pain points
  • Overall usability (not very mature)
  • Basic output - No much to gain running in PSU
• Desired functionality
  • Some way to tie tests to feature groups, resource groups, individual resources (API endpoints, apps, etc)
  • Triggers for pester tests when code changes
  • Nightly runs of Pester tests
  • Triggers for failed test runs
• Discussed best ways to handle test assignment
  • Pester\PSU Tags - Possible but could get messy
  • Naming Conventions - Maybe easy to do but also could cause unexpected side effects
  • Test Manifest - Most rigid but maybe easier to support

High Availability

• Question around general success of high availability
• Attendee mentioned success with Docker Compose, PSU and PostgreSQL
• Some discussion around the best database to use
  • Similar performance for PG and MS SQL
  • MS SQL used more often and typically more of a focus of the dev team
  • PG starting to be used more and is getting some more attention from dev team
• An attendee mentioned that PSU does not survive database downtime well
• Talked about how Notifications are coming to the trigger feature to get info about admin console notifications

Rate Limiting Problems - Captcha issue

• Rate limiting and captcha configuration can be hard because not all internal URLs are well documented
• Custom APIs should be rate limited and internal URLs should be allowed through
  • Blazor Hub
  • Dashboard Hub
  • Internal Components URL
• Easier configuration of PSU's built in rate limiting for custom APIs

External\Internet Facing PSU Instances

• There was a question around how users expose PSU to external networks
• Attendee described the use of Azure API Management to surface some APIs to external services

Skills

• An attendee is looking for a skill to create a custom App components
• We have an internal experimentation around this that we can formalize and publish

New-UDUpload

• Multifile support is desired
• 2gb limit is a blocker

Workflow

• Not enough there. Needs more features
• Not everyone had played with it yet but will give feedback when more time allows
• Approvals would be awesome
• Approvals via slackops is ideal

Agents

• We are building PSU support in devolutions-agent (open source)
• We are taking advantage of PSRemoting to be able to service event hubs-style features as well as run jobs