If your Project Management Office (PMO) relies on repeatable project templates or frequently spins up similar engagements, this update eliminates the need to manually rebuild project structures, configurations, and related Microsoft Dataverse records from scratch every time a new engagement kicks off. However, because externally scheduled projects operate under different validation rules than native Project for the Web schedules, administrators and project managers need to understand exactly what gets copied, how resource assignments behave during the transition, and which guardrails still apply.
The Rollout Timeline and Parity Goal
Microsoft first introduced the ability to copy externally scheduled projects in public preview on January 30, 2026, before moving the feature into general availability in September 2026 (with M365 Admin reporting the general availability rollout reaching tenants starting September 4, 2026).
Prior to this release, the Copy Project button was restricted to projects scheduled through the default Project for the Web engine. Teams that opted for external scheduling had to manually recreate their task hierarchies, configurations, and supporting project data whenever they wanted to replicate a past engagement or establish a standardized template. With this update, Microsoft brings functional parity across scheduling modes through a unified copy workflow directly in the web interface.
Section Summary:
- Feature: Copy Project support for externally scheduled projects in Dynamics 365 Project Operations.
- Tracking IDs: Microsoft 365 Roadmap ID 576862; Message Center ID MC1464762.
- Timeline: Public preview began January 2026; General Availability arrived in September 2026.
- Availability: Worldwide (Standard Multi-Tenant) web platform, enabled by admins, makers, or analysts for end users.
Understanding External Scheduling in Project Operations
Why would an enterprise bypass Microsoft's built-in scheduling engine in the first place? According to Microsoft Learn documentation on external scheduling, the mode is designed for organizations that already use specialized third-party or proprietary tools to define their work breakdown structures, or those that need direct control over schedule hierarchy, dependencies, and task durations without hitting the structural limits enforced by Microsoft Project for the Web.
In external scheduling mode, organizations can natively create, update, and delete data directly within WBS-related Dataverse tables. That freedom comes with a major caveat: limited validation. Microsoft warns that if data is entered improperly into WBS-related tables, the resource reconciliation grid, estimates grid, tracking grid, and resource assignment grid may fail to render the data properly. Furthermore, once a project is created with the Externally Scheduled engine selected, that scheduling mode is permanent and cannot be switched later, and access to Project for the Web is restricted for that record (users view the WBS via the tracking grid instead).
How Admins Expose the Scheduling Engine Setting
While external scheduling is enabled by default in Project Operations, the column required to select it is hidden out of the box. According to Microsoft Learn, administrators or makers must expose it before users can create externally scheduled projects:
- Open the Maker portal and navigate to the main page for the Project entity.
- Select the Scheduling Engine column and change its property to Visible by Default (or add the column to your custom project main page if you do not use the out-of-box form).
- When creating a new project, users can then select Externally Scheduled from the Scheduling Engine dropdown list.
How the Unified Copy Workflow Works
Once you have an externally scheduled project that you want to reuse—whether as an official template or simply as a baseline for a repeat client engagement—the copying process follows the standard Project Operations workflow documented on Microsoft Learn.
There is one mandatory prerequisite: the source project must contain at least one task before the system will allow you to copy it.
Step-by-Step Copy Procedure
- Open the source project you wish to duplicate on the Projects form.
- Select Copy project from the command bar.
- Choose between Copy to New Project or Copy to Existing Project (which targets an eligible existing empty project).
- If copying to a new project: A quick-create form opens, allowing you to review and modify key project attributes—such as Contracting Unit, Owning Company, Calendar Template, and other project-specific settings—before finalizing the copy. Adjusting these fields upfront ensures the new project fits its target business context immediately, including fields that lock after project creation.
- If copying to an existing project: A dialog box prompts you to pick the destination project from a list of eligible records and specify your team member copy preferences.
Because copying a project duplicates the primary record, its attributes, and numerous related entities across Dataverse, Microsoft notes that Copy Project is a long-running operation. As soon as the copy process starts, the destination project page is locked for editing until the background operation finishes.
What Copies Over—and What Changes in Transit
A common trap in enterprise ERP and CRM administration is assuming that a "Copy" button performs a literal 1:1 clone of every underlying relationship. In Dynamics 365 Project Operations, the copy operation is intentionally selective to prevent corrupting resource bookings or financial contracts.
According to Microsoft Learn's Copy a project documentation, the action duplicates six core categories of data:
- Project properties
- Work breakdown structure (WBS)
- Project team members
- Project Estimates (Labor, Expense, and Material)
- Project checklists
- Project buckets
However, deployment model differences apply to specific project properties. Microsoft's documentation breaks down field-level support across deployment types as follows:
| Project Property Field | Project Operations Non-Stocked Materials | Project Operations Core | Project for the Web |
|---|---|---|---|
| Name | Yes | Yes | Yes |
| Description | Yes | Yes | No |
| Customer | Yes | Yes | No |
| Calendar Template | Yes | Yes | Yes |
| Currency | Yes | Yes | No |
| Contracting Unit | Yes | Yes | No |
| Owning Company | Yes | No | No |
| Project Manager | Yes | Yes | Yes |
| Status / Overall Project Status | Yes | Yes | No |
| Comments | Yes | Yes | No |
| Estimates (Labor & Expense Cost, Effort, Dates) | Yes | Yes | No |
| Estimated Material Cost | Yes | No | No |
Note on Estimated Dates: During the copy process, the Estimated Start Date reflects the date the project is created from the copy, and the Estimated Finish Date is automatically adjusted relative to that new start date.
Critical Resource, Schedule, and Commercial Boundaries
Before handing this feature over to project managers, IT administrators and PMO leads should highlight three major operational behaviors documented by Microsoft:
- Named Resources Become Generic Resources: When the resource-loaded WBS and project team are copied, the system preserves existing generic resources and their assignments, but it automatically converts any named resources into generic resources.
- Schedule Recalculation Risks: If the named resources in the original project had different working hours than the generic resources that replace them during the copy, Project Operations recalculates the schedule, which can alter task durations in the destination project.
- Quotes and Contracts Are Left Behind: While resource, expense, and material estimate lines copy over to the new project, quotes and contracts are not linked to the destination project. Teams starting a repeat engagement for an existing client will still need to establish new quote and contract linkages manually.
Ongoing Limitations of Externally Scheduled Projects
While gaining the Copy Project feature brings external scheduling closer to parity with native scheduling, externally scheduled projects still operate under strict functional boundaries in Dynamics 365 Project Operations. According to Microsoft Learn, administrators and project planners must still account for the following restrictions on externally scheduled projects:
- No Copilot Task or Status Generation: Copilot features for creating tasks, risks, and issues, as well as generating project status reports, are not available on externally scheduled projects.
- Static Dates and Work Hour Templates: Changing the project's start date does not automatically shift task start dates or resource assignments in the WBS ("Move project" is unsupported), and updating the project's work-hour template does not trigger a schedule recalculation.
- Resource Contours and Fulfillment Constraints: Creating resource assignments does not automatically populate the
mdyn_PlannedWorkcolumn that stores time-phased effort contours; organizations must format and supply valid contours themselves so cost and sales price contours calculate properly. Additionally, you cannot generate resource requirements directly from generic team members who have assignments, nor does the system replace generic resources on existing task assignments when an open requirement is fulfilled. Deleting a team member also does not automatically delete their resource assignments. - Quote and Contract Import Caps: When importing quote or contract line details from a project, the application enforces a ceiling of 500 tasks in the WBS, based on a maximum of 20 assignments per task.
Practical Takeaway for Dynamics 365 Admins
The arrival of Copy Project for externally scheduled projects removes a major point of friction for organizations that rely on custom or third-party scheduling engines alongside Dynamics 365 Project Operations. Being able to duplicate a project into a new or existing empty record—while adjusting the Contracting Unit, Owning Company, or Calendar Template on the fly—turns template-based planning from a manual data-entry chore into a routine workflow. Just make sure your project managers know to audit task durations after named-to-generic resource conversions and to wire up their new quotes and contracts once the copy lock releases.