Hello RA-07041050-0 ,
Greetings! Thanks for raising this question in the Q&A forum.
This is a great and very detailed question. The core reason behind these limitations is that the
Microsoft Project Accelerator, when deployed in a
custom (non-default) Dataverse environment, operates outside the native integration boundaries of Microsoft Planner and the new unified To Do/Planner ecosystem. Features like task assignment notifications and due date reminders are tightly coupled to the default environment's Planner integration, which is why they don't surface in a custom environment setup even when everything is deployed correctly per Microsoft's guidance.
Let me address each of your questions step by step:
Question 1: Enabling Full Planner/Project Functionality in a Custom Dataverse Environment
Step 1: As a workaround for notifications and reminders, build Power Automate flows triggered on Dataverse row changes (task creation, assignment updates, due date changes) to send email or Teams notifications. This effectively compensates for the missing native notification capability.
Step 2: For due date reminders specifically, use a scheduled Power Automate flow that queries tasks approaching their due dates and sends reminder messages via Teams or Outlook.
Step 3: Be aware that some Planner-native features (like the unified Planner hub in Teams) will remain unavailable in a custom environment. These are platform-level limitations and cannot be fully unlocked without migrating to the default environment.
Question 2: Migrating Existing Plans/Projects to the New Planner (Native) Environment
Step 1: There is currently no out-of-the-box migration tool to move Project Accelerator data from a custom Dataverse environment to the native Planner environment.
Step 2: The recommended approach would be to use the Dataverse Web API or Power Automate to export your existing project and task data, then recreate the plans in the new Planner environment either manually or via the Planner Graph API for bulk creation.
Step 3: Before attempting any migration, thoroughly document your current data model — including custom fields, relationships, and dependencies — so nothing is lost in the transition.
Step 4: Pilot the migration with one or two smaller projects first to validate the approach before doing it globally.
Question 3: Alternative Microsoft-Native Solutions for Multi-Global Project Management
Step 1: Consider the new Microsoft Planner (which now unifies To Do, Planner, and Project for the Web under one experience) deployed in the default environment — it provides native notifications, reminders, and Teams integration out of the box.
Step 2: If your organization needs more robust portfolio-level management, Microsoft Project for the Web (accessed via project.microsoft.com) in the default environment is your best native option, as it sits on Dataverse but within the supported default environment boundaries.
Step 3: If cross-project reporting and resource management are important, pairing Project for the Web with Power BI connected to Dataverse gives you strong portfolio visibility without additional licensing costs.
Step 4: Avoid redeploying into a custom environment unless there is a strict data isolation requirement, as it consistently introduces these integration gaps.
The overall recommendation is to plan a phased migration toward the default environment using the new unified Planner, and bridge the gap in the meantime with Power Automate flows for notifications and reminders.
If this answer helps you kindly accept the answer which will help others who have similar questions.
Best Regards,
Jerald Felix.
