CSP Accelerator: Defender & Purview Deployment (Business Premium)
Deployment and adoption of the Defender and Purview add-on suites on Business Premium. Co-funded delivery, not a workshop.
What this is
Offsets some of the cost of deploying and driving adoption of incremental Microsoft Defender and Purview suite seats with Business Premium customers. Customers must purchase add-on suite(s) on annual-term subscriptions via CSP. Partners can claim customers before the qualifying CSP transaction within the programme term or within 30 days after it occurs. Partners have 120 days from the date of customer consent to deliver eligible services and submit proof of execution. Incentive payments are a co-investment and are not intended to cover the full cost of deployment activities.
What you leave with
- The Defender and Purview add-on suites deployed and adopted on your Business Premium tenant
Who qualifies
Your commitment
- The add-on suite subscription itself, on an annual term; that is the purchase Microsoft co-invests against
- Change-management time across the delivery window
- A signed consent form and, at the end, a customer attestation form
- The incentive is a co-investment and is not intended to cover the full cost of deployment activities; any fee on our side is stated in writing before anything begins
How we run it
- A consent form. Microsoft's delivery clock starts on the day you sign it, so we agree the schedule first and sign second.
- Deployment inside Microsoft's 120-day window, scheduled around your change control rather than around our claim.
- Attestation at the end: the customer attestation form Microsoft requires as proof of execution.
In and out
In the funded scope
- The Defender and Purview add-on suites deployed and adopted on your Business Premium tenant
Not in it
- Licences and subscriptions. Microsoft's co-investment is against our delivery, never against what you buy.
- Microsoft's metered charges. Consumption, ingestion and any usage-based billing stay yours, billed by Microsoft as usual.
- Work outside the deployment we scoped. If the deployment surfaces something else, we quote it separately rather than quietly absorbing it into the window.
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.
What starts the 120-day clock?
Your signature on the consent form, not the first day of work. We agree the delivery schedule before you sign, so the window is spent on deployment rather than on scheduling.
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.