<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on PowerShell Today</title>
    <link>https://powershell.today/post/</link>
    <description>Recent content in Posts on PowerShell Today</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 06 Apr 2026 19:47:28 +0200</lastBuildDate>
    <atom:link href="https://powershell.today/post/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Graph Api, Batch Like You Mean It</title>
      <link>https://powershell.today/2026/04/graph-api-batch-like-you-mean-it/</link>
      <pubDate>Sun, 05 Apr 2026 17:01:42 +0000</pubDate>
      <guid>https://powershell.today/2026/04/graph-api-batch-like-you-mean-it/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve all been there. You open the fridge, grab the milk, walk back to your desk, realize you also need juice, walk back to the fridge, grab the juice, sit down again - and then remember the eggs. It&amp;rsquo;s exhausting, and it&amp;rsquo;s exactly what most Graph API scripts do under the hood.&lt;/p&gt;&#xA;&lt;p&gt;This post is about breaking that habit.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-one-item-shopping-trip-problem&#34;&gt;The One-Item Shopping Trip Problem&lt;/h2&gt;&#xA;&lt;p&gt;Imagine you need to check the license status of 50 users in your tenant. The naive approach looks something like this:&lt;/p&gt;</description>
    </item>
    <item>
      <title>idPowerToys Conditional Access Documenter - Manual generation Helper</title>
      <link>https://powershell.today/2023/06/idpowertoys-conditional-access-documenter-manual-generation-helper/</link>
      <pubDate>Wed, 21 Jun 2023 00:00:00 +0000</pubDate>
      <guid>https://powershell.today/2023/06/idpowertoys-conditional-access-documenter-manual-generation-helper/</guid>
      <description>&lt;p&gt;When it comes to auditing conditional access policies, the IdPowerToys&amp;rsquo; Conditional Access Documenter is a powerful tool. However, the app-consent requirement often hinders its usability by presenting reports filled with GUIDs instead of user-friendly display names. In this blog post, I&amp;rsquo;ll introduce you to idPowerToysCaDocumentHelper.ps1, a versatile PowerShell script that resolves this issue. Join me as we explore how this script enhances the Conditional Access Documenter, making your auditing process more efficient and intuitive.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New (diagrams.net) diagram</title>
      <link>https://powershell.today/2022/02/new-diagrams.net-diagram/</link>
      <pubDate>Sun, 13 Feb 2022 00:00:00 +0000</pubDate>
      <guid>https://powershell.today/2022/02/new-diagrams.net-diagram/</guid>
      <description>&lt;p&gt;Who likes to document? And who likes to keep theses documents updated?&lt;/p&gt;&#xA;&lt;p&gt;Maybe not me, but sometimes documenting is necessary. So why not automate it?&lt;/p&gt;</description>
    </item>
    <item>
      <title>New-Chunks</title>
      <link>https://powershell.today/2021/04/new-chunks/</link>
      <pubDate>Mon, 26 Apr 2021 00:00:00 +0000</pubDate>
      <guid>https://powershell.today/2021/04/new-chunks/</guid>
      <description>&lt;p&gt;Small function for splitting an array or hashtable into smaller chunks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
