<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Modules on PowerShell.org - Welcome Automaters!</title><link>https://powershell.org/tags/modules/</link><description>Recent content in Modules on PowerShell.org - Welcome Automaters!</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 15 Sep 2023 16:21:15 +0000</lastBuildDate><atom:link href="https://powershell.org/tags/modules/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Graph PowerShell Module: Getting Started Guide</title><link>https://powershell.org/articles/2023-09-15-microsoft-graph-powershell-module-getting-started-guide/</link><pubDate>Fri, 15 Sep 2023 16:21:15 +0000</pubDate><guid>https://powershell.org/articles/2023-09-15-microsoft-graph-powershell-module-getting-started-guide/</guid><description>&lt;h1 id="microsoft-graph-powershell-module-getting-started-guide"&gt;Microsoft Graph PowerShell Module: Getting Started Guide&lt;/h1&gt;
&lt;p&gt;by Jeff Brown&lt;/p&gt;
&lt;p&gt;Microsoft is retiring the Azure AD Graph API sometime after June 30, 2023 (&lt;a href="https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/azure-ad-change-management-simplified/ba-p/2967456"&gt;announcement&lt;/a&gt;). This retirement includes the Azure AD PowerShell module. In its place, Microsoft has released the Microsoft Graph PowerShell module. The Microsoft Graph PowerShell module is the next-generation way of managing Microsoft cloud services using PowerShell. If you have used MSOnline or Azure AD PowerShell in the past, you&amp;rsquo;ll need to read on to learn about this new module.&lt;/p&gt;</description></item><item><title>Writing Your Own PowerShell Functions / Cmdlets</title><link>https://powershell.org/articles/2020-11-05-writing-your-own-powershell-functions-cmdlets/</link><pubDate>Thu, 05 Nov 2020 18:53:35 +0000</pubDate><guid>https://powershell.org/articles/2020-11-05-writing-your-own-powershell-functions-cmdlets/</guid><description>&lt;p&gt;This article is an attempt at describing some of my thought process when building functions. By functions I mean a command that you can execute after importing a module. I am not referring to running a script that accepts parameters and input. Having a task to complete for a function is of course the first objective. Once an idea is in mind I like to write as much as the Help section first as possible as this helps me outline and plan what I am going to do.&lt;/p&gt;</description></item><item><title>Creating a PowerShell Module to Improve Your Code</title><link>https://powershell.org/articles/2020-07-27-creating-a-powershell-module-to-improve-your-code/</link><pubDate>Mon, 27 Jul 2020 18:24:52 +0000</pubDate><guid>https://powershell.org/articles/2020-07-27-creating-a-powershell-module-to-improve-your-code/</guid><description>&lt;p&gt;Do you have PowerShell code that you reuse in your scripts over and over? Do you have server names hard coded in variables? Are you using a text file or CSV file to import server names? Do you find yourself only utilizing one server out of a cluster of servers to make your PowerShell commands? These are the questions I asked myself and the answer used to be YES. In this post, I will go over how you can store your infrastructure server information in a SQL database and call that data from a custom PowerShell module. By utilizing this method, you can expect the below benefits:&lt;/p&gt;</description></item><item><title>A New Home for Plaster</title><link>https://powershell.org/articles/2020-06-16-a-new-home-for-plaster/</link><pubDate>Tue, 16 Jun 2020 21:17:21 +0000</pubDate><guid>https://powershell.org/articles/2020-06-16-a-new-home-for-plaster/</guid><description>&lt;p&gt;&lt;img src="https://powershell.org/wp-content/uploads/2020/06/scaffold-thumb.jpg" alt=""&gt;Some of you may be familiar with the Plaster PowerShell module. This slick tool lets you build out a new module in seconds. Actually, Plaster can be used to scaffold a framework for any type of project. You can install the &lt;a href="https://www.powershellgallery.com/packages/Plaster/1.1.3"&gt;current version from the PowerShell Gallery.&lt;/a&gt; However, the project has been in limbo for a while with no updates or progress. After discussions with the PowerShell Team about the module, a decision was made to transfer ownership to the PowerShell community. We&amp;rsquo;re happy to report that the Plaster repository is now under the auspices of PowerShell.org. The GitHub repo, including pull requests and issues, can now be found at &lt;a href="https://github.com/PowerShellOrg/Plaster"&gt;https://github.com/PowerShellOrg/Plaster&lt;/a&gt;.&lt;br&gt;
It will take some time to get re-organized and work through the backlog of issues and pull requests. Although it is possible that we&amp;rsquo;ll simply zero out things like pull requests and start with a fresh slate. The basic functionality of the module should work just fine in its current state. Enough members of the PowerShell community recognize the value in the Plaster module which is why this transfer was made.&lt;br&gt;
And frankly, this is one of PowerShell.org&amp;rsquo;s primary purposes: to serve the community. In this case, Microsoft had a languishing asset that needed more attention than what they could provide. Which is exactly where PowerShell.org fits in. We can step in providing the resources and in the end contribute back to the community. A big thank you to Steve Lee at Microsoft for making this possible.&lt;/p&gt;</description></item></channel></rss>