Planner Portfolio is showing the date plans were uploaded or some other date instead of their actual start dates.

Winston Jones 20 Reputation points
2026-10-08T18:42:49.7466667+00:00

2026-10-08_14-21-48.pngI am experiencing an issue with Microsoft Planner where the Portfolio view displays an incorrect Start Date for a Premium plan, even though the End Date is correct.

Example:

Plan Name: Modernize Orders

Actual Start Date (Plan Grid View): 10/15/2026

Incorrect Start Date (Portfolio View): 5/14/2026

End Date: 9/29/2028 (correct in both views)

I have verified that October 15, 2026, is the earliest start date across all tasks and subtasks in the plan. However, the Portfolio view continues to display May 14, 2026.

This creates inconsistencies in portfolio reporting and project scheduling visibility.

Is this a known synchronization issue or bug in Planner Premium Portfolios? How can I ensure the Portfolio view accurately reflects the Start Date from the underlying plan?

I have attached a screenshot illustrating the discrepancy.

Microsoft 365 and Office | Project | For business | Windows
0 comments No comments

1 answer

Sort by: Most helpful
  1. Kai-L 20,025 Reputation points Microsoft External Staff Moderator
    2026-10-08T19:26:04.3966667+00:00

    Dear Winston,

    As a forum moderator, I genuinely wish I could directly review your plans and portfolio or delve into the backend systems to diagnose and fix this for you. Unfortunately, my role here is limited to providing general guidance and solutions that can be applied by users. 

    Since the plan's summary row and earliest tasks all start on 15 October while the end date shows correctly, the plan's schedule itself looks fine. The problem seems to be in how Portfolio reads the start date. I tried to reproduce this on my side, but the start dates in my portfolio matched the plans correctly. That suggests something specific to how these plans were set up or imported, rather than a general problem affecting all portfolios. I also couldn't find a Microsoft notice confirming this as a known issue.

    One thing worth checking: open the plan's details and look at its own Start date, which is separate from the task dates. If it's still set to 14 May 2026, change it to 15 October 2026 and see whether Portfolio updates. If the start date in the plan details is already correct, I recommend reporting it to Microsoft through Feedback (top right) > Report a problem in Planner and include your screenshot.

    Since this affects portfolio reporting, I also recommend that the Global Admin in your organization create a service request with Microsoft Support. A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin. If you don't know who your IT administrator is, please refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support 

    I truly hope you get your issue resolved swiftly. Please know that even though I can't directly intervene, directing you to the correct, specialized support is the most effective help I can provide from my position. Thank you for your patience and understanding. Please let me know if you need anything else. Wishing you all the best. 


    If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

    Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.