Montro

Microsoft Teams Collaboration Governance

Microsoft Teams is central to how your organisation communicates - and often overlooked in access reviews. Montro imports Teams users and licences so your collaboration platform is as governed as everything else in your estate.

01GDPR

GDPR

Microsoft Teams and GDPR - collaboration data is personal data

Microsoft Teams processes personal data on your behalf - user identities, email addresses, and account metadata. Under GDPR, your organisation is the data controller and Microsoft acts as a processor. A Data Processing Agreement must be in place. Connecting Teams to Montro brings user and licence data into Montro EU-hosted infrastructure under a separate DPA, with all data remaining within the EU.

Learn more →
02EU AI Act

EU AI Act

Microsoft Copilot in Teams and the EU AI Act - deployer obligations apply

Microsoft Copilot in Teams - meeting summaries, message drafting, conversation intelligence - is an AI system under the EU AI Act. If your organisation has Copilot enabled, deployer obligations apply: documenting its use, confirming the risk tier, and ensuring oversight is in place. Usage in HR, performance, or employee-facing workflows warrants review under Annex III. Montro surfaces Teams so Copilot usage is governed and documented.

Learn more →
03DORA

DORA

Microsoft Teams and DORA - collaboration tools belong in your ICT register

Under DORA, every ICT tool supporting your operations must be registered and assessed. Microsoft Teams, as a communication platform, is an ICT service that belongs in your ICT Third-Party Register under Article 28.3. Connecting Teams to Montro supports register completeness and gives you the visibility needed to meet DORA third-party risk obligation

Learn more →
04NIS2

NIS2

Microsoft Teams and NIS2 - communication tools are ICT supply chain

NIS2 Article 21(3)(d) requires organisations to document and assess the cybersecurity of their direct ICT suppliers. Microsoft Teams is a communication and collaboration platform that qualifies as an ICT service under NIS2. Connecting Teams to Montro brings it into your governed application inventory, supporting your supply chain security obligations and ensuring Teams is visible in any NIS2 compliance review.

Learn more →
05ISO 27001

ISO 27001

Microsoft Teams and ISO 27001 - evidence your collaboration controls

ISO 27001 Annex A requires documented asset inventories, access control policies, and user provisioning processes (A.5.9, A.5.15, A.5.16). Teams user and licence data in Montro gives auditors a consolidated, timestamped view of collaboration platform access and ownership - supporting the evidence requirements that ISO 27001 audits demand.

Learn more →

Discovery

What Montro discovers from Microsoft Teams

When you connect Microsoft Teams to Montro, the platform pulls user account data and subscription information into your governed application inventory. IT and security teams get a clear view of who has access to your Teams environment, how licences are allocated, and whether Teams is mapped against your EU compliance obligations.

Collaboration user visibility

See every Microsoft Teams user account tied to your organisation, including users provisioned outside your standard identity provider flow. Montro surfaces accounts added directly rather than through your governed onboarding process - giving you a complete picture of who has access to your collaboration environment.

Licence allocation

Understand how Teams licences are distributed across departments and identify seats that are assigned but inactive. Montro gives you the data to right-size your Microsoft 365 collaboration spend, reclaim unused licences, and ensure your allocation reflects actual usage across the organisation.

Subscription tracking

Teams subscription records are imported into Montro's Subscriptions module for renewal management and cost visibility. Track your plan details, licence counts, and renewal dates alongside every other SaaS and AI tool in your estate - so nothing renews without a governance review.

Onboarding and offboarding support

Montro keeps your Teams user records current, supporting onboarding and offboarding processes with an accurate, real-time view of who has access. Identify users who have left your organisation but retain active Teams accounts - a common access governance gap that creates both security and compliance risk.

Technical details

Authentication Method


Microsoft Teams authenticates through Microsoft's OAuth authorisation flow. Users sign in with their Microsoft account credentials and complete multi-factor authentication via Microsoft Authenticator before granting Montro access. 


How to Connect:


  1. Navigate to Integrations in your Montro dashboard.
  2. Select Microsoft Teams from the integrations catalogue and click Connect.
  3. Click Connect on the permissions screen to initiate the Microsoft authentication process.
  4. Sign in with your Microsoft account by entering your email address.
  5. Enter your password and click Sign In.
  6. Complete multi-factor authentication by opening Microsoft Authenticator and approving the verification request.
  7. Review the requested permissions, select 'Consent on behalf of your organisation', and click Accept.
  8. Montro begins synchronising Microsoft Teams data.
  9. Review synchronised records in the Users module (Teams user identities) and Subscriptions module (Teams subscription information).


Data Synced

Users Module

Microsoft Teams user identities, including email addresses and account access information.

Subscriptions Module

Teams subscription records, licence counts, and user allocation details.


Data Residency


Microsoft Teams data imported into Montro is stored on AWS Frankfurt (eu-central-1), within the European Union. No customer data is transferred outside the EU. Data residency terms are specified in Montro's Data Processing Agreement.


Sync Frequency


Data can be synchronised manually at any time after the initial connection, with no limit on the number of manual syncs. Montro also provides an automatic sync option - when enabled, the platform synchronises data once every night to keep information current.


Permission Scope


Montro requests read-only permissions from Microsoft Teams, scoped to user account information and subscription data. Montro does not request access to Teams messages, chats, meeting content, files, or channel conversations. Administrator consent on behalf of the organisation is required during setup. All permissions are the minimum required for SaaS and AI governance visibility.


EU Data Storage


Montro's infrastructure runs exclusively on AWS eu-central-1 (Frankfurt), governed by Irish and EU law. There is no FISA 702 exposure and no Schrems II ambiguity. Your data is never replicated outside the EU without your explicit, documented consent. EU data residency is not a configuration option - it is the architecture.

Related

Apps commonly used with Microsoft Teams

Discover compliance profiles for tools in your stack.

Project & Knowledge Management

Jira External User Discovery & Governance

Jira accounts are where contractors, agencies, and external collaborators often live - outside your identity provider, outside your offboarding process, and outside your compliance picture. Connect Jira to Montro to bring them in.

Learn more →

Slack Workspace Access & AI Governance

Slack is where work happens, and where ungoverned access accumulates. Guest accounts, inactive seats, and users added outside your identity provider all show up when Montro connects to your workspace.

Learn more →

Zoom Governance & Compliance Discovery

Zoom accounts grow quietly - provisioned outside your identity provider, renewed without IT review, and rarely audited. Montro discovers every user and licence in your Zoom environment and maps it against your EU compliance obligations.

Learn more →
Ankur Arora

Ankur Arora

Co-founder

Fifteen years of enterprise digital transformation across telecoms, media, consumer goods, and agriculture - and a front-row seat to AI adoption outpacing governance at every organisation he worked in. He built Montro so the next firm doesn't have to learn that lesson the hard way.