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.