Microsoft drew a hard line in July 2025: personal Microsoft accounts can no longer sign into the Power Automate cloud service. The rule only applies to the web portal and mobile apps—the desktop automation tool still works with Outlook.com and Gmail credentials—but for the millions who use cloud flows to connect SharePoint, Outlook, and Teams, it now requires a work or school address. This change, combined with the rollout of AI-assisted development and stricter governance controls, reshapes who can build what in Power Automate.
What Changed: Account Gates and Platform Updates
The most concrete shift is the enforcement of work or school account requirements for cloud services. After July 26, 2025, anyone attempting to sign into make.powerautomate.com with an @outlook.com, @gmail.com, or other personal email will be blocked. The mobile apps on iOS and Android follow the same rule. Microsoft’s reasoning is clear: cloud flows often interact with enterprise tenants, and tying them to organizational identities simplifies compliance and lifecycle management.
However, Power Automate for desktop remains an exception. The desktop application, which automates Windows UI and web tasks, continues to accept personal Microsoft accounts. This means a user can still record and run desktop-based RPA jobs using a free Outlook.com login, but they cannot manage those flows through the cloud portal, trigger them from online events, or access mobile dashboards without a work or school identity.
Beyond the account gates, several platform updates landed in 2026. Copilot, Microsoft’s AI assistant, is now integrated into the cloud flow designer, generating entire automations from natural language descriptions. An administrator can disable it, but for organizations that enable Copilot, makers can type “When a high-priority item is added to the Facilities SharePoint list, post an adaptive card in Teams and email the technician” and receive a draft flow in seconds.
Governance also tightened. Microsoft is rolling out advanced connector policies that operate on an allowlist model, where administrators explicitly permit specific connectors and actions instead of merely grouping them into business/non-business categories. These policies can block a maker from even selecting a restricted action during design time, a level of control previously unavailable. As of 2026, they are still in rollout and may not cover every connector type or builder environment.
On the desktop side, version 2.55 and later require the .NET 8 runtime, and the standalone MSI installer attempts to fetch it automatically, but locked-down enterprise machines may need manual packaging. Microsoft also introduced automatic updates for the standalone installer in April 2025, reducing the patch burden for some organizations.
What the Changes Mean for Different Users
The impact of these shifts varies wildly depending on who you are.
Home and personal users
If you’ve been using cloud flows with a free personal account—say, to save email attachments to OneDrive or post to Twitter—those automations stopped working after July 2025. You can’t even sign in to the portal to export them. Your only remaining path is to obtain a work or school account (unlikely for hobbyists) or migrate the logic to a local process using Power Automate for desktop, which doesn’t require any subscription for basic attended automation. That’s fine for tasks on your own Windows PC, but you lose cloud connectivity and mobile triggers.
Business users and citizen developers
For corporate employees, the account change is mostly transparent—they already sign in with Azure AD/Entra ID. But many organizations previously allowed employees to use personal accounts for evaluation or side projects; now those experiments won’t work. The bigger shift is Copilot: if your tenant enables it, you can prototype flows in seconds, but you must still review the output carefully. The AI can misconfigure recipients, overlook data types, or connect to the wrong environment. Treat generated flows as first drafts.
IT administrators
Admins face a triple challenge: enforcing account alignment, managing the new connector policies, and keeping desktop infrastructure current. Advanced connector policies are particularly significant. The classic data loss prevention (DLP) model groups connectors into business, non-business, and blocked bins, but it doesn’t control at the action level. The new policies let you say “allow the SharePoint connector, but block the ‘Delete item’ action.” That precision is welcome, but it requires testing, as not all maker portals may respect the policies yet.
For desktop automation, the .NET 8 prerequisite and automatic updates for the standalone installer demand attention. Machines that run unattended flows—often virtual machines or dedicated terminals—must be patched or risk dependency failures. The choice between Store and MSI installers is now more nuanced: the Store version doesn’t require admin rights and auto-updates, but the MSI offers machine-runtime components needed for cloud-triggered unattended automation. A hybrid approach, where the Store app coexists with an MSI-installed runtime, is supported and can simplify updates.
Developers and solution architects
Power Automate’s environment model now demands discipline. Every cloud flow lives in a Power Platform environment, and creating one in the wrong environment can cause missing connections or governance restrictions. Use solutions to package flows with connection references and environment variables, enabling clean dev-test-prod promotion. Child flows are a mature way to centralize logging, notifications, or validation logic so you don’t replicate it across dozens of automations.
How We Got Here: From Flow to Power Automate
Power Automate originated as Microsoft Flow in 2016, a simple trigger-and-action service for connecting Office 365 apps. Microsoft rebranded it in 2019, then accelerated its evolution by acquiring robotic process automation capabilities and integrating them into the desktop client. Process mining, AI Builder, and deep Teams integration followed, turning what was once a glue-tool into a full automation platform.
The account tightening is part of Microsoft’s broader push to entangle Power Platform with organizational identity management. As flows increasingly touch sensitive data in SharePoint, Dataverse, and third-party services, tying them to corporate identities allows for auditing, conditional access, and compliance controls that personal accounts can’t offer. The deprecation was announced well in advance, but many casual users missed the deadline.
What to Do Right Now: Practical Steps
If you used a personal account for cloud flows
Accept that cloud flows are gone unless you can switch to a work or school account. If possible, recreate the logic in Power Automate for desktop. For example, if a flow moved attachments from Gmail to a local folder, you can build a desktop flow that opens the browser, logs in, and downloads them. It’s more brittle but functional.
If you manage a team or department
Audit all existing flows for owner identity. A flow tied to an individual who leaves the company can stop working. Assign co-owners, use service accounts where appropriate, and document each flow’s purpose and support contact. Start moving business-critical automations into solutions.
If you’re an admin
Roll out advanced connector policies in a test environment first. Communicate the changes because a maker who suddenly can’t select a connector may think Power Automate is broken. Plan the .NET 8 deployment and decide on a desktop installer strategy: for VMs running unattended RPA, the MSI with automatic updates enabled is likely best; for knowledge workers building personal productivity automations, the Store version works.
If you’re a new user
Start with a cloud flow if the task involves online services. Use a template or Copilot to get a draft quickly, but then manually inspect every action: verify the trigger scope, connection identity, condition logic, and error handling. Avoid using Excel as a database; use SharePoint lists or Dataverse for anything shared.
Outlook: AI and Governance Will Define the Next Year
Copilot will improve, but the real story for 2026 is governance. Advanced connector policies are just the beginning. Microsoft’s vision ties Power Automate into a larger “agent” strategy where automated processes feed into autonomous AI agents that make decisions. For that to be trustworthy, identity and access control must be airtight.
Desktop automation will not fade away. Many organizations still run custom Windows applications that lack APIs, and AI-based computer-use models may eventually make UI automation more resilient. In the meantime, desktop flows remain the only bridge to legacy systems, and Microsoft continues to invest in their reliability, including the new .NET 8 baseline and better installer management.
For everyday Windows users, the message is clear: Power Automate is no longer a casual playground. Even a small flow can touch business data, and Microsoft is treating it accordingly. The tools are more capable than ever, but they demand the same respect you’d give any line-of-business application. Build carefully, own what you build, and when the platform changes—as it just did—adapt with purpose.