=============================================

Design Change Request (DCR)

=============================================

Title:

Enable Environment Routing Rules for M365 Office Workflow App Creation (Teams, Excel, Word, PPT, Outlook, OneDrive, SharePoint)

Date: 2026-06-08

Requesting Team: CSS - Power Platform Support

Target Product: Power Automate - M365 Office Workflow Integration

---------------------------------------------

CURRENT BEHAVIOR

---------------------------------------------

When users create Workflow apps from M365 Office products (Teams, Excel, Word, PPT, Outlook, OneDrive, SharePoint), the Workflow is ALWAYS created in the Default environment.

This behavior does NOT respect the organization's environment routing rules, unlike other M365 integration scenarios that already support routing.

---------------------------------------------

COMPARISON WITH OTHER SCENARIOS

---------------------------------------------

Scenario | Respects Environment Routing? | Target Environment

#1 M365 Office -> Workflow app (THIS DCR) | NO | Always Default environment

#2 M365 Copilot -> Workflow Agent (conversational) | YES | Personal Developer environment (via routing rule)

#3 M365 Copilot -> Agent Builder (Copilot Studio) | YES | Personal Developer environment (via routing rule)

#4 SharePoint -> Canvas App Rich Form | YES (configurable) | Designated environment

Scenarios #2, #3, and #4 already support environment routing or environment designation, but Scenario #1 (the most commonly used by end-users) does not.

---------------------------------------------

CUSTOMER IMPACT

---------------------------------------------

- Organizations that have configured environment routing rules to direct personal workloads to developer environments expect ALL M365-initiated Power Platform resources to follow the same routing logic.

- The Default environment becomes cluttered with individual user Workflows that should be routed to personal developer environments per organizational policy.

- Admins must manually move or recreate Workflows in the correct environment, creating unnecessary overhead.

- Inconsistent behavior across M365 entry points confuses both admins and end-users:

"Why does my Copilot agent go to my dev environment, but my Teams Workflow goes to Default?"

---------------------------------------------

ASK

---------------------------------------------

Primary ask: Allow M365 Office Workflow app creation (from Teams, Excel, Word, PPT, Outlook, OneDrive, SharePoint) to respect the same environment routing rules that already apply to M365 Copilot Workflow Agent and Agent Builder scenarios.

Specifically:

1. When an environment routing rule is configured in the organization, M365 Office Workflow creation should route to the designated environment (e.g., personal developer environment) instead of always targeting the Default environment.

2. If no routing rule is configured, maintain current behavior (Default environment) for backward compatibility.

3. Optionally, allow admins to configure a dedicated "Workflow environment" similar to the existing "SharePoint Form environment" designation.

Reference: https://learn.microsoft.com/en-us/power-platform/guidance/adoption/manage-default-environment#designate-a-sharepoint-form-environment