Leexi on iOSLeexi on Android

Microsoft Teams and the GDPR: what your organization needs to verify

  • Hosting, retention, sharing, and Copilot: Microsoft commitments and settings to verify within your organization.
Try for free
Hosting, retention, sharing, and Copilot: Microsoft commitments and settings to verify to govern your Teams meetings.

Microsoft Teams documents data protection commitments and settings to govern your meetings. Their scope depends on your Microsoft 365 organization, the activated services, and your contract. Before recording, verify where files are stored, who can access them, and which rules apply to their retention. Teams storage and permissions. EU Data Boundary scope.

A file retained in OneDrive, a transcript used by Copilot, and meeting notes produced by a third-party assistant require distinct verifications. The storage location provides insight into part of the data journey. Documented processing, integrations, and exceptions complete this analysis. EU Data Boundary residual transfers. Copilot modes in Teams.

This page is published by Leexi. It is based on public Microsoft documentation, GDPR provisions, and Leexi's public DPA accessed on November 5, 2026. It describes the applicable framework and does not constitute legal advice. Settings and commitments must be aligned with your contract and your actual use.

Where Microsoft Teams hosts and processes your data

Storage of recordings and transcripts in OneDrive and SharePoint

For a standard meeting, the recording is saved in the organizer's OneDrive. A channel meeting uses the SharePoint associated with the channel. For a one-on-one or group call, the file goes to the OneDrive of the person who starts the recording. Transcripts also rely on OneDrive or SharePoint. Teams storage and permissions.

Start by identifying the meeting type and the file owner. Specific rules apply when the organizer does not have OneDrive or for certain events published as video-on-demand. The account used to organize the meeting therefore matters in your review. Teams storage and permissions.

Your organization's region and the scope of the EU Data Boundary

The EU Data Boundary is Microsoft's commitment regarding the storage and processing of certain data categories within a defined European area. For Microsoft 365, the organization's registration country must be located in the European Union or the European Free Trade Association. Microsoft excludes customers who have purchased Multi-Geo capabilities from the described scope. EU Data Boundary scope.

Identify your organization's country, subscribed options, and the locations displayed for each service. A French company must not assume from its address that all its data is stored or processed in France.

Processing and transfers to verify outside this region

Microsoft documents exceptions to the EU Data Boundary. They include governed remote access and transfers triggered by customer usage. Communication with a user located outside the boundary, a third-party application, or a connector may fall into these scenarios. EU Data Boundary residual transfers.

For your analysis, associate each data flow with the service that processes it and its terms. An integration enabled in Teams may fall under a separate contract. Maintain the list of authorized services alongside the documentation used to decide on their activation.

Retention and deletion of your Teams recordings

File expiration and your organization's retention policies

Microsoft indicates a default expiration of 120 days for recordings and transcripts. This value is configurable and includes exceptions depending on the subscription plan or event type. A change to the policy applies to new files; it does not automatically modify the expiration of all existing files. Teams expiration policy.

Expiration serves to manage storage space. Microsoft specifies that it is not sufficient to ensure retention and deletion requirements related to compliance. Sensitive meeting options.

GDPR, Article 5(1)(e): "storage limitation" (unofficial translation). GDPR Articles 5 and 6, CNIL text.

The duration must correspond to the purpose and applicable obligations. Document this requirement before selecting the value in Teams. The 120 days are a product setting, with no general statutory retention status.

Recycle bins, downloaded copies, and shared files

Upon expiration, the file moves to the recycle bin. According to Microsoft, restoring it removes the initial automatic expiration. The documentation also indicates that a recording moved outside its original location falls outside the described expiration setting. Purview expiration and retention. Sensitive meeting options.

Have your administrator verify recovery options. The reviewed Microsoft pages provide differing indications regarding the recycle bin retention period; no universal timeframe is stated here. Also inventory downloaded or exported copies. The deletion of the original file does not demonstrate their erasure.

Retention policies and preservation obligations

A Microsoft Purview retention policy can keep a copy in a preservation hold library after the file disappears for the user. A deletion policy has a different effect: when it coexists with Teams expiration, the earliest deletion date may apply. Purview expiration and retention.

