Power Platform Community Forum Thread Details

Limitations with Project Accelerator in Custom Dataverse Environment – Need Guidance

In 2024, we initiated a centralized PPM (Project Portfolio Management) approach to manage our internal projects using Microsoft-native solutions, without additional investment.

Initially, we evaluated Project Online but decided against it due to its upcoming deprecation and limited long-term viability. We then adopted the Microsoft Project Accelerator, which aligned well with our requirements. Our pilot was successful, and we began scaling it across multiple projects globally.

However, over the past 6–12 months, we have encountered several limitations impacting user experience and adoption. Some key challenges include:

No notifications when tasks are assigned

No reminders for task due dates

Limited functionality for tasks created within plans generated via Project Accelerator

Missing basic features expected in standard task management tools

Upon raising support requests, we were informed that these limitations are primarily due to the setup—specifically, hosting in a custom (non-default) Project/Dataverse environment, even though the deployment followed Microsoft-recommended guidance.

These gaps significantly impact usability and create a suboptimal user experience compared to standard Microsoft offerings.

We are seeking guidance on the following:

Is there a way to enable full Planner/Project functionality (notifications, reminders, etc.) in a custom Dataverse environment?

Can existing plans/projects from Project Accelerator be migrated to the new Planner (native) environment? If yes, what would be the recommended approach?

Are there alternative Microsoft-native solutions or architectures better suited for managing multiple global projects with full functionality?

We would greatly appreciate insights, recommended approaches, or best practices from the community.

Thank you in advance for your support!

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.

Quick Links

Leaderboard > Engage with the Community