<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Batching on PowerShell Today</title>
    <link>https://powershell.today/tags/batching/</link>
    <description>Recent content in Batching 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/tags/batching/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>
  </channel>
</rss>
