Forum Widgets
Latest Discussions
[BUG] msdyn_project silently renamed from "Plan/Plans" to "Project/Projects" in new environments
We need clarification from Microsoft on whether this is a bug or an intentional breaking change. Overnight and without any announcement, the msdyn_project table now ships with display name Project / Projects in newly provisioned environments. Dev and UAT environments provisioned a few months ago have Plan / Plans out of the box. All environments are running the exact same PSCore version: 1.0.163.730. The entity is as expected, marked non-renameable — read-only in the maker portal — so there is no way to align environments manually. Solution import from an existing environment (where msdyn_project = "Plan") into a newly provisioned Production environment fails with: 0x8004023B: Entity 44286cce-2389-4532-ac04-7a18a2818e9a is not a renamable entity. Hence Entity Display Name cannot be modified The only workaround — and why it is not acceptable It is technically possible to manually edit customizations.xml inside the solution ZIP before importing, removing the <DisplayName> node for msdyn_project. The import will then succeed, but Production will permanently show "Project" while Dev and UAT show "Plan" — a broken inconsistency across environments. More importantly, this is not how ALM is supposed to work. Developers should never have to manually patch solution artifacts to work around a platform-level inconsistency introduced silently by Microsoft. This is incompatible with automated CI/CD pipelines and unsustainable for any team managing multiple environments. The question for Microsoft Is this a bug or a planned change? If it is a bug: when will it be fixed, and is there a supported workaround in the meantime? If it is a planned change: why was it not communicated, and what is the supported migration path for teams with existing environments and solutions? [UPDATE]: After 3 attempts of resetting and reprovisioning the Production environment, msdyn_project finally came up with Plan / Plans — same process, same PSCore version each time. The behavior is non-deterministic. The only workaround currently available is to keep resetting your environment until you get lucky, which is not an acceptable answer for any type of deployment.
2026.02.20 - Planner UI update is worse
The UI changes to Planner within the latest Teams desktop app update (version 26032.208.4399.5) has regressed in its functionality and is worse than before. Previously, all of the contents of an item in the Planner were visible at the same time. Now I have to tab between Task Details, Attachments and Checklist, and am unable to view these at once, which has become a critical workflow for me. It is extremely irritating, as I've developed a workflow around how Planner was presented (which was that everything within a task was visible at once), and now it has been compartmentalised. Please unwind this - it is a regressive update and provides less information and requires more interaction to work through the detail of a task.
Planner tab missing from Teams channel only shows as separate app
Our users can no longer open the Planner in the Teams channel; they can only access it via the app. This has been the case for a short while now. Does anyone know of a fix for this, or is this how it’s supposed to work? It cannot be selected via apps.
Premium Planner compatible apps?
Has anyone found any 3rd party solutions to bridge the gap on some of the shortfalls of Planner Premium? I'm really looking for something that my field team can use to access Planner tasks on their mobile devices. Also, for management, I need a solution that allows them to track tasks assigned to their team members across multiple open plans/projects. Thanks for any suggestions! Also, if Microsoft is working on any of these solutions, please put out some communications to help us explain to our bosses that something is being done.@mentions in Microsoft Planner
Introducing @Mentions in Microsoft Planner: A Game-Changer for Task Management At No More Bad Mondays, we're all about making your workday smoother and more productive. Today, we're thrilled to share a solution that addresses a common pain point in Microsoft Planner: the lack of an @mention function in comments. We've developed a solution that enhances your commenting notification capabilities and ensures that your team stays informed and engaged. Here's how our new free download can transform your task management experience. The Challenge Microsoft Planner is an excellent task management tool, but it's been missing a feature that many users have been requesting: the ability to @mention team members within comments. Without this feature, reaching someone to update on a task can be challenging, especially when Planners standard notifications can sometimes be overlooked or in many cases, not actually reach them! The Solution Imagine you've assigned a task to your team and want to follow up with a specific member. You might comment, "How are you getting on with this one David?" but in Planner, this won’t notify David directly. That’s where our new Power Automate solution comes in. With our solution, when you add an @ in a Planner comment, the following happens: Teams Notification: The relevant staff member receives a Microsoft Teams notification with the comment you posted, including the task name and a direct link back to the task. Clean Communication: The @mention is automatically removed from the Teams message, keeping things neat and focused. Personal Touch: The notification is sent from the person who posted the comment, ensuring a personal touch. This solution not only improves comment notifications but also ensures that the right person is always aware when someone has left a comment on a task. How to Get Started Download the Solution: Grab our Power Automate solution for free. Configure: You'll need to update the solution to point to the relevant Plan you want to monitor. It will then work for all tasks within that Plan, old and new. Multi-Plan Use: Feel free to use it across multiple Plans within Microsoft Planner for comprehensive coverage. Share the Love We’re excited to offer this solution free, but we’d appreciate your support. If you find our solution helpful, please share this post or a link to (external link removed by moderator) on your social media and within your organisation. Your support helps us continue to develop and offer more solutions to make your workday better. Thank you for being a part of our community, and happy planning! Download your free @Mentions solutions today and take your Microsoft Planner experience to the next level! (external link removed by moderator)
New planner doesn't show a "schedule" view of tasks assigned to me from different plans
The new version of web-based Planner was enabled for me a few days ago, on November 17th. Apparently, I realized that one of the features I used is missing. At the "My Tasks" view, in the old version of Planner, one could choose to have different views, apart from the grid view. The most useful one for me was the "schedule" view, since I could see in one calendar, all assigned tasks from different plans/teams/projects. This functionality now seems to have been removed, and one can only see one separate schedule per plan.
Moving basic planner to premium planner.
We're testing the new planner premium features and are unable to convert our current plans to show the new features. We have the ability to create a new premium plans but the information on learn doesn't match what we're seeing in app on team and on the web. https://learn.microsoft.com/en-us/office365/planner/plan-conversion#converting-to-a-premium-plan We've also tried creating a Premium plan and recreating the buckets of the original plan with the aim to move the tasks to the new plan but the new plan does not show on the main list. Are we missing something?Planner premium conversion issue
Hello, I need to convert planner basic to planner premium and I receive the below error: A copy of your plan is now premium Your plan couldn't be converted to premium, so a copy of it was created for you to try out. You can try to convert the plan for your team later.