Ask your administrator to review expiration, retention, deletion, and any litigation hold measures together. Also verify who can retrieve preserved files. A recording absent from the user's library may still exist within an administrative repository.

The organizer's obligations are detailed in the guide recording a business meeting under the GDPR. They complement Teams retention settings.

Informing participants and accessing recordings

Purpose, legal basis, and notice prior to recording

Define the use of the recording before the meeting: preparing meeting minutes, training a team, or keeping an archive do not constitute the same processing. The legal basis must correspond to that use. Consent is among the options in Article 6; it is not an automatic solution for every business meeting.

GDPR, Article 6(1): "following conditions" (unofficial translation). GDPR Articles 5 and 6, CNIL text.

Next, prepare participant notice, including recipients, retention, and procedures for exercising data subject rights.

GDPR, Article 13(1)(c): "the legal basis for the processing" (unofficial translation). GDPR Article 13, CNIL text.

The notice must explain the processing actually intended, including the use of transcription or an assistant when this concerns the collected data.

Teams notifications and participant agreement

Teams allows requesting agreement before a participant can turn on their microphone or camera. The choice is recorded in the attendance report. Microsoft also documents adding a URL to a privacy statement. Sensitive meeting options.

Use these settings consistently with the notice and legal basis selected. The presence of an agreement button does not, on its own, demonstrate that the legal requirements for processing are met. Have the mechanism validated for the context of the meeting, drawing on Articles 6 and 13 cited above.

Access rights for organizers, colleagues, and guests

For standard meetings, Microsoft specifies explicit sharing with guests and external participants. Their attendance does not automatically give them access to the recording. Co-organizers have edit permissions on files in the standard scenario. Recording policies. Teams storage and permissions.

An option allows choosing who can view the recording and transcript. Documentation reserves this to Teams Premium or a Copilot license, with exclusions for channel meetings and ad-hoc meetings. Check availability in your configuration before drafting an internal procedure. Persons authorized to access files.

Downloading and sharing after the meeting

Permissions may change after the meeting. Microsoft notes that altering permissions in SharePoint, labels, or sharing links can override the initial setting chosen in meeting options. Third-party applications are not restricted by this option alone. Persons authorized to access files.

Monitor actual access to the file and links sent. For channel meetings, Microsoft documents a policy to block downloads. Test behaviors with the relevant profiles, particularly an external guest, before standardizing your procedure. Sensitive meeting options.

How Microsoft handles your Copilot conversations

Data used depending on the enabled Copilot mode

The mode allowing Copilot to be used during and after the meeting relies on a saved transcript. The mode restricted to the meeting uses speech recognition data that is not saved after the exchange ends. Access depends on licenses and configured policies. Copilot modes in Teams.

Select the mode based on authorized use. For a confidential meeting, also check authorized persons and retention rules for Copilot interactions.

Commitment on model training and its scope

Microsoft indicates that prompts, responses, and data accessed through Microsoft Graph are not used to train foundation models. This commitment is presented in the documentation for the enterprise service. The terms for agents and connected services require additional review. Commercial Copilot data and privacy.

Model providers may have different scopes. Microsoft excludes the relevant Claude models from the EU Data Boundary and documents separate terms for certain variants with retention. OpenAI documentation distinguishes models operated by Microsoft via Azure from models operated directly by OpenAI as a subprocessor. For the latter, it specifies European commitments and their limitations. Claude in Microsoft services. OpenAI as a Microsoft subprocessor.

These documents do not allow identifying the specific model used for a given meeting. Verify the features and authorized providers in your environment before attributing a data flow to a service provider.

Retention of prompts, responses, and transcripts

Operating without a saved transcript does not mean that all interactions disappear. Microsoft indicates that Copilot prompts and responses in Teams may be retained for compliance purposes under Purview policies. Copilot modes in Teams.

Examine the transcript lifecycle and that of Copilot interactions separately. General documentation describes a history containing prompts, responses, and referenced data. Inquire about which retention settings apply to this history in your organization. Commercial Copilot data and privacy.

Microsoft 365 certifications and documented safeguards

Scope of certifications applicable to Teams

Official Teams documentation cites ISO 27001, ISO 27018, and SOC 1 and SOC 2 reports. It refers to Microsoft compliance resources. These references provide items to review for your assessment. Teams security and compliance.

