Dynamics 365 Project Operations: Import tasks into a project from other projects
Currently, to bring tasks from another project into a new project, you must manually enter the task details in the task grid or use schedule APIs. You can also use the Copy project feature to create a new project with the same tasks, but this feature has limitations: You copy t
DIGITAL SKILL WORKS LTD / 12 PANES
What it is
Dynamics 365 Project Operations: Import tasks into a project from other projects is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: Rolling out.
What it does
Currently, to bring tasks from another project into a new project, you must manually enter the task details in the task grid or use schedule APIs. You can also use the Copy project feature to create a new project with the same tasks, but this feature has limitations: You copy the entire project, including unwanted tasks and extra information. You can't combine tasks from multiple projects into a new project. With this feature, you can select and import tasks from one or more existing projects into a new project, saving time and effort. You can choose the project and tasks to import while adhering to the task limits per project as specified in the public documentation. When this feature is enabled in the feature control settings, you can: Select the Import Tasks button from the project ribbon. Use the project picker to select the source project in the side pane. See the grid populate with the tasks associated with that project after a project is selected. Choose the tasks to be imported into the target project, and then select Add . Know that imported tasks are automatically appended to the target project's Work Breakdown Structure (WBS).
Why you should care
Board
Track as Horizon signal; decide whether it changes Wave 0 priority or stays on the watchlist.
CISO
Confirm identity, data access, and overshare exposure before enabling for broad cohorts.
CFO
Map licence or consumption impact to the frozen value case; avoid seat spray.
Adoption
Pilot with a named cohort and measure changed work, not vanity clicks.
Suggested action
Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Add to Horizon watchlist with an owner. Pilot only after Steady controls for the affected surface are in place.
12 Panes: 03 Horizon
Communication needed
- Security: Assess exposure, Conditional Access, and agent/tool permissions.
- GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
- FinOps: Forecast seat or credit impact; align to frozen value case.
- Adoption: Plan cohort messaging, clinics, and success measures.
- Comms: One story for board and staff — what changes, what does not, who owns risk.
Benefits
- May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
- Roadmap visibility helps Horizon planning without guessing dates.
Risks
- Status and dates change; treat MRC as directional, not a contract.
- Enabling without Steady controls can amplify overshare or cost leakage.
- Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.
Source
- MRC id: 573692
- Status: Rolling out
- Products: Dynamics 365 Project Operations
- GA / disclosure: October CY2026
- Preview: November CY2025
- Platforms: Web
- Cloud instances: Worldwide (Standard Multi-Tenant), GCC
- moreInfoUrls: —
- Open on Microsoft 365 Roadmap
Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.