Microsoft 365 Copilot Chat: Flow Builder now included in Copilot license

Flow Builder, a Microsoft 365 Copilot agent for creating automation flows via natural language, is now included in the $30 Copilot license starting September 29, 2025. It requires no extra cost, is ON by default, and needs AI Step and AI Prompt connectors in DLP policies.

[Introduction]

Flow Builder is a Microsoft 365 Copilot agent that enables users to create automation flows using natural language. Based on customer feedback, Flow Builder is now fully included in the $30 Microsoft 365 Copilot license for employee-facing scenarios—no separate license or add-on is required.

[When this will happen:]

General Availability (Worldwide): Rollout begins September 29, 2025.

[How this affects your organization:]

Who is affected: All Microsoft 365 tenants with Copilot licenses.

What will happen:

• Flow Builder will be available to all users with a Microsoft 365 Copilot license ($30/month).
• No additional cost to build, run, or deploy Flow Builder agents.
• Flows are saved in each user’s Power Platform environment.
• Flows follow Microsoft’s standard Data Subject Request (DSR) processes.
• Conversation history is not stored—no chat data is saved or exportable.
• Feature is ON by default for eligible tenants.

Note: To enable Flow Builder in your environment, both AI Step and AI Prompt connectors must be included in your DLP policy.

Screenshot 1: Simply describe to the agent what you would like to automate:

 

Screenshot 2: Build your automation by simply chatting with AI:

 

[What you can do to prepare:]

Admins should:

• Confirm Flow Builder is turned on in the Microsoft 365 admin center (Copilot > Agents).
• Review Power Platform environment settings for export/delete options.
• Ensure that both the AI Step and AI Prompt connectors are included in your DLP policy, as both are required to enable Flow Builder in your environment.
• Check tenant-level feedback collection settings (applies across all Flow Builder entry points).
• Update internal documentation to reflect new licensing and privacy details.

[Compliance considerations]

No compliance considerations identified, review as appropriate for your organization.