Request documents covering the services used, their validity period, and their scope. Full certificates and reports were not inspected for this page. A reference in public documentation therefore does not serve to confirm here coverage for each subscribed option.

Compliance documents to request or consult

Gather the applicable DPA, service terms, subprocessor list, and reports available in the Service Trust Portal. Keep the reviewed version and the date of your review. Safeguards must correspond to the services actually activated. Teams security and compliance. Microsoft DPA: catalog and French document November 2026.

The French DPA provided by Microsoft as of November 1, 2026, was reviewed for this page, particularly regarding transfers and subcontracting. The version that applies to your organization must be confirmed in your contract. The existence of a recent public version is not sufficient to determine your contractual terms.

The Microsoft contract and data transfer framework

The contracting entity and data processing agreement

Identify the entity appearing on your purchase agreement and the documents incorporated into it. Your procurement channel and terms must be examined together.

GDPR, Article 28(3): "Processing by a processor shall be governed by a contract" (unofficial translation). GDPR Articles 28, 32 and 35, CNIL text.

The Microsoft DPA designates Microsoft Ireland Operations Limited as the data protection representative in the EEA and Switzerland. This designation alone does not identify the contract signatory for each customer. Distinguish between the representative, the contracting entity, and entities participating in the processing. Microsoft DPA: catalog and French document November 2026.

Subprocessors and safeguards governing transfers

The Microsoft DPA governs the use of subprocessors and provides safeguards for transfers. Its transfer section refers to the 2021 standard contractual clauses. The complete subprocessor list was not audited for this page. Microsoft DPA: catalog and French document November 2026.

GDPR, Article 46(1): "appropriate safeguards" (unofficial translation). GDPR Articles 46 and 48, CNIL text.

Identify the relevant flows and the mechanisms applicable to them. Retain documentation supporting your rationale, taking into account connected services and documented localization exceptions. A DPA is one component of this analysis; its existence does not validate every possible use.

Government access requests and the US legal framework

US law provides for preservation or disclosure obligations that may apply to data located outside the United States when it falls within the possession, custody, or control of the provider concerned.

18 USC §2713: « within such provider’s possession, custody, or control ». 18 USC §2713, US official text.

This statute forms part of the obligations and procedures of the relevant chapter. It does not provide for permanent access without due process. European law also regulates the recognition of requests from third-country authorities.

GDPR, Article 48: "on condition that it be based on an international agreement" (unofficial translation). GDPR Articles 46 and 48, CNIL text.

The article reserves the other transfer grounds provided in the chapter. Microsoft states that it seeks to redirect requests to the enterprise customer and notify them, unless legally prohibited. Review these elements together with your legal counsel, without inferring automatic illegality solely from the provider's nationality. Microsoft policy on government requests.

Verifications to conduct within your organization

Documents and settings to gather with your DPO and IT department

Gather documentary evidence and the settings actually applied. The following table serves to prepare this review. It does not constitute the outcome of an audit of your environment.

Verification item Document or setting Practical consequence
Localization Region by service, registration country, Multi-Geo Define applicable commitments
File ownership OneDrive or SharePoint, organizer Identify who manages access and deletion
Retention Teams expiration and Purview policies Check what happens to files after they disappear from the interface
Sharing Permissions, links, and external access Control who can view or retrieve the recording
Copilot Mode, licenses, providers, and history Authorize processing corresponding to the intended use
Contract DPA, subprocessors, compliance reports Keep the records underpinning the decision

These checks draw on the Microsoft documents cited in previous sections. The security rule depends on the processing risk.

GDPR, Article 32(1): "a level of security appropriate to the risk" (unofficial translation). GDPR Articles 28, 32 and 35, CNIL text.

Specific requirements for sensitive meetings and regulated sectors

Submit to your DPO the nature of the information exchanged, the recipients, and the planned integrations. Authorization granted for a routine commercial meeting does not support the same conclusion for a meeting containing sensitive information or governed by sector-specific regulations.

GDPR, Article 35(1): "high risk" (unofficial translation). GDPR Articles 28, 32 and 35, CNIL text.

