Power Platform: September 18, 2026
Tooling week. PAC CLI gained more than 200 commands generated straight from the Power Platform API, Foundry got a one-command dev setup, and the Copilot Studio team wrote up how they moved their cache to Azure Managed Redis. Matthew Devaney also published a multi-agent pattern for Copilot Studio.
Auto-generated Power Platform API commands in PAC CLI
PAC CLI has a public preview of command groups generated from the monthly Power Platform API spec: 15 new namespaces and over 200 commands for licensing, governance, environment lifecycle, Copilot Studio and workflow agents. If an endpoint ships before the CLI catches up, pac auth token gives you a bearer token to call it directly.
Foundry Dev Pack bundles the setup
Foundry Dev Pack is an installer for a Foundry development machine. One winget or Homebrew command pulls Azure CLI, Azure Developer CLI, the Foundry extension, the VS Code extensions and the coding agent skills. Handy for a new laptop or a CI image; you stop keeping the prerequisite list by hand.
What Copilot Studio learned moving to Azure Managed Redis
The Copilot Studio team wrote up their move from Azure Cache for Redis Classic to Azure Managed Redis. They cut redundant cache writes and put an in-memory L1 check in front of distributed lookups, and cache server load went from peaks of 95 percent to 15 to 40 percent. Worth reading if you run anything chatty against a shared cache, agents or connectors included.
Multi-agent workflows in Copilot Studio
Matthew Devaney's guide splits one job across several Copilot Studio agents running in parallel. The walkthrough combines deterministic JSON rule evaluation with document extraction and SharePoint knowledge retrieval. He reports faster runs and more accurate output than a single agent with one long prompt.