How to Uninstall TeamsMaestro AI Meeting Notes
Removing TeamsMaestro from Microsoft Teams involves the app itself, any calendar connections and account-level access. Here is how to work through each step and document your team's approved meeting-assistant policy.
Updated 4 min read
TeamsMaestro is an AI meeting notes tool that works inside Microsoft Teams. If you want to stop using it, the steps cover uninstalling the app from Teams, removing any calendar connections, and reviewing account-level access so the tool no longer operates in the background.
Whether you are removing it for one user or enforcing a team-wide policy, recording the decision in a shared place matters. A tool like fenbs keeps your team's approved meeting-assistant rules visible so the next person who joins knows what is permitted.
Remove the app from Microsoft Teams
To uninstall TeamsMaestro, go to the Apps section of Microsoft Teams. Find TeamsMaestro in your installed apps and select the option to uninstall or remove it. The app will stop appearing in your Teams interface. For current steps, check the Microsoft Teams apps documentation (opens in a new tab) since the interface may change between product updates.
If you installed TeamsMaestro through your organization's app catalog, an administrator may have deployed it for the workspace. In that case, a personal uninstall may not be available, and you will need to contact your IT administrator to have it removed at the organization or user level.
Check calendar connections
AI meeting notes tools often connect to a calendar so they can join meetings automatically. Uninstalling the app from Teams may not remove the calendar connection. Check your Microsoft 365 account settings or the TeamsMaestro account settings directly to see whether a calendar connection is still active.
To review connected apps in Microsoft 365, go to your Microsoft Account settings and look under Connected Apps or Third-party integrations. Remove any active TeamsMaestro connections you find there.
If TeamsMaestro was authorized through an OAuth flow, revoke that authorization. The exact location depends on how it was set up, but Microsoft Account settings at myaccount.microsoft.com (opens in a new tab) is a good starting point.
Review account-level access
Some meeting assistant tools request permissions at the account level when they are first set up: access to read calendar events, join meetings, or store recordings. After uninstalling, it is worth checking whether those permissions are still active.
In Microsoft 365, an administrator can review which third-party apps have been granted permissions across the tenant through the Microsoft Entra admin center. Individual users can also check their own connected app list. Remove any TeamsMaestro entries you find.
If TeamsMaestro stored meeting recordings or transcripts, check whether those are retained in a connected storage location and decide whether you need them deleted. The tool's own settings or their support documentation will describe the data-retention options.
Set a team policy for meeting assistants
If you are removing TeamsMaestro because it was installed without clear team agreement, this is a good moment to write the policy that should have existed first. Which meeting assistants are permitted? Under what conditions may a call be recorded? Who must be informed before a recording starts?
A short written policy prevents the same situation from recurring when a different tool is proposed. It also gives everyone in the team a shared answer when a client or external participant asks whether the meeting is being recorded.
Your policy should cover retention as well as access. If meeting notes are stored automatically in a cloud account, decide how long they are kept, who may access them, and who is responsible for reviewing them. When a team member leaves the organization, their meeting notes and any connected accounts should be reviewed and either transferred or deleted according to your retention policy.
When you introduce a new team member, include the meeting-assistant policy in their onboarding materials. Tools like TeamsMaestro are easy to install and quick to set up; a policy that arrives after the first meeting is harder to enforce than one that is shared at the start. New members should know the approved tools and the conditions for using them before they join their first recorded call. If your team hosts external participants, the policy also tells you what to say when those participants ask whether the call is being recorded or transcribed.
For a comparison of meeting note takers and how to choose one, see AI meeting note taker.
Document your team's meeting-assistant policy
Write the approved tools and recording rules as Decisions in fenbs. Team members and connected AI apps read those rules first, so the policy is visible the next time someone installs or proposes a meeting tool. When the policy changes, the reason is recorded alongside the new decision.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account. Start a project for AI governance or team tool policies.
- Add a Decision stating which meeting assistants are approved, any conditions on recording, and what to do when uncertain.
- Add a task to review meeting tool permissions quarterly. Keep a next-step note so the review stays on the agenda.
- Connect your AI apps over MCP from Integrations so they read the policy before answering questions about meetings.
- When a new meeting tool is proposed, add a task to evaluate it and record the outcome as a Decision.
A personal board is free and a good place to start tracking your own tool decisions and governance notes. A team board gives each member a clearly defined role with appropriate access and keeps the full History of every policy change, so you can see precisely who updated the meeting-assistant rules and when.