A data protection impact assessment must be considered when the conditions set out in this article are met. This page does not validate any specific sector regulatory regime and does not attribute HDS or SecNumCloud qualification to Teams. The review must address your processing operations and their applicable requirements.

Additional verifications when an assistant like Leexi joins Teams

Adding Leexi requires examining its own DPA, the transmitted data, access to meeting summaries, and their retention. Teams recording access options alone do not restrict third-party applications. Persons authorized to access files.

The Leexi DPA outlines customer obligations in Article 5 and the prohibition on model training in Article 7. Its Annex 2 details providers and processing locations, including AWS in France and Ireland, Azure in France and Sweden, and Mistral in France. Leexi DPA, public PDF.

Review these commitments alongside the selected configuration and the terms of activated integrations. To prepare this review, you can consult the Leexi security pack and share the relevant documents with your DPO. Leexi security page.

To examine the processing added by Leexi, see the overview of the Leexi DPA and the commitments on non-training on meeting data. These documents concern Leexi; Microsoft guarantees must be assessed separately.

Try Leexi for free to see how the assistant fits into your Teams meetings.

Frequently asked questions about Teams and the GDPR

Can Microsoft Teams be used in a European company?

Using Teams must be evaluated based on your contract, your data, and your settings. Microsoft documents European commitments, including the EU Data Boundary for eligible organizations. Your DPO and IT department must review their scope, data transfers, and intended use before approving your configuration. EU Data Boundary scope.

How can I check where my Teams organization's data is hosted?

In the Microsoft 365 admin center, go to organization settings, then organization profile and data location. Identify the locations by service. Next, verify the EU Data Boundary scope and subscribed options, including Multi-Geo. This check must be supplemented by assessing processing and transfers linked to connected services. Teams data location, EU Data Boundary, documented transfers.

Does the Teams recording notification suffice to inform participants?

The notification alone does not cover all information required by Article 13 of the GDPR. Provide accessible notice specifying who processes the data, why, on what basis, for which recipients, for how long, and how to exercise rights. Teams allows adding a privacy URL. GDPR, Article 13, Teams settings.

Article 13(1)(c): "the purposes of the processing for which the personal data are intended as well as the legal basis for the processing" (unofficial translation).

The notice must therefore describe the intended use of the data, beyond the mere start of recording.

Can a Teams recording be kept past its expiration date?

You can modify the expiration date if you have the necessary edit permissions. Also check applicable Microsoft Purview policies with your administrator. The chosen duration must remain justified by the purpose of processing and applicable obligations. If the file has already expired, promptly ask the administrator to check recovery options. Expiration management, Purview retention, GDPR, Article 5.

Article 5(1)(e): "for no longer than is necessary for the purposes" (unofficial translation).

The technical ability to extend retention must correspond to a documented need.

Can an external guest access the recording after the meeting?

Yes, if the recording is explicitly shared with them and your organization's policies allow it. For standard meetings, their attendance does not automatically give them access to the file. Check OneDrive or SharePoint permissions and sharing links before sending the recording. Teams recording policies.

What should be verified before enabling Copilot for a confidential meeting?

Check the Copilot mode, the persons authorized to view the data, the activated model providers, and retention rules. The "only during the meeting" mode uses speech recognition data that is not saved after the exchange. However, prompts and responses may be retained under Microsoft Purview policies. Have these parameters validated for the confidentiality level of the meeting. Copilot in Teams, Copilot data protection.

What checks should be carried out before adding Leexi to Teams?

Examine the Leexi DPA, providers and processing locations, retention periods, and access to meeting summaries. The DPA specifies customer obligations and Leexi's commitments, including no model training. Also check the data accessible to the integrations you enable. Teams settings must be supplemented by Leexi-specific controls. Leexi DPA, Articles 5 and 7 and Annex 2.

Article 7.2: "Leexi imposes this same prohibition, by contract" (unofficial translation).

This commitment extends the training prohibition to the relevant subprocessors; the terms of connected third-party tools still require review.

Sources and verification date

Sources accessed on November 5, 2026. Public documents describe commitments and features; no testing in a customer environment or comprehensive legal audit was conducted. Full certificates were not inspected.

Recommended Articles

Ready to boost your productivity with Leexi?

Leexi AI Notetaker takes notes for you

Discover here