Microsoft 365 can cover a straightforward project without a separate project-management platform. Use Teams for conversation and meetings, Planner for tasks, SharePoint for controlled documents, Lists for structured registers and Power Automate for specific hand-offs. The hard part is agreeing which tool owns each type of information.
A simple working model
| Need | Microsoft 365 home |
|---|---|
| Project conversation and meetings | Microsoft Teams |
| Tasks, owners and due dates | Microsoft Planner |
| Files, versions and controlled access | SharePoint |
| Risks, issues, decisions and changes | Microsoft Lists |
| Personal view of assigned work | Microsoft To Do or Planner My Tasks |
| Repeatable notifications and approvals | Power Automate |
Do not duplicate the same task in a spreadsheet, Planner and a channel post. Pick one authoritative record and link to it.
Set up the project
- Create or choose the Microsoft team that will own the work.
- Record at least two team owners and the expected closure date.
- Create channels around durable workstreams, not every passing topic.
- Add a Planner plan for deliverables, owners and due dates.
- Use the connected SharePoint site for project documents.
- Create Lists only for structured records that need fields, views and history.
- Write a one-page working agreement explaining where each object belongs.
Every team has a connected Microsoft 365 group and SharePoint site. Removing the team or changing membership can therefore affect more than chat. Build an archive and ownership plan before the project ends.
Planner basic and premium
The current Planner brings together basic work management and capabilities previously associated with Project for the web. Basic plans provide common views for team tasks. Premium plans add features such as Timeline, dependencies, custom fields, workload and goals, subject to licensing.
Do not label a project “Project for the web” in new operating guidance without checking the tenant's current Planner experience. Microsoft is bringing those capabilities into Planner, and app names have changed during the transition.
Choose premium only when a named requirement needs it. A Gantt view can be helpful, but it does not fix unclear ownership or unreliable updates.
Keep files in SharePoint
Upload project files to the team's connected SharePoint library rather than attaching private copies from personal storage. Use folders or metadata consistently, keep version history on and restrict sensitive material deliberately.
A Teams channel is a collaboration surface over Microsoft 365 services. Deleting or renaming something in Teams can affect its SharePoint-backed content, so owners should understand both sides.
Automate only stable hand-offs
Power Automate can remind an owner, create an approval or update another system. Start with a manual process that has a clear trigger, owner and recovery step.
For each flow, record:
- service account or owner;
- connections and permissions;
- expected failure notification;
- duplicate-run behaviour;
- manual fallback;
- retirement date with the project.
Automation output is not proof that a human approved or completed something unless the flow stores that evidence correctly.
Reporting without surveillance theatre
Use Planner and Lists to answer operational questions: what is late, blocked, unowned or awaiting a decision? Avoid turning activity counts into performance claims.
Power BI can combine approved data for wider reporting, but that introduces data modelling, refresh, permission and licensing work. Add it only when the decision cannot be served by the source views.
Close and recover
At closure, confirm final owners, move lasting records to their governed home, export or preserve the required registers, remove obsolete guests and archive the team where appropriate.
Test recovery before the project is urgent: restore a file version, reassign an orphaned task and identify how a failed flow is rerun safely.
What this proves
This model proves that every project object has an agreed home and owner. It does not provide formal portfolio management, guarantee delivery or determine the correct licence. Test the design with one real project and document the gaps before scaling it.
For practical ways to keep Microsoft 365 work organised, join the Microsoft 365 Productivity Space.