The archive
Twenty-four practical pieces on Power Automate, Copilot, bots, integrations, and the smaller Teams habits that keep a workday from filling up with clicks.
None of these Microsoft Teams features are secret. They are just buried. I list the ones I show a new teammate in the first hour, and the one I stopped recommending because it confused more than it helped.
Continue reading →Presence in Microsoft Teams is a signal, not a surveillance score. I explain what each status actually does, how the calendar overrides you, and the custom message I set during focus time.
Continue reading →A new Microsoft Teams team feels productive for a day and expensive for a year. I lay out the channel rules I use so people can find last Tuesday’s decision without joining twelve more teams.
Continue reading →Marcus keeps a short list of Microsoft Teams shortcuts he actually uses, and he tells you to open the in-app sheet before you memorize a combo that changed when new Teams shipped.
Continue reading →Automation that nobody adopts is a hobby project. I track a week of repeated Microsoft Teams clicks, choose three, and describe the awkward conversation when the old manual path has to close.
Continue reading →Chat is a terrible ticket system and a fine front door. I show the Microsoft Teams workflow I use when a team wants tracking without standing up a separate tool they will not open.
Continue reading →Dropping a policy PDF in a Microsoft Teams channel is not the same as approving it. I wire the library, the approval, and the column I check before anyone treats the file as final.
Continue reading →People say they need to “sync Teams to SharePoint” when the file has been in SharePoint the whole time. I sort out what is already shared, what a flow should copy, and what it should leave alone.
Continue reading →An incoming webhook is the shortest path from another system into a Microsoft Teams channel, and the easiest secret to paste into a ticket by mistake. Marcus explains both sides and the rotation drill.
Continue reading →The Microsoft Teams calendar is not a task list, and a task list is not a calendar. I spell out what actually stays in step, and a small flow I use when a meeting ends with a real action item.
Continue reading →Pinning a plan to a Microsoft Teams channel is the easy half. The hard half is deciding which system owns the status so you do not update the same task in two places and trust the wrong one.
Continue reading →A CRM notice in Microsoft Teams is useful the first time a deal changes stage. It is noise the fifth time the same record saves. This is the filter I add before the channel will keep the app installed.
Continue reading →A wall of JSON is how adaptive cards get a bad reputation. I introduce the Microsoft Teams card I actually post: a status, an owner, and one button, then the two fields I stopped adding.
Continue reading →Someone asks for a custom Microsoft Teams app every time a flow feels ugly. Sometimes they are right. Here is the checklist I use before anyone opens a project and names it version one.
Continue reading →You can automate Microsoft Teams without a marketplace full of logos. These are the apps I install, or ask an admin to allow, before I write a single custom connector.
Continue reading →An echo bot teaches the plumbing and nothing else. I walk through a first Microsoft Teams bot that answers from a SharePoint list, including the admin consent step that stalled my own first install.
Continue reading →“Summarize this” is how you get a paragraph nobody acts on. These are the Copilot prompts I paste into Microsoft Teams, including one that failed until I told it the decision format I wanted.
Continue reading →The feature list in Microsoft Teams is longer than a team will configure. I pick three AI settings that pay for themselves in a week, and I write down the ones I leave off until someone asks twice.
Continue reading →A summary is only useful if the people who were not in the room can trust it. I compare the Microsoft Teams recap, the transcript, and a hand-edited channel post, including the time I almost shared a salary comment.
Continue reading →Copilot will draft the follow-up. It will also invent an owner if you let it. This is the sequence I use after a Microsoft Teams meeting so the recap becomes tasks a human has actually checked.
Continue reading →Most notification flows are how a channel gets muted. Marcus walks through a Microsoft Teams alert that posts only when a SharePoint status flips to Blocked, and the rules he uses before adding anyone else to the audience.
Continue reading →An approval that lives only in a chat thread dies when the approver is on a plane. Here is how I move that decision into the Approvals app, what I store, and when I still refuse to automate the judgment itself.
Continue reading →Not every click in Microsoft Teams deserves a flow. These six do, because the rule is stable and the cost of a missed step is a person chasing someone in chat. I have shipped each one more than once.
Continue reading →The first flow I trusted in a live Microsoft Teams tenant created forty-one Planner tasks before lunch. This is the smaller version I wish I had built, and the checks I run before a flow leaves the sandbox channel.
Continue reading →
