Bots & Custom Apps
Microsoft Teams apps worth installing for automation
Teams already ships with more automation surface than most companies use. Before anyone asks me to evaluate a marketplace full of shiny third-party tiles, I make them install and actually configure the first-party apps that sit next to the chat window every day.
I am Priya Shah, a Microsoft Teams automation consultant. This is an independent educational article. I am not a Microsoft partner, I do not earn affiliate fees from app installs, and Microsoft does not endorse this list. Use it as a practical tour of first-party options: Workflows and Power Automate, Approvals, Lists, Planner, Forms, and Files with SharePoint.
If an admin blocks an app, that is a governance signal, not a personal insult. I will cover what to do next without turning into a bypass guide.
Start with Workflows and Power Automate
In modern Teams clients you will see Workflows as the friendly doorway into Power Automate. Same family. Same connectors under the hood for many scenarios. The value is triggering work from a message, a channel event, a scheduled time, or another Microsoft 365 signal, then posting results back where people already work.
Install or pin Workflows for the people who will own automations, not for every employee on day one. Too many unused pins create clutter and support noise.
Good first automations are small. Notify a channel when a Forms response arrives. Create a Planner task from a tagged message. Post a daily digest of open Approvals. Avoid your first flow posting into the same channel it watches without a filter. I have told that story enough times that my friends finish the sentence for me.
Ownership matters. A workflow tied to one person’s connections will break when that person leaves. Prefer clear owners, shared connections where your governance model supports them, and a short runbook pinned in a sandbox channel.
Workflows will not replace every custom app. They will retire a surprising number of “we should build something” conversations if you give them two honest weeks.
Approvals: the automation people feel immediately
Approvals is first-party glue for yes, no, and comment. Used well, it removes the screenshot-of-an-email ritual that still haunts too many teams.
Install Approvals for groups that already have a repeatable decision: discount exceptions, access requests, content publishing, vendor onboarding steps that are not formal contract signature. Keep the request fields few. Title, requester, amount or scope, due date, link to evidence.
Wire Approvals to Power Automate when the decision should create a downstream action: update a List item, post a channel confirmation, grant a temporary access package through your identity process, or notify Finance.
What not to do: turn every casual question into a formal approval. Approval fatigue is real. People start clicking Approve to clear badges. Then you have theater, not control.
I ask sponsors one question before we standardize Approvals. What happens if nobody responds for three days? If the answer is “nothing,” you may need a reminder flow or a smaller audience, not a louder badge.
Lists and Planner: structure beats chat amnesia
Lists in Teams gives you a structured table living beside the conversation. It is ideal for intake logs, RAID items, equipment trackers, and content calendars that need columns, not vibes.
Planner is for task ownership with progress. Buckets, assignments, due dates, charts that managers actually open.
Install Lists when the team keeps pasting the same table into a wiki tab and watching it rot. Install Planner when work has owners and dates but keeps falling out of chat threads.
Automation angle: Power Automate can create List rows from Forms, create Planner tasks from Approvals, and post Adaptive Cards when a row changes status. The apps are the system of record. Chat becomes the notification layer.
Concrete example. A regional marketing team tracked campaign requests in a spreadsheet nobody trusted. We moved requests into a List with status, owner, launch week, and asset link. A simple workflow posted a card to their intake channel when status moved to Needs Creative. Planner carried the creative tasks. Chat stopped being the database. Request volume did not drop. Panic did.
Keep permissions tidy. A List that everyone can delete will eventually lose a row someone needed for an audit. Use views and permissions intentionally.
Forms and Files with SharePoint
Forms is still the cleanest way to collect structured input from people who should not edit your List directly. Embed or link Forms from a Teams tab. Send results into Excel, a List, or a flow.
Files in Teams is SharePoint under a friendlier name. Document libraries, version history, permissions, and metadata live there whether people realize it or not. Automation that moves files, waits on content approval, or posts when a new contract folder appears is really SharePoint automation wearing a Teams jersey.
Install and teach Files habits before you build exotic bots. Naming conventions, folder templates, and “do not store the only copy in chat” prevent more pain than a clever webhook.
Connect Forms to Files when submissions should attach evidence. Connect Files to Workflows when a new file in a library should notify a channel with a link, not an email attachment copy.
One caution. Forms is easy to overgrow. Twenty optional fields will tank completion rates. Start with the fields you will actually filter on later.
- Forms for intake.
- Lists for operational records.
- Planner for owned tasks.
- Files and SharePoint for durable documents.
- Approvals for decisions.
- Workflows to connect the dots.
A sensible install order for a new team
Day one: Files tab with a short folder template and a pinned README in the library.
Day two: Lists or Planner based on whether you need records or tasks. Sometimes both.
Day three: Forms for external or broad intake if needed.
Day four: Approvals for one decision type only.
Day five: one Workflow that connects two of the above.
That order keeps chat readable while structure arrives. Reversing it, starting with five workflows and no system of record, creates automated confusion.
Train with the team’s real work, not a fictional demo company. People remember the campaign request List. They forget Contoso Sample App 12.
When an admin blocks an app
First, read the block as information. Many tenants restrict third-party apps by default and even stage first-party rollout. Ask which policy applies: app permission policies, setup policies, conditional access oddities, or a deliberate business decision.
Second, document the business need in one paragraph. Which process, which data, which users, which alternative you already tried. Admins respond better to process language than to “everyone else has it.”
Third, accept alternatives when they are good enough. If Workflows is available but a marketplace connector is not, redesign around first-party connectors. That constraint often improves the architecture.
Fourth, never coach people to sideload around a block on production tenants. Sandbox sideloading with permission is different from shadow IT. I will help you write the exception request. I will not help you hide an install.
If the blocked app is first-party and still unavailable, check license assignment and whether the user is in the right group for the Teams app setup policy. Sometimes it is not a ban. It is an assignment miss.
Keep a shared note of what is approved. Teams spend weeks rediscovering the same “no” otherwise.
What I refuse to pitch
I do not rank third-party apps here. I do not drop referral links. I do not claim a tool will transform culture by itself. First-party apps earn attention because they inherit your existing Microsoft 365 permissions model and usually clear security review faster.
That does not mean third-party tools are bad. It means you should exhaust the boring suite before you expand the attack surface and the renewal surface.
Measure success by fewer lost requests, clearer owners, and shorter time from question to decision. If those numbers do not move after you install Workflows, Approvals, Lists, Planner, Forms, and disciplined Files use, a new logo will not save you.
Pin fewer apps. Configure the ones you pin. Connect them with one careful workflow at a time. When something is blocked, escalate with a process brief. That is the whole strategy, and it scales better than a shopping spree in the Teams store.
One more habit that helps after the first month: hold a thirty-minute cleanup. Unpin apps nobody opened. Archive unused Flows that still send test messages. Confirm the Lists and Planner boards still have owners who work there. Automation debt accumulates quietly, the same way chat debt does.
If a new hire asks which Teams apps matter for automation, point them at this first-party set and a single sandbox channel. Let them break things somewhere safe. Then promote only what survived contact with real work. That path is slower than installing everything on Monday. It is also how you end the quarter with tools people still trust on Friday.