product news is dominated by a shift from isolated productivity features toward governed, agent-driven work: Power Platform makers are receiving stronger AI-assisted app and automation capabilities, Copilot Studio is becoming a more complete app-building platform, and Microsoft is consolidating roadmap communications around a new AI at Work destination. The business priority is clear: accelerate AI-enabled creation and collaboration while strengthening administration, lifecycle controls, data governance, and human review before automations or agents act at scale.
Top stories
- Power Platform September update: AI becomes more deeply embedded in maker workflows. Microsoft’s September feature update highlights general availability of the canvas authoring agent plugin and a model app-builder skill, enabling makers and developers to build or modify apps from natural-language requirements. The update also includes Copilot Studio agents from Power Automate, expanded AI Builder capabilities, and image support in email messages.
- Power Pages expands AI-enabled site and agent development. Key Power Pages developments include preview capabilities to add AI features to lists, ask Copilot questions in Power Pages, create an agent from a form, configure Microsoft Entra ID authentication for Power Pages Agent, and control generative-AI use for users. This points to Power Pages evolving beyond external-facing websites into a governed front end for AI-assisted customer, partner, and employee experiences.
- Copilot Studio app building gains administration and lifecycle management. Microsoft says apps built in Copilot Studio can now be produced from a description of the desired business outcome, with source control, deployment stages, and version isolation on Microsoft-hosted infrastructure. Administrators can control where users are permitted to build apps through the Microsoft 365 admin center; building and running these apps are separately metered through Copilot Credits usage-based billing.
- Power Automate focuses on desktop automation, forms, and operational visibility. September’s planned or released capabilities include integrated Power Apps forms, custom dashboard tiles, Python-script execution using current Python versions in desktop flows, local-AI-model connectivity from desktop flows, and machine and flow-utilization dashboards. Power Automate for desktop version 2609 began worldwide availability on September 17.
- Power Apps improves Dataverse access and model-driven-app productivity. September availability includes online-mode access to Dataverse for canvas apps, enhanced row summaries in model-driven apps, configurable offline profiles through a FetchXML editor, and a streamlined model-driven app header and navigation experience. Microsoft also lists direct SharePoint List integration in the new Power Apps experience and Microsoft 365 Copilot use in model-driven apps among its 2026 release-wave capabilities.
- Power Platform governance shifts from policy-only controls toward AI-quality and operational management. Microsoft lists September preview plans for AI-node evaluation, multi-grader comparison, an Agentic Center of Enablement, and faster detection of operational-health issues across Power Platform resources. The ability to move apps out of the default environment reaches general availability in September, reinforcing environment strategy as a practical governance priority.
- Microsoft is replacing traditional release waves with continuous, AI-centered roadmap communications. Beginning this month, Dynamics 365, Power Platform, and Dataverse roadmap content is moving to the AI at Work roadmap, alongside Microsoft 365, Copilot, agents, and business-applications updates. Microsoft says it will no longer publish a September 2026 Release Wave 2 announcement, with existing release plans scheduled for archival and Release Planner retirement by November 15.
- Teams news centers on frontline calling collaboration and more streamlined messaging. The Queues app for Microsoft Teams turns an existing call queue into a shared workspace where supervisors and calling representatives manage the same customer conversations. Microsoft also continues to position the new chat-and-channels experience as a simpler way to organize, navigate, and triage collaboration.
- Copilot Chat and Microsoft 365 Copilot continue moving toward richer in-context productivity assistance. Microsoft has described upcoming Copilot capabilities including in-app editing in Word, Excel, and PowerPoint; Copilot Chat experiences in Outlook that can work with email, calendar, and meeting information; and updated Copilot Notebooks that organize chats, outputs, and references around projects. For government environments, Microsoft also outlined a broader fall rollout across GCC, GCC High, and DoD, subject to the respective availability plans.
- SharePoint Online remains a foundation for AI-ready content, permissions, and developer experiences. This week’s Microsoft community agenda highlights flexible sections in SharePoint and a SharePoint Copilot application for managing site permissions directly from Copilot through SP Permissions Explorer. Microsoft also has a September 23 session planned around content readiness for AI and agents, underscoring that information architecture, permissions, and content quality remain prerequisites for reliable Copilot outcomes
- Power BI: no major standalone September 21 product announcement surfaced in the current Microsoft-focused results. The broader Power Platform and Microsoft 365 direction still affects Power BI teams: organizations are increasingly expected to combine AI-enabled application development, automation, governance, and connected data experiences rather than operate analytics in isolation. The near-term focus should be semantic-model governance, secure access to data, and readiness for AI-assisted insights.
What leaders should do
- Review Copilot Studio app-building permissions, Copilot Credits exposure, source-control expectations, and deployment-stage governance before enabling broad maker access.
- Prioritize Power Platform environment strategy: move unmanaged production apps out of the default environment, strengthen DLP policies, and establish an ownership, support, and lifecycle model
- Prepare Power Automate desktop teams to evaluate version 2609, dashboard-based utilization monitoring, local-model scenarios, and Python automation under appropriate security guardrails
- Treat SharePoint content hygiene and permissions remediation as an AI-readiness workstream, especially before enabling agents that can ground responses in organizational content.
- Track the AI at Work roadmap rather than relying solely on former twice-yearly Power Platform release-wave documents.
