PPCC 2026 agent demos need a process owner in the room
Microsoft's PPCC 2026 preview asks attendees to bring one process. The stage agent will work either way. What decides the pilot is who owns that process.
Microsoft / Product coverage
Power Platform
Source-linked reporting organized by product, platform, and the topics that connect them.
Latest coverage
Match each Dynamics 365 planning decision to a roadmap channel
Microsoft's AI at Work roadmap, Message Center, and Learn each answer a different planning question. Here is which channel each decision belongs to.
PPCC 2026's procurement example gets the approval step right
Microsoft's PPCC 2026 procurement example sends only higher-risk exceptions to a person. Most approval steps in a live tenant would fail that test.
PPCC 2026's procurement agent needs one record it writes to
Microsoft's PPCC 2026 preview runs a procurement request through Copilot, an agent, a workflow, and a reviewer. We'd ask which Dataverse row holds the trace.
One Microsoft roadmap still needs a release owner in your tenant
Microsoft's always-on AI at Work roadmap removes the wave date that used to force a review. Someone in your tenant now has to own that date.
AI at Work roadmap and Message Center answer different questions
Microsoft's August 25 post keeps public roadmap items and tenant change notices in separate channels. Someone on your team has to join them.
Getting your team ready for the AI at Work roadmap switch
Microsoft retires Release Planner on November 15, 2026. What admins and architects should export, rebookmark, and reschedule before that date.
Analysis and architecture
What an unused license actually costs you
An unused seat still gets billed. Cross usage logs against the assignment list, flag the quiet accounts, and reclaim seats before renewal locks the price in.
Map the Power Platform and SAP flows before the roadmap
Before a Power Platform or SAP roadmap gets sequenced, list every flow it touches with a source of record, a consumer, and the person who fixes exceptions.
What a ServiceNow catalog entry owes the support desk
A catalog entry for a Power Platform flow should name who gets paged, what to check first, and who can switch it off. The design document stays where it is.
Related guides
How many Power Platform environments you actually need
A working rule for deciding which Power Platform solutions get their own dev, test, and production environments, and who approves promotion between them.
Build a Power Platform ALM pipeline makers actually use
A pipeline survives when the build takes under two minutes, test data looks real, and a maker can roll back without opening a ticket.
Governance that keeps Power Platform makers building
A fifteen-minute conversation before the first screen is built, recorded on the Dataverse solution, does more than an approval form completed after go-live.
How to read a licensing change before finance does
The four numbers a platform owner needs before a Power Platform, Dynamics 365, or Agentforce repackaging note gets forwarded to finance.
A release checklist for shared Power Platform solutions
The questions a platform team should ask before a shared Power Platform solution reaches other makers, and where to keep the answers for the next owner.
Keep your Power Platform center of excellence small
A center of excellence earns its keep with office hours and a pattern library, and loses it the day it starts approving every app or owning every maker's flow.