
Tool Overload
Part of Team communication integrations
Removing integrations that no longer serve a team safely
Retire stale chat integrations by checking dependencies, removing the right authorisations and verifying that messages and access have stopped.
Start with a safe-retirement audit
List every app, custom integration, webhook and connector touching your chat or collaboration platform. For each, record who installed it, who owns it now, the business process it supports, and the other systems it reads from or writes to. Build the inventory from admin tooling, not memory: people forget tools added years ago.
Record the install route: it decides who can act. On Google Chat work or school accounts, an administrator can install apps for users, and those apps can send people direct messages. Such apps behave differently from apps a person added to a conversation themselves.
Record the scope of each item. An app added to a Google Chat space can fetch basic information about that space and create messages in it. Teams app centric management assigns access to each app individually, either to everyone or to a selected set of users and groups.
Flag every integration with no living owner. These break without anyone noticing, because nobody receives its alerts and nobody knows which downstream process depends on it.
Pre-Removal Audit Checklist for Integrations
- List all integrations, webhooks and connectorsInclude who installed it, current owner, supported business process, and connected systems.
- Identify no-owner integrationsFlag any that lack a living owner—these often break silently.
- Record install route (user vs admin)Determine whether the app was added by a user or an administrator—this affects removal rights.
- Document data access scopeNote what information the app can read or write, including profile details and message context.
Separate user-installed tools from admin-controlled access
A person can uninstall an app they added themselves. In Google Chat, uninstall from a direct message via the app name at the top of the conversation.
Apps installed by an administrator are different. On work or school accounts you can't uninstall apps your admin installed. You can turn off notifications for conversations with the app instead.
Administrator action is required at another level too. In Teams, only Global Administrators can grant consent to an app's permissions on behalf of everyone in the organisation, so organisation-wide access can't be undone by the people who use the app.
Access can be narrowed rather than switched off completely. Teams app centric management lets an admin set an app to Everyone, or limit it to specific users and groups, including security groups, Microsoft 365 groups, dynamic membership groups, nested groups and distribution lists.
Space-level restrictions also exist. If you are an external member of a Google Chat space created by a work or school account, you can't add, remove or interact with any apps in that space.
Admin-Controlled vs User-Installed Apps in Google Chat and Teams
- Pros of Admin-Installed Apps
- Centralised control, consistent security policies, ability to enforce organisation-wide access.
- Cons of Admin-Installed Apps
- Users cannot uninstall them; only admins can restrict or disable them.
- Pros of User-Installed Apps
- Users can manage their own tools, tailor experience to personal needs.
- Cons of User-Installed Apps
- Risk of unauthorised or orphaned tools; harder to track dependencies and ownership.
Trace permissions and data access before revoking anything
Read what the app actually asked for before you cut it off. In the Teams admin centre, the Permissions column on the Manage apps page shows whether an app has permissions that need consent. A View details link lists the permissions and the access to organisational information the app requests.
Typical requests include reading information stored in a team, reading a user's profile, and sending email on behalf of users. The requirement to view details and grant consent applies to custom and third-party apps, not to apps provided by Microsoft.
Check what the app can reach in day-to-day use. An app in Google Chat can see your email address, avatar and basic information, and can see other people's basic information in a chat, but not their email address or avatar unless they interact with it directly.
Adding an app to a Google Chat space grants it access to the messages that triggered it, not to every message in the space; apps that need the full message context can only get it with explicit permission. Timing matters: revoking access before confirming this can silently cut off work the app was performing.
Third-party account access sits outside the chat platform. An app performing tasks on your behalf prompts you for permission to access your Google Account, and the vendor's terms of service and privacy policy govern what happens to that data. Removing the integration from a conversation does not by itself remove that account-level access, which is revoked separately.
Treat webhooks and connectors as special cases
A webhook is not an app, and it can't be managed like one. With this architecture users can't interact with the webhook or the connected external application, because communication is one-way; webhooks aren't conversational and can't respond to or receive messages from users or app interaction events.
A webhook is bound to a single destination. Each webhook only works in the chat space in which it is registered, and webhooks can't be published to the Google Workspace Marketplace. Incoming webhooks in direct messages work only when all users have apps enabled, and the organisation must permit users to add and use incoming webhooks at all.
In Teams, an incoming webhook lets external applications share content in channels and provides a unique URL for sending a JSON payload with a message in card format. These are typically used as tools to track and notify rather than to hold a conversation.
Connectors are being retired. Microsoft 365 Connectors are nearing deprecation and the creation of new ones will soon be blocked, with the Workflows app positioned as the more flexible and secure replacement. Anyone still building on Office 365 Connectors should migrate to Power Automate connectors or move the posting into a Teams app using proactive messages.
Migration has its own constraints. The Workflows app can post as a flow bot in shared channels, but posting as a flow bot in private channels is still under development. While Workflows support Adaptive Cards and Message Card format, button rendering isn't supported.
Because a webhook is tied to one space, replacing it means registering a new endpoint in each space it served, then updating the external system that calls it. Uninstalling an app won't do that work.
Incoming Webhooks vs Workflows App in Microsoft Teams
- Functionality
- One-way messaging; no interaction possible
- Management
- No user interface; managed via URL and JSON payload
- Future Support
- Being retired; new ones blocked
- Alternative
- Workflows app (Power Automate) – more flexible and secure
Plan for orphaned automations and ownership gaps
Automations often belong to a person, not to a team. Workflows are linked only to specific users, called the owners of the workflow, and not to a Teams team or channel. When the owner leaves and no co-owners were assigned, the flow becomes an orphan flow.
Before anyone leaves or an integration is removed, find every flow with a single owner and add one or more co-owners, which gives them full control over the workflow. This step keeps the automated business process continuous.
Administrators have two further levers on an orphaned workflow: adding authentication for connections, and enabling the flow if it has been disabled. Both are needed when the original owner's credentials were the thing keeping it running.
Apply the same test to automations outside the chat platform. Ask who holds the connection credentials, whose account the trigger runs under, and who receives the output when it fails.
Remove in stages and monitor for fallout
Stage one is to reduce visibility without breaking the connection. For an admin-installed app you can't uninstall, turning off notifications for conversations with the app is the available action, and it can be reversed if the app turns out to be needed.
Stage two is to remove the integration from the spaces and channels it serves, so it stops receiving triggers before the app itself is gone. In Google Chat that means removing the app from the space or, for a direct message, uninstalling it from the app name at the top of the conversation.
Stage three is to uninstall the app or delete the custom integration. Where the app holds access to an external account, revoke that separately, for example by removing third-party app access to your Google Account; where a workflow is involved, add co-owners first.
Stage four is monitoring. Watch the affected spaces and channels for missing posts, check the flows that were disabled or reassigned, and watch the external systems that used to call a webhook endpoint.
Keep the audit record current as you go: what was removed, when, who approved it, and what replaced it. That record is what tells you why a notification stopped three months later.
Safe Removal of Stale Integrations in Teams and Chat Platforms
- Stage 1: Reduce VisibilityTurn off notifications for admin-installed apps; this preserves functionality while reducing user disruption.
- Stage 2: Remove from Spaces/ChannelsUninstall app from Google Chat spaces or direct messages; remove from Teams channels to stop triggers.
- Stage 3: Uninstall IntegrationRemove the app or delete custom integration. Revoke external account access (e.g., Google Account) separately.
- Stage 4: Monitor for FalloutCheck affected channels, flows, and external systems for missing messages or failed automations.



