Known limitations include:
- The synchronized data should be in accordance to Planner Premium plans limits and boundaries: Project for the web limits and boundaries
- Task custom fields are not synchronized yet (implementation is on the roadmap)
- Project custom fields are not synchronized yet (need feedback if it is needed)
- Resource custom fields are not synchronized
- The Agile view is not synchronized yet
- Bookable resources are not created automatically in the Dataverse / CRM. The sync process tries to match the resources by their names / emails / logins.
- The tool currently takes date matches as a priority over duration matches. In other words, in case of scheduling differences caused by different calendars, the tool will try to enforce the Start and Finish dates to match, even if it will sacrifice the Duration matching.
- Task fields currently being synchronized: "Task Name", "Outline Level", "Start Date", "Finish Date", "Duration", "Notes", “% Complete”, “Work”, “Actual Work”, “Task Type”
- As Task Type is set only at the Plan level in Planner Premium / Project Operations and can’t be changed after creation, Task Type synchronization can’t be done 2-way, and only synchronized from Planner / Project Operations to MPP
- Variations in Task types in the MPP file can't be synchronized to Planner Premium / Project Operations plan due to the limitation mentioned above, and can result in deviations in synchronized data.
- Duration units unsupported by Planner Premium / Project Operations, such as elapsed days/weeks are not guaranteed to be processed correctly.
- Manually scheduled leaf tasks are synchronized but not fully supported by Planner / Project Operations and may not be scheduled/synchronized properly.
- Manually scheduled Summary Tasks are not supported and will be synchronized as automatically scheduled, with start & end dates calculated based on child tasks.
- External tasks are excluded from the synchronization by default. If included and synchronized to Planner / Project Operations, they may affect the parent Summary task(a) and can cause inaccuracies in the synchronized schedule.
- Individual task calendars are not supported, and the schedule that is heavily reliant on task calendars may be synchronized incorrectly.
- Master Projects support is not complete
- Sub-projects are not automatically synchronized from the Master Plan with individual Planner Plans / Project Operations Projects, even when connected to Planner plans with Project Sync
- Sub-projects can be opened individually and synchronized to connected Planner Plans / Project Operations Projects, not affecting the Master Plan connected to their Master Project
- Inactive tasks are not synchronized to Planner Premium / Project Operations Projects to avoid scheduling inaccuracies
- Manual tasks or tasks scheduled with elapsed duration units that start and finish over the non-working days require setting the project calendar in Planner / Project Operations to include these days as working (e.g. 24/7 or 8/7 calendar). Using 24/7 calendar can be helpful to have the Work values calculated the same way as in Project Desktop in case of elapsed days duration units.
- Using 24/7 calendar (e.g. as suggested above) can lead to limitations in task duration that are shorter then the limitation officially suggested by the official service limitation documentation. The documented limitation is 1250 days for leaf tasks; however, with 24/7 calendar the maximum leaf task duration is ~416 days. Both values are 10,000 hours, which seems to be the true limitation.
- Baselines are not yet fully supported by the Planner / Project Operations and not synchronized
- The following task constraints are not supported by Planner / Project Operations and tasks that utilize these are synchronized using supported types of constraints
- As late as possible
- Start no later than
- Finish no later than
- Must finish on
- Must start on
- "Schedule from setting" at the project level is not supported by the Planner / Project Operations and not synchronized
- Recurring tasks are not supported by the Planner / Project Operations and are synchronized as individual, unrelated tasks
- Task Deadlines are not supported
- Resource Assignment units are not supported by Planner / Project Operations and are "emulated" during the synchronization using the timephased assignment data entry
- Resource assignments made to the Summary Tasks are not supported by Planner / Project Operations and can't be synchronized.