Services · Data protection in the Microsoft environment

Data protection in Microsoft 365, Copilot and Dynamics 365.

Data protection rarely fails because a document is missing. It usually fails because of the environment the data actually sits in. Anyone running Microsoft 365, Microsoft 365 Copilot or Dynamics 365 has to bring together which personal data flows where, who can technically read it, and which documents prove that. That is exactly where we work: we review permissions, sharing and data paths in your tenant within the agreed scope, and we document processing activities so that your data protection or legal advisors can build on them. The legal assessment stays where it belongs — with the professionals responsible for it.

Art. 30 GDPR one fully drafted entry per commissioned business process No legal advice technical findings, no legal assessment Microsoft Partner since 2007 Review scope agreed up front, anything unreviewed is named

Our position

The seam between technology and data protection.

We are Microsoft consultants. We are not a law firm, not a provider of the data protection officer function, and not an audit body.

For general data protection advice and for appointing an external data protection officer there are law firms and specialized consultancies; that is where this service belongs. One question, however, can only be answered inside the environment itself: what actually happens there — which SharePoint site is readable by everyone in the organization, which guest access is still active, which connector feeds in data from a third-party system, which field in Dynamics 365 carries health or applicant information.

Our place is this seam: data protection in Microsoft environments, where technical implementation and data protection expertise meet. We supply the technical findings and the documentation that make a data protection assessment sound in the first place — and we state what we did not review.

Our services

Four blocks — each with a result you hold in your hands.

The blocks can be commissioned individually. Each delivers a self-contained result that keeps its value even if the next block is postponed. Scope, your contribution and responsibilities are agreed in writing up front.

01

Baseline assessment

A structured starting point for organizations that want to know where they stand before commissioning individual measures. We look at up to three jointly selected processes and up to five central documents — an existing processing overview, a privacy notice, a data processing agreement or a permissions overview, for example. Alongside that we examine the corresponding places in your Microsoft environment.

Your result: a prioritized action report that states, for every finding, where it was found, what technical or organizational action it calls for and what the next step should be, plus a results meeting with management, IT and those responsible for data protection.

Not included: a complete review of all processes, all documents or the entire tenant, a data protection assessment of the findings, and any form of certificate. The selection of processes and documents limits what can be said — the report states that.

02

Documenting a business process

For one clearly delimited business process we draft the documentation that brings the Microsoft environment and the data protection documents together. Typical examples are recruitment, customer care in Dynamics 365, contract filing in SharePoint or a support mailbox in Microsoft 365.

We capture the data flows of the process: which personal data arises, where it is stored, who can read it, which systems and services are involved, and when it is meant to be deleted. From that comes an entry for your record of processing activities under Art. 30 GDPR. For the applicable data processing agreement we compile the technical details your legal advisors need in order to review the contract: which version applies to your purchasing route and whether it was accepted, which services it covers, which subprocessors and locations it names, and which of those are actually in use in your environment. And we provide the factual details that belong in your privacy notice: categories of data processed, storage locations, services and recipients involved, who has access, and the deletion periods that can be implemented technically.

Your result: a data flow overview, one fully drafted entry for your record of processing activities, a findings note on the data processing agreement with open points and responsibilities, a structured list of details for your privacy notice, and a short explanation of how to transfer the entry to further processes.

Not included: the legal review or negotiation of the contract, the judgment whether it meets the statutory requirements, determining the legal basis, drafting and approving the privacy notice, and maintaining the record in day-to-day operation. The entry is a fully drafted proposal for your documentation, not a record we are responsible for. The text of the privacy notice is drafted and owned by your data protection or legal advisors.

03

Ongoing support

Data protection questions do not arise in the project, they arise in operation: a new department wants to use Copilot, a service provider asks for access, a business unit would like a report, and the question comes up where data on one individual person is held at all. For the technical questions that come out of them we agree on an advisory quota that management, IT and those responsible for data protection can draw on — for follow-up questions about the environment, short technical checks, and the technical preparation of decisions.

Your result: a dedicated subject-matter contact within the agreed framework, documented answers and findings notes on the questions raised, and an overview of the quota used and remaining.

Not included: the data protection officer function, handling data subject requests, and representing you before a supervisory authority. For an access request we can technically compile where data on a person is held; which details have to be disclosed is decided by your data protection or legal advisors. We commit to response times and availability only to the extent that they are expressly agreed. Scope and term are recorded in writing; anything beyond the quota is agreed separately.

04

Our technical part

