Welcome to the M365 FM podcast, where we explore the people, ideas and technologies shaping the future of work. The tracking spreadsheet everyone is afraid to touch. Here's what happens when a messy tracking spreadsheet becomes a Microsoft list. The rows stay, but the chaos goes because every column now knows whether it holds a name, a date, a price, or a status. You don't need to be an admin or write any code, since lists comes with the Microsoft three hundred sixty five plans that include SharePoint, it shows up in the lists app in SharePoint and right inside teams. So the data lives where your team already works. By the end, you'll know what it is, how to start one, where it fits, and the limits that trip people up. Welcome to the M365 FM podcast where we explore the people, ideas, and technologies shaping the future of work. Most of us have met this spreadsheet. Someone owns it, everyone edits it. And by Friday there are four copies with slightly different numbers. The problem was never the people, because a spreadsheet was never built for a team to share. At the same time, that gap is exactly what this episode is about, what Microsoft lists actually is. So let's answer the question plainly. Without the jargon. Microsoft Lists is a shared table for tracking information built right into Microsoft three. Sixty five Microsoft describes it as a way to organize, collaborate, and share the information you care about, and that's a fair summary of what it does. If you've used SharePoint before, you've already met the idea lists is the modern, friendlier way to build a SharePoint list, and it arrived as its own app back in August twenty twenty. Before that, the same feature existed, but it lived inside SharePoint sites and was harder for a beginner to find. The part that matters is where the data lives. Every list is stored in SharePoint, which is the same place your Microsoft three hundred sixty five files and team sites already sit. That means your list inherits the sharing and permissions you already understand. Instead of creating a whole new system, you have to learn from scratch. A list is a collection of data you share with your team and anyone else you give access to. You can open it from the lists app, from a SharePoint site, or as a tab inside Microsoft Teams. It's the same list seen through three doors, and nobody ends up working in a separate copy. What people actually track with. It covers a wide range support teams, track issues. IT teams, track laptops and monitors, marketing teams, track content ideas, HR teams, track new hires and event planners, track sessions and speakers. The common thread never changes. It comes down to several people, the same structured information and a need to see it live. Now, a list isn't a spreadsheet, and it isn't a database either. It sits in the middle as a shared tracker with structure, and that middle ground is where it earns its keep. Picture a small support team that lives in a spreadsheet today. One person logs the ticket, someone else updates the status, and the third person keeps asking which version is current. Put that same work in a list and everyone opens the same live view. There's no emailing, no version names, and no guessing which file is real. That's the promise of the tool, and it's a modest one, a single, shared, structured place for the information. Your team keeps passing around. Three easy ways to start your first list. Getting started is easier than you might expect, because you don't have to design anything from a blank page unless you really want to. There are three ways to begin, and each one fits a different situation. The first is from scratch. You create an empty list, then add the columns you need one at a time. This is the right choice when you already know exactly what you're tracking, and you'd rather build it your own way. The second is from a ready made template, and this is where a beginner should start. Microsoft ships a set of templates with pre-built columns, formatting, and structure already in place. There's an issue tracker, an employee onboarding checklist, an asset manager, a content scheduler, an event itinerary, a recruitment tracker, a travel requests list, and a work tracker. Pick the one closest to your job and you're already most of the way there. Take the issue tracker as an example. It arrives with columns for priority status and the person assigned plus two rules already built in that email. The right person when an issue lands on their plate. You didn't build that. It's just there waiting for your first item. The third way is to turn an existing spreadsheet into a list. If your team already tracks something in Excel, you can bring that data across and keep the columns you've been using. You don't lose your history and you don't start over. Bringing a spreadsheet across is more forgiving than it sounds. Microsoft reads your columns, guesses the types, and lets you fix anything it gets wrong before you commit. If a column full of dates arrives as plain text, you change it in a single click. Your data comes with you, and the list takes over from there. So the honest advice for a first list is simple start with a template, rename it to fit your team and add or remove columns as you go. You can always change your mind later because a list is never locked in place. Keep one number in the back of your mind as we go. It's the one that catches almost every new user off guard, and it decides how far a list can grow. Before you need a different tool, we'll come back to it. Columns are where the real difference shows up. What separates a list from a spreadsheet comes down to columns, and it's worth slowing down for. In a list, every row is an item and every column is a field with a type. A column isn't a blank cell waiting for anything. You drop into it. You tell it what it holds when you create it. The choices cover most of what a team tracks. You get text a choice from a short list, a person, a date and time, a currency amount, a number, a yes or no, a link, an image, a location, and a lookup to another list. Getting the type right early saves real pain later. If a date column keeps the wrong type, you lose the calendar view and the sorting that comes with it. If you leave a status column as free text, you get six spellings of the same word and a filter that can't find anything. The column type is a small decision that pays off every time someone opens the list. The type matters for a practical reason. A choice column gives people a drop down, so nobody types in progress five different ways. A person column knows it's holding a real person, complete with a photo and a click through to their profile. A currency column does math, and a date column can drive a calendar. The data stays clean because the column itself protects it. The lookup type is the one that surprises people. It creates a relationship between two lists. Say you have a list of projects and a list of tasks, instead of retyping the project name on every task. The task uses a lookup column that points back to the project. Change the project once and every related task follows along. This is the honest difference from Excel. A spreadsheet cell holds anything you put in it, which is exactly why spreadsheets drift over time. A list column holds what you told it to hold, so the structure survives contact with real people. And because every item has a type, you can filter, sort, and group on that structure later without cleaning up a mess. First one list many ways to see it. Once your data is clean, the next question is how you want to look at it. And this is where views come in. A view is a saved way of seeing the same list. It decides which columns show how the items are sorted, how they're grouped, and which ones are filtered out. You can make as many as you need and switching between them takes a single click. There are a few shapes of you can take. The grid is the familiar table and it's the default. The calendar view takes anything with dates and lays it out across a month, which is perfect for the event itinerary template. The gallery view turns each item into a card so it works well for photos or an asset directory. The board view gives you columns. You drag items between, which is great when status is the thing you care about most. Picture the same event list used two ways during planning. You live in the grid view checking speakers, rooms, and capacity. On the day itself, you switch to the calendar and see the whole schedule. At a glance, it's the same data, but two completely different experiences. Filtering is the other half of this. The filter pane lets you narrow a long list down to just what matters. Almost like shopping online, filter to your own items, or to everything that's blocked, or to everything due this week. Sorting and grouping work right alongside filtering. You might sort by due date so the nearest deadlines float to the top or grouped by owner so each person sees their own section. Save that arrangement as a view, and the next person who opens the list gets the same clean picture without touching a single setting. Formatting is what brings the list to life. You can color code a status column, so blocked items glow red or flag a whole row when a due date slips. None of this changes the underlying data. It just makes the important things impossible to miss. An HR team gets a lot out of this. Their onboarding list can show only this week's tasks in one view, only the tasks with no owner in another and a color coded view where anything overdue turns red. It's one list that answers three different questions at a glance when the list starts working without you. Now, for the moment, that makes people lean in. A good list doesn't just sit there waiting for you to update it. It can start doing work on its own. The simplest version is a rule. Rules are a no code feature that sends an email when something specific happens on the list. Add a new issue and the assigned person gets a notification. Change the status to blocked and the right person hears about it right away. You set it up once and it runs without you. Rules replace the older alerts feature and there are a lot friendlier to build. The next level is Power Automate, where a rule handles a single notification. Power automate connects your list to a whole workflow across Microsoft three hundred sixty five and beyond. A new item can trigger a sequence that updates another list, posts to a teams channel, sends an approval, and logs the result. If you've ever wished a spreadsheet could just handle the boring part for you, this is that wish answered. Then there's Power Apps, which lets you customize the form people fill in when they add an item. Instead of a plain form, you can build something that looks and behaves like a real app without leaving the list behind. Microsoft builds this right into the list. You open the item form, choose to edit it, and customize it with Power PowerApps. Approvals are the last piece, and they're surprisingly useful. You can send an item for approval and track the decision right inside the list. Think about a travel request list. Someone submits a trip, the manager gets asked to approve it and the status updates. Once they decide there's no separate email thread, no lost request, and no wondering who dropped the ball. Here's a small end to end example a new item lands in your issue tracker. A rule emails the assigned person, and power automate adds a card to the team's teams channel. When the issue is marked done, a second flow updates a summary list that the manager checks on Monday morning. You built none of that busywork. The list and its flows did it for you. Where lists fits in Microsoft three hundred sixty five. Before we get to the limits, let's zoom out and see where list sits because it doesn't live alone. Underneath everything, your list lives in SharePoint. That's why sharing permissions and version history behave the way they do. It's also why you can hand someone access to a single list, or even a single item without opening up everything else. The data is a SharePoint list wearing a friendlier face. Inside Microsoft Teams, you can add a list as a tab so your teams team's conversation and the data it's about sit side by side. That one move is often what turns a list from a side project into the place your team actually works. There's a personal side too. You can keep lists of your own through OneDrive, so your private trackers don't sprawl across team sites where they don't belong. When you outgrow the list view, you have somewhere to go. You can export the data to Excel to CSV or straight into power BI for heavier analysis. And because lists is part of the power platform, Family Power Automate and Power apps are always within reach, there's one more connection worth naming. A list can act as the data source for a power app, which means a team can work through a friendly screen while the list holds the records underneath. That's how a simple tracker grows into something that feels like a purpose built tool without a developer in the room. Now, the Azure question answered honestly lists as a Microsoft three hundred sixty five app, not an Azure service. You go and set up. It runs on Microsoft's cloud and through the power platform, it can reach Azure Site tools, but you never have to touch Azure to use it. If you're a beginner, that's good news. There's nothing to provision and nothing to configure in the cloud before your first list. As for cost lists is already included in the Microsoft three hundred sixty five subscription. That gives you SharePoint, and there's a free personal preview. If you want to try it with a Microsoft account, chances are it's already sitting in the account you have open right now. The limits nobody wants you about. This is the part that saves you from a bad afternoon, so let's be straight about it. Microsoft says you can store up to thirty million items in a list or library. That number sounds enormous, and it is, but it's not the number that matters day to day. That number I asked you to hold on to shows up right here and it's about five thousand. It's called the list view threshold. And by default it sits around five thousand items. When a view has to work with more than that at once, the view can fail to load and throw an error. Microsoft starts warning you on the list settings page. Once you pass three thousand items, which is your cue that the list is getting big. The limit exists for a reason. The list sits in a shared database, and locking too many rows at once slows the whole system down for everyone, so Microsoft throttles it on purpose. The exact number can shift with activity and configuration, so treat five thousand as a rough line rather than a law of physics. A few other ceilings are worth knowing. An individual file or attachment can be up to ten gigabytes, which is plenty for most teams. Unique permissions are capped at fifty thousand per list, though Microsoft recommends staying near a five thousand and lookups have a join limit of twelve, so you can't chain unlimited relationships between lists. None of this should scare you off your team list. Probably never comes close to these numbers, and the ones that do usually belong in a different tool anyway. So the practical rule is this. And it's the honest one. A list works best for tracking hundreds or a few thousand shared rows, not for millions of rows of analysis. When a list starts to strain, you have moves. You can index the columns you filter on, build narrower filtered views, split the data across folders, or send the heavy analysis to Excel or Power BI. Knowing that ahead of time is the difference between a tool that works and a tool you blame the mistakes beginners make and what to do instead. With the limits in mind, beginner problems come down to a handful of predictable mistakes, and every one of them has a simple fix. The first is treating lists like Excel. People import a giant analysis spreadsheet, hit the view threshold, and decide the tool is broken. It isn't broken. Lists is for shared tracking, not for crunching numbers. And the moment you need real analysis, you export to Excel and let it do that job. The second mistake is using lists for personal to do lists for your own tasks. Microsoft to Do and planner are the better fit. Save lists for the shared structured information your team needs to see together. The third is building one giant list for everything that feels efficient at first, but it turns into a list with forty columns that nobody wants to open. Build a few focused lists instead and connect them with lookup columns when they relate. The fourth is waiting until a list gets slow before doing anything about views and indexes, set up a filtered view early. Add indexes to the fields you sort on, and the list stays quick as it grows. There's a fifth mistake that's less obvious. People build a list and then never tell anyone it exists. A tracker only earns its keep when the team knows where it lives and how to use it. So share the link early and pin it somewhere people already work. If you want a simple rule to carry with you, here it is. If several people need to update the same structured information and see it live, a list fits. If one person needs to crunch numbers in private, reach for Excel. The pain almost always comes from mixing those two situations up. That one distinction explains almost every complaint about the tool. People who expect a spreadsheet from a list feel let down, and people who need shared structure wonder how they ever managed without it. The short version and one question for you. So let's bring it together. Microsoft Lists gives your team one shared, structured place to track information inside Microsoft three hundred sixty five. It stores that data in SharePoint, keeps it clean with typed columns, shows it through flexible views, and can automate the busy work with rules in the power platform. It's not a spreadsheet and it's not a database. It's the middle ground your team keeps trying to build out of a flat file. My question for you is this. What's still living in a messy spreadsheet that a list might handle better if this made the topic feel less intimidating? Subscribe to M365 FM. To master the tools and the mindset shaping the future of work.