Data Security Envisioning Workshop
Data-driven discovery of data security and regulatory risks in your own environment, then collaborative sessions on remediating them with Microsoft Purview.
What this is
Designed to build customer intent to purchase Microsoft Purview solutions. Provides real data-driven examples of data security and regulatory risks in the customer's own environment, combined with collaborative workshop sessions, to create compelling ways for customers to remediate and prevent data security risks using Microsoft Purview (E5 Compliance) technologies.
What you leave with
- Real, data-driven examples of data security and regulatory risks in your environment
- Ways to remediate and prevent those risks using Microsoft Purview
Who qualifies
Your commitment
- Time from the compliance or data owner and the technical owners for the workshop sessions
- Read-level access to your production environment for the data-driven discovery
- Microsoft has not published the partner effort; we confirm the schedule at scoping
- A customer attestation form at the end, which Microsoft requires as proof of delivery
- Any fee on our side is stated in writing before anything begins
How we run it
- A scoping call, and a written consent checklist naming exactly what the evaluation will touch in your environment and what it will read.
- The discovery window itself, run against your production tenant, with a check-in at the end of each day so nothing in the readout is a surprise.
- A readout delivered by the engineers who did the work, walking through what was actually found rather than a deck written by somebody else.
- The customer attestation form, which is how Microsoft is shown the engagement was delivered.
In and out
In the funded scope
- Real, data-driven examples of data security and regulatory risks in your environment
- Ways to remediate and prevent those risks using Microsoft Purview
Not in it
- Remediation. The engagement finds and explains; fixing what it finds is a separate engagement, quoted at our normal fixed price.
- Production policy changes and deployment. Nothing in your tenant is altered under this engagement without a separate, quoted piece of work.
- Ongoing monitoring. The workshop is a window in time; running what it recommends is a service, not a workshop.
The funding, plainly
Microsoft describes this incentive as a co-investment that is not intended to cover the full cost of deployment activities. In practice, Microsoft pays us for a defined portion of this engagement; your commitment is the time and access listed above, plus any fee we state in writing before work begins. We never state Microsoft's funding amount: it varies by customer band and programme period, and quoting it would be guessing. If the programme window closes while your request is in flight, we tell you and requote the same work at our normal fixed price.
Asked before booking
Does Microsoft pay for all of it?
No. Microsoft describes the incentive as a co-investment that is not intended to cover the full cost of deployment activities. Microsoft pays us for a defined portion; your side is the time, access and any fee we state in writing before work begins.
Do you need access to our production environment?
Yes, read-level. That is the whole point of this shape of engagement: Microsoft funds it to find real findings in a real tenant, not to demonstrate on a sample one. The consent checklist lists every place we look before anyone signs it.
What if we do not qualify?
We say so and quote the same work at our normal fixed price. The eligibility check itself costs you nothing but the conversation.