This part goes deepest into the environment — it requires read access within the commissioned scope. Within that scope we review the places in your Microsoft environment where data protection is decided technically:

  • Sharing in SharePoint and Microsoft Teams — which sites, libraries and teams are readable by everyone in the organization, which sharing links exist and how far they reach, which permissions that grew over the years now point to content that was never intended for that audience.
  • External access — guest accounts, shared channels, service provider access, delegated administration rights and application permissions that take effect independently of individual users.
  • Data classification — whether sensitivity labels exist and are assigned, and whether they take effect for Copilot at all: a label without encryption and without a matching DLP policy at the Copilot location only marks content, it does not restrict it. We review which of your labels actually have an effect and where particularly sensitive content sits without any label at all.
  • Connectors and interfaces — which Graph connectors, integrations, flows and agents pull data into the environment or carry it out of it, with which permissions they run, whose access rights apply in the process, and whether the source system's permissions are genuinely carried over or set as a blanket value in the connector.
  • Model and region settings — which AI models are enabled for Copilot in your tenant, which additional subprocessors come with them, which supplementary terms apply, and what that means for the place of processing and the data region. We read the state in your tenant and in your contract documents instead of repeating a general vendor statement.

Your result: a technical review report with findings per reviewed area, concrete change proposals, a sequence ordered by effect and effort, and documented evidence of the review. On request we implement the agreed changes.

Not included: a complete tenant audit. What is reviewed is the commissioned scope; whatever lies outside it is explicitly named in the report as not reviewed. A finding with nothing of note is a snapshot of the review date and not an assurance for continued operation.

On implementation: changes to permissions reach into work in progress — a withdrawn share can interrupt a workflow that has been relying on it. We therefore implement only what has been expressly approved beforehand, name foreseeable side effects up front, proceed in delimited steps, and document the state before and after each step. The decision on every change stays with you; the risk of remaining dependencies that were not identifiable beforehand cannot be ruled out.

The substance of it

Why Copilot turns an over-broad permission into a data protection problem.

In its documentation on data, privacy and security for Microsoft Copilot, Microsoft describes two points that sound reassuring at first. First: Copilot only displays organizational data where the individual person has at least read permission — the existing Microsoft 365 permission models therefore continue to apply. Second: according to that documentation, prompts, responses and data accessed through Microsoft Graph are not used to train the foundation models, including those used by Copilot.

Both address a widespread concern — and both shift the actual risk rather than resolving it. The second statement takes the role of the leak channel away from the model: if your content does not flow into training, then the risk does not arise where most people suspect it, but in your own configuration. And the first statement says exactly where: if Copilot mirrors the existing permissions, then every over-broad permission stops being theoretical from that moment on.

The SharePoint site that was set to “everyone in the organization” years ago and today holds HR matters was open before as well. Even so, nobody found it, because nobody went looking. Copilot goes looking. Personal data that is reachable under the existing access rights becomes findable and, in answer to a question, summarizable — in seconds, in natural language, without the person asking needing to know where anything is held. The permission stays unchanged; its effect in data protection terms changes completely.

In the same documentation Microsoft points out that it is important to use the available permission models so that the right people and groups have access to the right content. That is not an aside, it is the line of responsibility: you set the permissions, not the vendor.

That is precisely why the permission review from block 04 is the review that makes the difference. Not because Copilot is unsafe, but because a working Copilot turns every piece of carelessness in granting rights into a findable result. This review therefore belongs before the rollout: anyone who starts it afterwards is troubleshooting under time pressure — in an environment where search is already open to everyone.

Three qualifications belong with this. The two statements quoted come from the Microsoft documentation “Data, Privacy, and Security for Microsoft Copilot”; they are vendor statements that we are passing on, not an assurance from us. We verify vendor statements against the specific service and against the contract version that applies to you, because feature scope, data region and bundled additional services can differ. And they apply to the service described there: your own agents, connectors and third-party extensions bring their own data paths and their own terms, and are looked at separately.

Where we draw the line

Where our service ends.

Four limits we name explicitly, because they are regularly expected otherwise.

No appointment as external data protection officer. We are not available for designation as a data protection officer under Art. 37 GDPR and do not take on the tasks under Art. 39 GDPR, neither in fact nor temporarily. If you have an internal or external data protection officer, we supply them with the technical basis. If you have none and need one, we recommend bringing in a law firm or a consultancy set up for it.

No legal advice. We give no legal advice, assess no legal bases, negotiate no contracts and do not represent you before supervisory authorities. Our deliverables are technical and organizational groundwork for a legal assessment, not a substitute for it.

No complete data protection impact assessment. We do not produce a complete impact assessment under Art. 35 GDPR. We supply components it can rest on — data flows, the permission situation, the services involved, technical measures — and we name what is missing beyond that. Whether an impact assessment is required and how it turns out is judged by the body responsible for it.

No assurance of compliance. We certify no compliance and no legal certainty, and we do not release you from your own review and documentation duties — neither for Microsoft 365 nor for Copilot, Dynamics 365 or your configuration. A review report describes findings as of the review date within the commissioned scope. A technical review cannot carry an assurance of compliance — which is why we give none.

