MICROSOFT TEAMS SECURITY

Which Teams messages can an approved app send elsewhere?

An approved Teams integration can receive chat content through a Microsoft Graph subscription. Review the permission grant and the destination together.

An office worker wearing a headset while using a laptop.
Illustrative photograph. The person pictured is not connected with the research discussed.

An app owner asks to keep a Teams archiving integration. Which conversations can it read, and who controls the server that receives them? A permission review gives you the first answer. To get the second, inspect the integration’s active subscriptions.

In research published on 4 November, NetSPI demonstrated what can happen after an attacker gains control of an app with sufficient Microsoft Graph permissions. In its test, an application with the admin-consented Chat.Read.All permission created a subscription for Teams chat messages. Microsoft Graph delivered encrypted message content to the specified endpoint, where the recipient could decrypt it. Looking only for direct requests to read individual chats would miss that route.

Review the permission and the destination together

Ask the app owner to match each subscription to a business purpose, an approved destination and a named owner. Check whether the tenant collects GraphNotificationsActivityLogs and who would investigate an unexpected destination or renewal. If a subscription cannot be explained, investigate it before renewing approval.

Microsoft’s documentation explains how rich change notifications include encrypted resource data, the certificate information a receiving app needs and how Teams message subscriptions specify a notification endpoint.

Checks for an approved Teams integration

  • Confirm the Graph permissions granted to the application and why each is needed.
  • List the active subscriptions and identify the resource, destination, application and owner.
  • Compare every destination with the supplier architecture and the organisation’s approval record.
  • Review subscription creation, renewal and notification activity for unexpected changes.
  • Investigate an unexplained subscription before renewing the application’s approval.

For the wider review of external access, identity controls and applications inside Teams, read The fake help desk in Teams: why configuration matters.

Sources

Bring Teams application evidence into view

OpenGates, embedded in MobSTR, supports the application-assessment part of a Teams review through manifest, configuration, permission and data-handling analysis. Tenant administrators still need to review active Graph subscriptions, destinations and audit evidence in Microsoft 365.

Explore OpenGates with the MobSTR team ↗

← Back to all insights & news

LET’S MAKE APP RISK CLEARER

See what your
apps are really
up to.

Tell us what you need to protect. We’ll show you how MobSTR turns application risk into clear, informed decisions.

Mobile apps, browser extensions, Teams and privacy.
One conversation to get started.

We’ll use these details to respond to your enquiry. Read our privacy policy.

You’re in control. Your choice applies to this browser and can be changed using Cookie settings in the footer.

Read our cookie policy · Privacy policy

MobSTR video