Currently marked as "In development," this web-based feature is slated for General Availability in March 2027 across Worldwide (Standard Multi-Tenant) and Government Community Cloud (GCC) instances. As with all Microsoft roadmap items, the March 2027 window represents the company's current projection rather than a guaranteed delivery date.
How the Planned Hierarchy Import Works
In the existing task-import workflow for Dynamics 365 Project Operations, reusable task blocks pulled from other accessible projects are automatically appended to the bottom of the target project's WBS. While that provides a selective alternative to copying an entire project or calling schedule APIs, it leaves project managers with manual cleanup whenever those tasks actually belong in the middle of an active phase.
According to Microsoft's description for Roadmap ID 576298, the new feature adds a contextual entry point directly inside the schedule:
- Context Menu Selection: From the task grid, a project manager can open the context menu on an existing task and select Insert task below.
- Confirmation in the Import Pane: Selecting that option opens the standard Import Tasks pane, which explicitly confirms the chosen insertion point before the import runs.
- Same-Level Placement: Imported tasks are placed immediately after the selected task and sit at the exact same level in the task hierarchy.
- Subtask Protection: If the selected target task is a summary task that already contains subtasks, the system does not split the family tree. Instead, the imported tasks are inserted after the entire group of subtasks, preserving the existing hierarchy.
- Batch Integrity: When a manager imports multiple tasks at once, those tasks remain grouped together in their original order, retaining both their internal hierarchy structure and their task dependencies.
- Backward Compatibility: The standard Import Tasks command remains unchanged and continues to append imported tasks to the very end of the project plan for users who prefer the default behavior.
| Import Method | Trigger Location | Placement in WBS | Effect on Existing Subtasks |
|---|---|---|---|
| Standard Import Tasks | Project command bar / ribbon | Appended to the end of the project plan | None; added after all existing work items |
| Insert Task Below (Roadmap ID 576298) | Task grid context menu on a specific task | Immediately after the selected task at the same outline level | Inserted after the selected task's entire subtask group |
Section Summary: Roadmap ID 576298 introduces an Insert task below context-menu action in the task grid that anchors imported tasks to a chosen outline level while leaving the standard end-of-plan Import Tasks command intact.
Why Hierarchy Placement Matters in Project Operations
To appreciate why this seemingly small UI tweak matters, it helps to look at how the Dynamics 365 Project Operations scheduling engine calculates a Work Breakdown Structure. According to Microsoft Learn documentation on creating a WBS, a project schedule is divided into two fundamental node types: summary (or container) tasks and leaf node tasks.
Leaf node tasks hold the granular work estimates, assigned resources, planned start and end dates, and durations. Summary tasks, by contrast, hold no independent work effort or cost of their own; their effort, cost, start dates, and finish dates roll up automatically from their child container and leaf tasks. Furthermore, whenever you indent or promote a task in the grid, Project Operations recalculates the task's schedule ID to match its new outline depth and recalculates the parent summary task's effort, cost, and dates accordingly.
When an import tool dumps twenty tasks at the bottom of a 300-line schedule, the project manager has to drag and drop them—or use Cut and Paste in the schedule grid—and then indent or promote them to fit the target phase. One slip of the indentation level can accidentally turn a peer task into a child task, skewing the rollup dates and financial estimates of a summary container. By placing imported tasks at the exact hierarchy level of the selected task—and safely below any existing subtasks attached to that node—the planned Insert task below workflow removes a repetitive, error-prone post-import step.
Preserving Dependencies During Batch Imports
The roadmap entry also notes that importing multiple tasks together maintains their internal structure and dependencies. As documented on Microsoft Learn, Project Operations supports four predecessor dependency types—Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF)—along with lead and lag offsets that automatically reset a successor task's planned start date based on predecessor completion.
Keeping those internal links intact during a mid-schedule insertion means a reusable module—such as a standard "Requirement Analysis -> Development -> Testing -> Deployment" sequence —can drop into Phase 2 of a project without forcing the manager to rebuild the predecessor chain from scratch. Microsoft's roadmap summary does not specify how the engine resolves edge cases where an imported task's predecessor sits outside the selected batch, so administrators will need to watch for updated Microsoft Learn documentation as the feature nears release.
Section Summary: Because summary task costs, effort, and dates roll up dynamically from child tasks in Project Operations, inserting imported work at the exact outline level avoids manual drag-and-drop reorganization and accidental rollup recalculations.
Broader Context and What Admins Should Expect
This update is part of a broader cluster of task-import enhancements Microsoft has been rolling out for Dynamics 365 Project Operations. Alongside the core ability to import tasks from other projects (tracked under Roadmap ID 573692) and public API support for programmatic task imports (tracked under Roadmap ID 574365), Roadmap ID 576298 focuses squarely on interactive usability for project managers working inside the browser.
For enterprise IT administrators and PMO leads preparing for the March 2027 General Availability window:
- No Disruption to Existing Workflows: Because the standard Import Tasks button continues to append tasks to the bottom of the project plan, existing training materials and user habits will not break when the update lands.
- Cloud Scope: The feature is scheduled for Worldwide (Standard Multi-Tenant) and GCC environments on the web platform. Organizations operating in other sovereign clouds should monitor the roadmap for separate rollout listings.
- Wait for Documentation Before Updating SOPs: Because Roadmap ID 576298 is still in development, project teams should continue relying on the standard append-and-move workflow in production today and hold off on revising internal standard operating procedures until the context-menu action appears in release notes.