How this fits

Where this page ends and which page takes over.

Data protection, information security, professional secrecy and AI regulation overlap, but they are four reviews side by side. This page deals with the protection of personal data in Microsoft environments: data flows, permissions, documentation duties.

If the subject is client and patient data and the particular duties of confidentiality of law firms, practices and comparable professions, the path leads to Microsoft 365 and AI for professional secrecy — there professional secrecy is at the center, not the GDPR alone, and that is where processing on behalf of a controller under Art. 28 GDPR additionally stands in the light of professional confidentiality. If the subject is the availability and integrity of your services, risk management, reporting duties and information security, the question belongs with Compliance & NIS2. If the subject is the regulation of AI systems themselves — roles as provider or deployer, risk classes, training and transparency duties — then EU AI Act is the right page; this page here looks only at the data protection side of Copilot, not at AI regulation.

One more neighbor belongs here, outside that row of four, because it sits close to block 04: Knowledge Management builds the information architecture and the permission concept so that knowledge becomes findable in the first place — there a permission is a design instrument for good search results. Here it is the subject of review from a data protection angle: we do not ask how content can be found better, but which personal data is unintentionally findable. Anyone who needs both can dovetail them; we settle the order in the initial conversation.

If several of these topics meet in your project, we sort them out in the initial conversation and say which review makes sense first.

Frequently asked questions

What is usually still open before the first conversation.

Are you a law firm, or do you take on the data protection officer function?

No, neither. We are Microsoft consultants and we work on data protection where it is decided technically: in the configuration, in the permissions and in the documentation of the processing that actually happens. For legal advice and for the formal appointment of a data protection officer, turn to a law firm or a consultancy set up for it.

Is Microsoft 365 compliant with data protection law?

Put that way the question cannot be answered, and an answer of yes would be an assurance nobody can keep. Microsoft provides contract documents, data protection information and technical features; what comes of that in your organization depends on configuration, permissions, the services you use and your processes. We review the technical side and name what is still missing for a legal assessment.

What does the GDPR mean for Copilot in practice?

According to the Microsoft documentation on Microsoft Copilot, the service only shows organizational data where the individual person has at least read permission, and prompts, responses and data accessed through Microsoft Graph are not used to train the foundation models, including those used by Copilot. The practical consequence is uncomfortable: it means your granting of permissions decides which personal data Copilot gathers together. An over-broad share becomes findable and analyzable as a result. On top of that come the legal basis, informing the data subjects, a deletion concept and logging; the legal assessment of these points is for your data protection or legal advisors.

Do you review our data processing agreement with Microsoft?

We compile the technical details on it: which version applies to your purchasing route, whether it was accepted, which services it covers, and which subprocessors and locations it names — matched against what is actually in use in your environment. Whether the contract meets the statutory requirements is judged by your legal advisors. If the subject is client or patient data and professional confidentiality, Microsoft 365 and AI for professional secrecy is the more fitting page.

Do you produce our complete record of processing activities?

No. We draft one entry per documented business process, including the corresponding data flows from the Microsoft environment. That entry works as a template for further processes, and we show you how to carry it forward. The record as a whole stays your documentation under your responsibility; we do not take on maintaining it in day-to-day operation.

Do you carry out a data protection impact assessment?

Not a complete one. We supply technical components — data flows, the permission situation, the services and subprocessors involved, the technical measures in place — and we name the open points. Whether an impact assessment under Art. 35 GDPR is required, how the risks are to be assessed and who owns it is decided by the body responsible in your organization or by your legal advisors.

Which access do you need for the technical review?

Less than is usually assumed, and never a blanket grant. For the commissioned review we clarify up front which read permissions are needed, set them up for a limited time and document what was set up and when it will be removed again. Changes to your environment are made only within the agreed scope. For the initial conversation we need no access and no personal data.

Do you work with our data protection officer, our law firm and our IT?

Yes. That division of labor is the usual arrangement and usually the fastest route: your data protection or legal advisors assess, we supply the technical findings; your IT or your IT service provider implements, or we take on the agreed part. Responsibilities, the access needed and the results are set jointly and recorded in writing.

Sources

What the vendor statements on this page rest on.

The statements quoted on Copilot come from the Microsoft documentation Data, Privacy, and Security for Microsoft Copilot. The statements on sensitivity labels and their effect on Copilot come from Learn about sensitivity labels and Microsoft Purview DLP for Microsoft 365 Copilot and Cowork. Vendor statements change; which version and which data region apply to you is something we verify against the specific service and your contract documents.

30-min initial conversation

Describe your situation to us.

In the initial conversation we clarify in thirty minutes which of the four blocks fits your situation — and which question should be answered first. For the initial conversation we need no access to your environment and no personal data.