
Microsoft MVP (Business Application & Data Platform) | Microsoft Certified Trainer (MCT) | Microsoft SharePoint & Power Platform Practice Lead | Power BI Specialist | Blogger | YouTuber | Trainer
The newsroom reviewed a YouTube video by Dhruvin Shah [MVP] that outlines the June 2026 Power Platform updates. The video walks viewers through six major rollouts and explains how each change affects makers, developers, and admins. Importantly, the presenter demonstrates new capabilities while noting what administrators must consider when they adopt these changes. Consequently, this coverage aims to give a concise, objective summary for readers who need the essentials.
First, the video highlights Closed-Loop Learning on the Power Apps MCP server, where agents learn from user corrections and store those corrections as structured memory. Dhruvin explains a two-agent model — a worker and a supervisor — that together enable automatic corrections and more reliable agent behavior. Moreover, he notes that the feature starts with data-entry tools but is positioned to expand to other automation scenarios.
However, closed-loop learning brings tradeoffs. On one hand, automation improves over time and reduces repetitive fixes, which speeds development and lowers manual effort. On the other hand, organizations must manage training data quality and guardrails because incorrect corrections could propagate unintended behaviors; therefore, governance and review processes remain essential.
Next, the presenter covers Advanced Connector Policies (ACP), which replace the classic Business / Non-Business / Blocked DLP model with a more granular approach. Dhruvin points out that ACP uses environment groups and a default-deny allowlist to give admins finer control over connector actions and what agents can call, and he emphasizes that ACP is now generally available. Additionally, the video shows how connector visibility is expanding in the Power Platform admin center and inventory APIs.
The governance changes offer clear benefits but require careful balancing. For example, default-deny policies reduce risk exposure and help enforce least privilege, yet they add operational overhead when teams must request exceptions or maintain allowlists. Therefore, organizations must weigh stricter control against potential friction for makers and weigh investment in governance tooling against the value of reduced blast radius.
Dhruvin also notes that desktop flow versioning is generally available and retains up to 12 months of version history, including side-by-side file comparisons of subflows, actions, variables, UI elements, and images. Furthermore, the video demonstrates a preview action that lets a Power Automate desktop flow launch a Power App directly via the Run a Power App action. These updates aim to improve traceability and enable tighter integration between desktop automation and canvas or model-driven apps.
Still, tighter integration creates design choices for teams. While versioning and app-launching simplify debugging and orchestration, they can also create stronger dependencies between desktop and cloud components. Consequently, teams must decide whether to favor modular, loosely coupled designs for maintainability or tighter coupling for simpler end-to-end automation and faster delivery.
The video outlines expanded inventory features in the Power Platform admin center, where connector and connector-operation visibility is rolling out in public preview across many asset types. Dhruvin shows that this inventory will surface connectors used by canvas apps, model-driven apps, cloud flows, and agents created in Copilot Studio or Microsoft 365 Copilot Agent Builder. In addition, admins can query the same inventory through platform connectors and APIs to support audits and impact analysis.
Greater visibility helps administrators assess risk and plan remediation, but it also increases the scale of data teams must process. As a result, organizations should plan how to filter and analyze inventory results and invest in tooling that converts raw inventory into actionable insights. In short, visibility is only valuable when paired with policies and processes that act on findings.
Throughout the video, Dhruvin stresses practical tradeoffs: the balance between enabling rapid innovation for makers and maintaining tight governance for enterprise security. He suggests that while AI-driven features and agent learning boost productivity, they require new governance patterns and testing strategies. Likewise, ACP and inventory features strengthen control but add administrative tasks that teams must budget for.
Finally, the presenter recommends that organizations pilot the new features in controlled environments and update operational runbooks to reflect versioning, connector policies, and agent training workflows. By doing so, teams can adopt capabilities incrementally, measure benefits, and address challenges such as data hygiene, policy exceptions, and cross-team coordination. Overall, the video offers actionable insight for both implementers and decision-makers while acknowledging the real tradeoffs that come with enterprise adoption.
Power Platform June 2026 updates, Microsoft Power Platform June 2026 features, Power Apps June 2026 update, Power Automate June 2026 changes, Power BI June 2026 release, Copilot Power Platform June 2026, Power Platform admin updates June 2026, Power Platform pricing June 2026