Stop confusing people between office 365 group and Plan
Office 365 Group is a group, not a plan. And a Plan is a plan, not a group. User can create as many plan as they want, personally. When they want to share with a group, then the plan can be accessed from the group. It's simple.
Currently, the way that you are connecting Plan and Office 365, you are destroying user experience and make the whole system unsuable.
Please distinguish them clearly as there are many confusing scatter around the uservoice:
Completely Agree! Many customers and even myself are baffled why a 'Plan' is an 'Office 365 Group'. Each individual user should be able to create as many Plans as they want, while also giving the ability for Groups to create Plans as well.
Paul Frederickson commented
This needs to happen. Nowhere in the verbiage for creating a new plan does it indicate you're actually making an O365 group. I thought the 'New Plan' screen verbiage was a bug at first, but it appears to be a complete architectural oversight in Planner.
A group should be able to have many plans, you should be able to see all the plans for a group, and be able to create a new plan and add it to a group.
You should also be able to create a plan independently from a group and store it in your OneDrive.
Bill Blais commented
See also these additional requests here, in addition to the ones posted originally by Van Ly. Together, they currently total about 55 votes. Nice to have them all in one place.
We just deleted our planner as well by removing the group in teams as it showed separate information, we assumed it was a separate teams group. To avoid confusion among our people we deleted it in teams in favor of just using planner, and to my surprise they were both gone! Not to mention the issues with private teams being proactively offered to random users in the company... Hey rando associate, Microsoft recommends you ask to join the IT department group! Uhhhhh NO!? What the actual ****?
I am an experienced user of Office 365 and SharePoint (databases, permissions, the works). We just started using Microsoft Teams, and we really liked the integration of Planner. We started building, and then I wanted to delete some empty Plans. I thought I was deleting an empty plan, but inadvertently deleted our active plan. Which wiped out not only the plan, but the Team, and our access to the associated SharePoint site with two databases and a bunch of files. Fortunately I have backups of all the files, but this kind of cascade of deletions should NOT be possible, and if it is, it should be reversible by the user. Not everyone has dedicated site admin, and I am having to babysit the restoration with our site admin, who have never seen this kind of thing and are not creative thinkers. The solution I found online the FIRST time I was aware how intertwined these tools are. If an experienced user like me could end up with this kind of mess by deleting a Planner, I can't recommend this tool for anyone. Which is a shame, because our team really liked what we were building with Teams, the Planner and SharePoint.