# Need for a PowerShell solution?

**URL:** <https://forums.powershell.org/t/need-for-a-powershell-solution/25379>\
**Category:** Uncategorized\
**Created:** [January 28, 2025, 2:36pm UTC](https://forums.powershell.org/t/need-for-a-powershell-solution/25379 "2025-01-28T14:36:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bamerto22](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@bamerto22](https://forums.powershell.org/u/bamerto22)\
**Post date:** [January 28, 2025, 2:36pm UTC](https://forums.powershell.org/t/need-for-a-powershell-solution/25379/1 "2025-01-28T14:36:35Z")

</div>

I have a software company, and we have been doing more and more work with Microsoft integrations. Working with many of our customers, it seems there may be a need for a good enterprise-grade PowerShell solution to provide the following:

- Central and secure repository for PowerShell scripts with versioning and change tracking.​
- Ability to support variables to reference internal and external data sources in the script.​
- Publish scripts as user-friendly web forms with roles-based access in a secure self-service portal.​
- Create PowerShell-driven workflows with approvals.​
- Convert scripts into an API service to integrate with other applications in the organization.​
- Schedule PowerShell scripts to run with status notifications. ​
- Track and report on executed PowerShell scripts to meet compliance or audit requirements.​

I figure there is no better place to get an opinion from the experts who live and breathe PS all day. If you don’t mind taking a moment, please let me know if you see any value or if I am wasting my time. Thanks.

---

<div class="post-metadata">

**Author:** ![neemobeer](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/neemobeer/32/4087_2.png) [@neemobeer](https://forums.powershell.org/u/neemobeer)\
**Post date:** [January 28, 2025, 2:46pm UTC](https://forums.powershell.org/t/need-for-a-powershell-solution/25379/2 "2025-01-28T14:46:33Z")

</div>

90% of this could be done in MECM

---

<div class="post-metadata">

**Author:** ![matt-bloomfield](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@matt-bloomfield](https://forums.powershell.org/u/matt-bloomfield)\
**Post date:** [January 28, 2025, 4:00pm UTC](https://forums.powershell.org/t/need-for-a-powershell-solution/25379/3 "2025-01-28T16:00:22Z")

</div>

PowerShell Universal does all that except native versioning and change tracking, but Git integration is easy to set up.

> **[PowerShell Universal | PowerShell Universal](https://www.powershelluniversal.com/)**
>
> The ultimate command center for your PowerShell environment.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\
**Post date:** [February 27, 2025, 4:00pm UTC](https://forums.powershell.org/t/need-for-a-powershell-solution/25379/4 "2025-02-27T16:00:59Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.