# PowerShell Specific Collection

**URL:** <https://forum.ansible.com/t/powershell-specific-collection/45708>\
**Category:** Project Discussions\
**Tags:** powershell, windows, aap\
**Created:** [April 20, 2026, 12:55am UTC](https://forum.ansible.com/t/powershell-specific-collection/45708 "2026-04-20T00:55:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [April 20, 2026, 3:45pm UTC](https://forum.ansible.com/t/powershell-specific-collection/45708/2 "2026-04-20T15:45:17Z")

</div>

Hey @jborean

Assuming this is somewhat related to [Documentation Attributes for PowerShell versions](https://forum.ansible.com/t/documentation-attributes-for-powershell-versions/45649), right?

In my mind, it makes sense to have these modules that support PowerShell 5+ (working on both Windows and POSIX) into a separate collection given they’re not Windows specific anymore. However, at the same time as you rightly point out, it has maintenance and UX downsides. It would also mean `ansible.powershell` would need to be certified separately to, adding to the maintenance.

I could help with maintenance if needed. I have experience with writing quite a bit of PowerShell too. Let me know if I can help 🙂

---

_[View the full topic](https://forum.ansible.com/t/powershell-specific-collection/45708)._