Courses, Blueprints, Briefings, Blockers, and Pulse — together in last-update order.
Collab365 Team
Microsoft removes the Power Virtual Agents help chatbot from every Power Automate maker-portal page on 9 September 2026. The lower-left chat entry disappears; the upper-right Help menu stays the supported route for guidance and support requests. Maker habits and internal guides…
Collab365 Team
Microsoft will let attended Power Automate desktop flows use canvas apps as interactive forms, passing structured inputs and outputs without screen scraping. Form-heavy attended automations gain a more maintainable UI pattern once the feature reaches general availability.
Collab365 Team
Microsoft changed SharePoint thumbnail data from 1 September 2026. Power Automate flows that pass thumbnail URLs into later actions can fail. Makers should use Get file thumbnail and test with a real file.
Collab365 Team
Microsoft stops wave-based Release Plans for Power Platform from September 2026. Features shift to a continuous AI at Work roadmap; Release Planner retires in November. Makers need ongoing filters and checks instead of twice-yearly wave lists.
Collab365 Team
From 15 September 2026, failed unattended desktop flow videos land in Dataverse and open from Power Automate portal run details, so support no longer needs host-machine recordings for UI failures.
Collab365 Team
Microsoft’s 2025 wave 2 plan for Power Automate covers approvals, run monitoring, Copilot flow help, and connectors with staggered GA into early 2026. Classic release plans stop after September 2026; access still depends on region, licence, and admin enablement.
Collab365 Team
Microsoft will stop publishing separate Power Automate release plans from September. New capability announcements move to the AI at Work roadmap. Flow makers should add that roadmap to pre-build checks alongside docs and environment tests.
Collab365 Team
Copilot can draft a plausible Power Automate cloud flow, but save success and green connections do not prove trigger, dynamic fields, recipients or connection identity match the business process. A first-run safety gate with test data and a run-revise-escalate decision is…
Collab365 Team
Copilot can draft a Power Automate flow quickly, but the maker still needs to prove the trigger, fields, connections, recipients, and first-run effects are safe before live use.
Collab365 Team
Copilot-built Power Automate flows can send messages, update records, or trigger approvals. This checklist covers trigger, actions, dynamic content, connections, and test data to confirm the draft matches the intended process before first-run sign-off.
Collab365 Team
SharePoint created-or-modified triggers report connector activity, not business intent. Without field or status conditions, Power Automate flows duplicate work on system updates, concurrent edits, and permission changes.
Collab365 Team
Microsoft’s 2026 release plan lists direct scheduling for desktop flows and a flow-chart view as August public previews, with dates subject to change. Makers still need machine owners, connection checks, and tested failure paths before production use.
Collab365 Team
Microsoft sharing docs still tie Power Automate flow actions to whoever authorised each connection. Co-owners alone will not keep departmental automations alive after staff leave. Critical flows need connections under a stable shared account.
Collab365 Team
Microsoft Power Platform admin docs separate Microsoft 365 seeded Power Automate rights from Premium, Process, and RPA capacity. Seeded plans cover standard cloud connectors; premium connectors, unattended desktop, and AI Builder sit on paid paths that can block production.
Collab365 Team
Copilot Studio agent skills package a job’s instructions, scripts and templates into a zip another agent can run. A certificate PDF example shows creation via Skill Creator, upload, and why tests with missing fields reveal whether the skill asks or invents.
Collab365 Team
Microsoft shipped a Power Automate plugin for GitHub Copilot CLI and Claude Code. Makers can create, edit, run and debug cloud flows in natural language from the terminal, shortening the run-history debug loop while ownership and production controls still matter.
Platform appCollab365 Team
Three SharePoint lists, a starter onboarding template pack, five guarded Power Automate flows, and one completed fictional-hire proof for an HR or operations coordinator.
Who builds it? You build the app in the named platform, with AI coaching you through the work.
Before you start: A licence, permission to create apps, a safe test area, and sample data.
Platform appCollab365 Team
Three SharePoint lists, starter test examples, a testing reminder flow, a go-live decision flow, and one completed low-risk example.
Who builds it? You build the app in the named platform, with AI coaching you through the work.
Before you start: A licence, permission to create apps, a safe test area, and sample data.
Coming next
Live 14th Sept 2026Collab365 Team
Power Automate can send mail successfully while still failing the business test if messages leave from the maker instead of HR, finance, or support. Send As, Shared Mailbox V2, and mailbox auto-reply differ on sender identity, reply routing, permissions, and Sent Items.
Live 14th Sept 2026Collab365 Team
Power Automate flows can succeed yet still send from the maker, not the shared mailbox. Wrong Outlook action or missing Send As permissions cause bad sender identity and Sent Items in the wrong place. Correct action and Exchange rights fix it.
Live 1st Oct 2026Collab365 Team
Power Automate flows often start as team-owned tasks but later become embedded in daily operations. This checklist helps makers evaluate whether a flow remains suitable for Power Automate or requires escalation to Logic Apps based on ownership, volume, monitoring, and support…
Live 5th Oct 2026Collab365 Team
Power Automate flows built for low-volume human processes later become high-volume system integrations. Makers lack criteria to decide when ownership should shift to IT and Logic Apps.
