Move In · Digital House Starter Kit · follow the pathStart
Welcome to the neighborhood
Moving into your digital village
Onboarding onto Microsoft Teams is like moving house. The hard part isn't the furniture — it's the architecture: how the place is structured, and one idea that changes how you work forever. This workbook walks your team through the move, one stop at a time. Each stop teaches the idea, shows the real Microsoft 365 term beside it, and asks you to fill in your own version.
Graphic placeholder
🏘️
Hero illustration — the village
A small village of houses (Teams) with a road running through it, one house highlighted. Establishes the metaphor at a glance. Bridge-work line-art style, connect-teal accent.
How to read each stop your guide
!First-timer mistakes — the classic week-one traps.
💡Nuggets — the under-the-hood fact that makes it click.
🔍Dig deeper — expandable detail you can skip or open.
landlordresident tags show who a point is mainly for.
i
Before the village, one mental shift. The next stop is the most important in the whole workbook — it's the single idea that makes everything else obvious. Don't skip it.
Stop 1 · The big idea
Communication and files just moved in together
Two buildings → one=Mail + Files now live in Teams
Everything else in this workbook follows from one shift. Until now, your work lived in two separate buildings: email, where you talked, and a file server or drive, where documents lived. They never really met — you discussed a file in one place, then went somewhere else to find it. You were the courier carrying context between them.
AI video / animation placeholder
🎬
"The two buildings merge"
~30–40s animation. Two separate buildings labelled Mail and Files slide together into one structure. Camera pulls back: every room inside now holds both a speech bubble and a folder. End card: "In Teams, you always think in two dimensions."
Two ways to say it — whichever clicks for you: • Teams is a chat built into your file explorer. • Teams is a mail account with all the files already attached.
From now on: think in two dimensions the core lens
Every container in Teams holds both a place to talk and a place to keep files. You never think about one without the other.
◆ Dimension 1
Communication
The talking — messages, posts, decisions, @mentions.
+
◆ Dimension 2
Files
The documents — drafts, working files, the shared record.
💡
Hold this and the rest is easy: a channel is a conversationand a folder. A Team is a group chatand a file store. The two grew together — so every choice you make happens in both dimensions at once.
What a Team really is demystified
Under the friendly surface, the structure is simple:
Diagram placeholder
🗂️
Folder-tree diagram — "a Team is a folder with chat"
Left: a SharePoint folder tree (Team site → channel subfolders). Right: the same thing shown as the Teams UI (Team → channels). Arrows connecting them 1:1. Caption: "house = top folder · room = subfolder."
The honest version: a Team is essentially a SharePoint site (a top folder) with a conversation layer on top. A channel is a subfolder with its own conversation. The files you see in a channel are that subfolder. We gave a folder a friendlier face.
What you're actually organizing the two levers
Here's the reframe that prevents most mistakes. People think channels and Teams organize topics. They don't. They control just two things:
🔑
Access
"Who can get in?"
Who can see the conversation and open the files.
🔔
Attention
"Who gets notified?"
Who it's addressed to — who gets pinged, who it's "for."
The reframed golden rule: don't create a space for a new topic. Create one for a new audience — a different "who can see it" or "who gets pinged." Topics are the excuse; access and attention are the real reason.
i
Carry these three things into every stop:(1) two dimensions — comms + files. (2) two levers — access + attention. (3) a Team is a folder with chat attached. That's the whole architecture.
🔍Dig deeper: the one nuance to keep us honest landlord⌄
"A Team is a folder + chat" is the right mental model, and it's literally true for the files dimension. Two small truths so we never teach something we have to walk back:
Channel messages aren't stored inside the SharePoint folder. The folder holds the files; the conversation lives in the group mailbox / Teams' own store, attached alongside. Experientially they "live together" — we just don't claim the chat is a file in the folder.
Private & shared channels are their own separate site, not a subfolder of the house (covered at the Move-in and Storage stops).
For day-one understanding the simple model wins. The precision is dig-deeper, not the headline.
You don't live in one house — you live in a village
The village=Your organization (Microsoft 365 tenant)
You won't have a Team — you'll belong to several. Each is a separate house with its own rooms, closets and residents, and they all sit inside one village: your organization's Microsoft 365 tenant. See the village clearly and the most common mistake — building a new house when you just needed a room — disappears.
i
Through the two levers: a new house is a new access boundary (new walls, new membership). A new room is a new attention stream inside walls that already exist. People build whole houses when they only needed a room — that's village sprawl.
The village map metaphor ↔ real term
The village = your tenant — one boundary, one directory.
Each house = a Team — you're a resident of several.
Rooms = channels — where work happens.
Your own home = your OneDrive — your private place.
The roads = chat & search — how you move around.
Another village = a different organization — where guests come from.
Diagram placeholder
🗺️
Village map — you among many houses
Top-down village: several houses (Teams) you belong to, your own small home (OneDrive) set apart, roads connecting them, and a neighboring village (another tenant) at the edge for "guests." "You are here" pin on two or three houses.
The golden rule of the village read twice
🚪 Same people, new topic?
Add a room (channel) to a house you already live in.
Default move
🏠 Genuinely new group?
Different people, own access → then a new house (Team).
The exception
🏚️ A house per topic?
Walls and access control you didn't need → sprawl.
Anti-pattern
!
Why villages get overcrowded
Creating a house is two clicks, so people do it constantly — one per project, per client, per "let me just spin something up." Each quietly provisions a SharePoint site, a mailbox, a calendar and a Planner. The cost of a house is hidden, but real.landlord
🗺️Dig deeper: what the "village" actually is landlord⌄
The village is your Microsoft 365 tenant — the single boundary holding every identity (in Entra ID), every Team, every SharePoint site, every mailbox and OneDrive. One tenant = one village.
Houses (Teams) are peers — there's no "main house." You can be a resident of many, a landlord of a few.
Your own home (OneDrive) is a personal SharePoint site that belongs to you — which is exactly why shared work shouldn't live there (see Storage).
Guests come from another village. External access = two villages phoning each other; a shared channel = a room two villages share.
Now let's move into one house. The next stops set up a single Team properly. Repeat them for any house you own.
Stop 3 · Move in
Build the house & its rooms
House & rooms=Team (M365 Group) + Channels
Before carrying a box in, decide what the house is, who holds the keys, and which rooms it needs. This is the architecture step most teams rush and regret.
This whole stop is mostly the access lever…with rooms setting attention streams
i
Why this matters: a Team is one Microsoft 365 Group — a whole house with its own storage, calendar and membership (both dimensions, bundled). A channel is a room inside it. Build a new house only for a genuinely separate group of people; otherwise add a room. Two keyholders keep the house from being locked when one person leaves.
House or just a room? the core decision
🏠 New house (Team) when…
A distinct group of people needs its own space (new access boundary).
Membership & lifecycle differ.
It outlives a single project.
🚪 New room (channel) when…
The same people need a new topic (new attention stream).
You'd otherwise duplicate a house.
A locked room (private channel) only if access differs.
Anti-pattern — "house sprawl": a new Team for every little topic. Instead: add a room when the residents are the same.
!
The #1 first-timer mistake
Treating a Team like a chat group — raising one to message five people, not realizing you just provisioned a SharePoint site, a mailbox, a calendar and a Planner. A Team is a building, not a conversation.
🏗️Dig deeper: what gets built when you create a Team landlord⌄
"Team" is the face of a Microsoft 365 Group. The moment you click Create, Microsoft provisions — across both dimensions — all of this at once:
Files: a SharePoint site, a Planner plan, a OneNote notebook.
Comms: a group mailbox & shared calendar.
Identity: an entry in Entra ID.
That's why "just make a Team" is never free — each multiplies your governance surface. It's also why General can't be deleted: every house needs one room, mapped to the root of the site.
Room types — and a hidden cost standard · private · shared
The difference isn't just who's invited — it's where the files physically live (the files dimension again).
🚪 Standard
A folder in the house's main closet. Everyone in the house can reach it.
Folder in team site
🔒 Private
Its own separate closet in another building — only channel members, not even owners.
Own SharePoint site
🤝 Shared
Its own closet too, openable to people from other villages (tenants).
Own SharePoint site
💡
The implication landlords miss: every private and shared channel spins up a whole separate SharePoint site — not a folder. Ten private channels = ten extra sites to secure and report on. Use them deliberately.
🔍Dig deeper: private-channel mechanics & a 2025 change landlord⌄
A private channel's site is genuinely isolated: parent-team owners have no access unless they're channel members. Teams keeps membership in sync, and restores the site within ~4 hours if it's deleted directly in SharePoint while the channel exists.
Changed late 2025: as private channels moved to group-level compliance, newly created private channels no longer get a separate document library by default — the site root holds new files. Older ones keep their structure. You also can't convert standard↔private.
Removing the house removes the SharePoint site, files, OneNote, Planner and mailbox — not just the chat. There's a ~30-day soft-delete, but don't rely on it. Archive dormant Teams instead — read-only, everything intact.
🔑
Why two keyholders, really: it's not bureaucracy. Two owners means the house survives someone being on leave or leaving the org, member changes don't get stuck waiting on one person, and lifecycle decisions (archive, renewal) never block. Owners aren't just admins — they're responsible for keeping the house livable. landlord
Your house plan fill in
The house
Move-in checklist
The rooms (channels) your floor plan
One row per room. Two examples are filled in — edit or replace.
Room / channel
Purpose
Type
Who's in? (access)
Who's notified? (attention)
Stop 4 · The two-twins rule
Chat vs channel is OneDrive vs SharePoint
One decision, made twice=mine & by-hand · vs · ours & by-place
Two questions trip up every new user: chat or channel? and OneDrive or SharePoint? Here's the secret — they're not two lessons. They're the same decision seen in each dimension. Learn it once and you've learned both.
Signature diagram placeholder
⊞
The 2×2 — the signature visual of the whole workbook
Axes: personal ↔ shared (horizontal) × communication ↔ files (vertical). Top-left quadrant pairs Chat + OneDrive ("mine, by hand"); bottom-right pairs Channel + SharePoint ("ours, by place"). Diagonal arrow linking the two "same idea" corners. This image should recur as a small motif on later stops.
The principle, once then applied twice
Feels like
Four different tools to learn — chat, channels, OneDrive, SharePoint.
Actually
One distinction, twice:personal & shared-by-hand vs shared & shared-by-place — in the comms dimension and the files dimension.
In the communication dimension chat vs channel
A chat belongs to people. A channel belongs to a place. That one line generates every difference:
💬 Chat — belongs to people
Owned by the individuals in it.
New people see no history.
Not searchable by the team; can fracture when someone leaves.
Access: hand-picked, frozen. Attention: just those people.
📋 Channel — belongs to a place
Owned by the house (the Team).
New members get the full history.
Searchable; survives anyone leaving.
Access: inherited from the house. Attention: addressable (@person / follow).
In the files dimension OneDrive vs SharePoint
Feels like
Two different products to learn separately.
Actually
OneDrive is SharePoint — a personal SharePoint site, one library, owned by you. Same engine. The only difference is whose it is.
🗄️ OneDrive — "my stuff"
Owned by you; default audience is just you.
You extend access by hand, link by link (like chat).
Doesn't survive you leaving.
Your own private home.
🚪 SharePoint — "our stuff"
Owned by the house; everyone in the team already has access.
Access is inherited by place (like a channel).
Survives anyone leaving.
The house's shared closets.
💡
The reveal: they're the same choice. Pick chat → your files default to OneDrive ("mine"). Post in a channel → files default to SharePoint ("ours"). You're not making two decisions — you're making one, twice.
The one rule for the wall memorize this
Disposable + personal → Chat + OneDrive. Shared + lasting → Channel + SharePoint. Stop asking two anxious questions. Ask one calm one: "Is this mine and throwaway, or ours and lasting?"
What getting it wrong actually costs real failures
The pain
What happened
Lever misused
"The file's gone since Anna left."
Shared in chat → lived in Anna's OneDrive → deleted at offboarding.
chat for shared
"I just joined, can't see the backstory."
History was in chat, which has no shared memory.
people not place
"Which version is real?"
Copies emailed around instead of one SharePoint file.
bypassed SharePoint
"Nobody can find what we decided."
Decision made in a DM, never surfaced to a channel.
wrong attention
!
The file-in-chat trap
When you share a file in a chat it goes to your personal OneDrive ("Microsoft Teams Chat Files"), not the team's storage — and you've made yourself a single point of failure. Late joiners don't get it; if you leave, links break. Significant files belong in a channel.resident
🗂️Dig deeper: the offboarding break & meeting recordings landlord⌄
Chat files upload to the sender's OneDrive and share a link with whoever's in the chat at that moment. Consequences:
Late joiners get nothing — Teams warns the sender, but people miss it.
Offboarding breaks links — when the sender's OneDrive is deleted/reassigned, recipients can lose the file.
No central control — admins can't manage chat-file permissions from a team site.
Bonus: a channel meeting recording lands in that channel's SharePoint (shared); a chat/calendar meeting recording lands in the recorder's personal OneDrive — and can leave with them.
Closets & your drawer=SharePoint & OneDrive (the files dimension)
You met the principle at the last stop — now apply it to files specifically, so nobody ever asks "which copy is real?" This stop is the files dimension in depth.
"My stuff" (OneDrive) → access by hand"Our stuff" (SharePoint) → access by place
Rule of thumb: Personal drafts → your drawer (OneDrive). Shared work → the closet (Teams/SharePoint). Stable official knowledge → the library (intranet/knowledge base). Legacy drives → the attic (archive only).
Diagram placeholder
🏠
"One engine, two front doors"
A single storage engine (SharePoint) drawn as a building, with two labelled doors: "OneDrive — my home" and "Team site — our house." Shows they're the same structure, different ownership.
💡
The model that ends the confusion:OneDrive = my home, SharePoint = our house. A file's home follows its ownership, not convenience. The question is never "which app?" — it's "whose file is this?"
What you gain in the closet SharePoint superpowers
🔁 Co-authoring
Several people edit one file at once — no conflicting copies.
🕓 Version history
Every save is restorable — this is what makes _final_v2 unnecessary forever.
🔎 Findability
Search across the whole site, not one person's folders.
!
The folder-depth mistake from the network-drive era
People rebuild folders six or seven levels deep. In SharePoint that breaks findability and defeats the point. Keep it shallow — two levels max — and lean on search and channel structure. resident
🏛️Dig deeper: one engine, three front doors landlord⌄
Under the hood, M365 file storage is all SharePoint:
OneDrive = a personal SharePoint site (one per user).
A Team's files = a standard SharePoint site, a folder per standard channel.
Each private/shared channel = its own separate site with its own quota.
Quota implication: OneDrive is per-user and doesn't count against the tenant SharePoint pool; team and channel sites do. Scattering shared work into OneDrives hides storage consumption from tenant reporting.
This is where both dimensions pay off. A working room connects the talking (channel posts) to the keeping (notes, files, tasks) so context never scatters.
The five systems of a working room the pattern to remember
Diagram placeholder
🔗
The five-part loop
A connected loop: Channel (context) → OneNote (decisions) → Files (documents) → Planner (tasks) → Channel post (visible update) → back to Channel. Show comms-dimension nodes in teal, files-dimension nodes in amber.
💬 Channel
The context. One topic, everything in place. (comms)
📓 OneNote
Notes, protocols, decisions. (files)
📁 Files + 📋 Planner
Documents & tasks with owners. (files)
See it in a real house examples
📅
The calendar surprise: there's no standalone "Team calendar." Every channel calendar is a filtered view of the single M365 Group calendar behind the house — which is also why private/shared channels can't have one.
!
Where teams lose their decisions
Decisions get made in a meeting, mentioned in chat, then evaporate. A decision not written in the journal didn't happen. Fix: a fixed OneNote protocol section, updated live, with action items pushed to Planner.
🧰Dig deeper: OneNote vs Planner vs Lists vs Loop landlord⌄
OneNote — narrative & memory: notes, decisions, context. The why.
Planner — accountable work: one owner, a due date, a status. The who/when.
Lists — structured records you'd want columns for (risks, assets, requests).
Loop — a live snippet that stays in sync wherever pasted.
Pick one home per kind of thing; link the rest. Planner tasks also surface in each person's To Do / Tasks app.
Naming note (current): "Planner" is now the unified app — Microsoft retired Project for the web in Aug 2025 and folded it in, so today's Planner spans simple task boards up to premium project plans. For a Move-In team, the free task-board level is all you need.
Guests from another village=Guest access & external collaboration
Sometimes you invite people from another village in. Decide who gets a guest key to the house, who you just meet on the porch, and — crucially — when to take the key back. This stop is the access lever, extended outside your village.
Guests are pure access-lever decisions
i
Why this matters: a forgotten guest key is a real security gap. Guests can see whatever room they're in — so keep internal-only matters in a private room, and review the guest list on a set cadence.
Guest key or porch visit? access types
🔑 Guest key (guest access)
Ongoing work where they need files too.
They join rooms, calls, see shared files.
An account you now own — and must remove later.
🚪 Porch visit (external access)
Occasional chat or a one-off meeting.
No file access, no membership.
Nothing to clean up afterward.
Anti-pattern — orphaned guests: keys left with people long after the work ended. Instead: set a review date now and prune the list.
⚠
Assuming guests only see "their" channel
A guest added to the Team can see every standard channel in that house. If some rooms are internal-only, they must be private channels — or the guest belongs in a separate house built for the collaboration.
🔐Dig deeper: guest vs external vs shared channel landlord⌄
Guest access creates a guest object in your Entra ID; they sign into your village, join specific houses, see files. An account you must review and remove.
External access (federation) connects two villages for chat/calls/meetings — no guest account, no file sharing.
Shared channels (Teams Connect) — collaborate with another village's users without making them guests, but the channel has its own SharePoint site and membership. And channel membership ≠ team membership — each is managed separately.
There are a hundred ways to use Teams — but you don't need a hundred. A handful of proven setups cover almost everyone. Each is just the architecture you've learned, arranged for a situation. Use the picker, or browse and choose.
i
Why patterns beat freedom: a blank house is paralysing. Starting from a known-good layout — then adjusting — is how good teams move fast. You can always grow from a simpler setup to a richer one; that's the point of the ladder.
Help me choose answer 3 → recommendation
1 · How big is the team?
2 · What kind of work?
3 · Comfort level with Microsoft 365?
Recommended starting point
—
The setups simple → advanced
A ladder. Most teams live happily on The Classic; climb only when you feel the need.
Recommended
🍃
The Lean
Level 1 · minimal
For: tiny or short-lived teams. A working group, a quick project.
1–2 channels, chat-forward
Files in the channel
No Planner / OneNote yet
Outgrow it fast: move to Classic once you're >5 people or it lasts more than a few weeks — or decisions start getting lost.
Recommended
⭐
The Classic
Level 2 · the default
For: standard ongoing teams with recurring work. The 80% case.
Channel per workstream
OneNote per channel — notes & decisions
Planner per channel — tasks
Weekly recap post
The whole game: actually using OneNote + Planner, not just having them.
Recommended
🗂️
The Organised
Level 3 · structured
For: larger, document-heavy teams where things must be found later. Ops, HR, knowledge work.
Classic + naming conventions
Lists for structured tracking
Metadata & views, not deep folders
A pinned "start here" tab
Don't over-engineer: add structure only where search alone fails.
Recommended
⚙️
The Automated
Level 4 · workflows
For: repeatable processes — approvals, intake, recurring reporting. Same steps every time.
Organised + Power Automate flows
Forms for intake
Approvals & scheduled posts
Templated channels
Automation debt: someone must own the flows. Start with the one that hurts most.
Recommended
🧭
The Hub
Level 4 · connected
For: teams coordinating across many other tools — Jira, CRM, DevOps, a wiki. Teams as the front door.
Classic + apps & Power Automate Workflows as tabs
Links out to systems of record
A clear "what lives where" map
Link, don't duplicate
Tab sprawl: keep only what's actually used weekly.
Diagram placeholder
🪜
The setup ladder
A simple ladder/staircase: Lean → Classic → Organised → Automated/Hub, with "most teams live here" marking the Classic rung. Reinforces that you climb only when needed.
Your chosen setup locked in
Stop 9 · Housekeeping
Keep the house livable
Housekeeping=Operating rhythm & lifecycle
A house you never tidy becomes unlivable. A short, regular rhythm keeps both dimensions clean — conversations findable, files current, access boundaries tight.
i
Why this matters: without housekeeping every workspace decays — dead rooms, stale files, forgotten guests. A 10-minute monthly tidy is what moves a team from "we have Teams" to "Teams works for us."
⏳
Houses can expire: if your org runs a Microsoft 365 Group expiration policy, an inactive Team can be auto-deleted unless an owner renews it. Exactly why two keyholders matters.
♻️Dig deeper: archive vs delete vs expire landlord⌄
Archive — read-only; everything intact and searchable. Reversible. The right default for a finished project.
Delete — the Group and everything attached goes (~30-day soft-delete, then gone).
Expire — inactivity triggers auto-deletion unless renewed. Set the policy and watch for renewals.
Pair a quarterly archive sweep with the two-owner rule so renewals never fall through.