QTM: Modern Work & Security Deployment Offer SOW/POE Guidance

Statement of Work

The Statement of Work confirms the details agreed upon between the Partner and the Customer who received the program voucher. The SOW must be submitted to QTM team prior to initiating work for them to review and verify.

If the partner initiates work with the eligible customer before the SOW has been submitted and approved by the QTM Team, it is possible for the partner to complete work that is outside the terms of the program and will not be compensated for it.

Proof of Execution

Upon completion of the agreed upon work, Proof of Execution must be submitted to the QTM Team. The POE is a statement of which services were provided to the eligible customer and should fall within the scope of the voucher issued.

Important: The Proof of Execution must match the approved Statement of Work.

Example: An SOW for the Modern Work & Security Deployment Offer has been submitted and the work has been completed. A POE for the Modern Work & Security Deployment Offer must be submitted to prove the project is complete. If the SOW and POE do not match, payment cannot be made.

Review the Common SOW and POE Issues section to learn about the most common issues that prevent SOWs and POEs from being approved.

Common Statement of Work and Proof of Execution Issues

Template

• Use of non-program SOW or POE documents instead of using the program templates.
• Use of the POE template for the SOW template or and vice versa.
• The POE is submitted prior to the SOW approval.
• The POE is submitted at the same time as the SOW.

Voucher information

• Missing or incorrect Voucher ID #.
• Missing or incorrect Voucher value.
• Missing or incorrect Voucher expiration date.
• Missing or incorrect Voucher program year and type selected.

Workloads/Scope of Work

• Workloads selected in Section 2 are not described in Section 3.
• Workloads described in Section 3 not selected in Section 2.
• Missing migration activities for Migration and M365 Deployment voucher redemption.
• Missing deployment activities for Migration and M365 Deployment voucher redemption.
• Missing Total Cost of Services, Deployment Services Cost and/or Migration Services Cost.
• Vague scope of work details on SOW.
• Ineligible workloads.
• Document not submitted in English.
• POE activities do not match approved SOW activities.

Contact Info

• Missing Partner or Customer signatory information.
• Signatory information and document signer differ.
• Invalid Customer Tenant ID.

Signatures

• Signature(s) and/or date(s) are missing.
• Cut and paste signatures are not acceptable. They must be physical or digital.
• Digital signatures must contain an audit trail.

Public Sector Disclosure

• Customer is Public Sector, Section 4.2, should be initialed by Customer.
• Customer is not Public Sector, Section 4.2, and should not be initialed by Customer.

Eligible workloads

A SOWs scope should be oriented towards the deployment of one or more eligible M365 workload(s) as is indicated on the SOW template.

These include:

• Azure Active Directory Premium (AADP) Conditional Access | Microsoft Entra ID
• Azure Active Directory Premium2 (AADP2) | Microsoft Entra ID P2
• Exchange Online
• Microsoft 365 Apps
• Microsoft Endpoint Management | Microsoft Intune
• Microsoft Defender for Cloud Apps (MDC) | Microsoft Cloud App Security (MCAS)
• Microsoft Defender Endpoint (MDE) | Microsoft Defender Advanced Threat Protection (MDATP)
• Microsoft Defender for Identity (MDI) | Azure ATP
• Microsoft Defender for Office (MDO)
• Microsoft Purview Insider Risk Management (IRM) | Purview Data Lifecycle Management (DLM)
• Outlook Mobile
• Purview Information Protection (MIP) | Data Loss Prevention (DLP)
• SharePoint Online
• Teams
• Teams Apps
• Teams for Frontline Workers
• Teams Meetings
• Teams Phone

Migration and M365 Deployment Vouchers must include at least one On-Prem to Cloud, or Competitive migration to one or more eligible M365 workload(s).

Activities that support deployment of eligible M365 workloads and migration from a competitive product to an on-premises deployment of O365 to M365 include:

• Understanding Business Requirements
• Planning
• Design Solutions
• Tenant Setup
• Security Configuration
• Data Migration
• Integration
• Customization
• Testing
• Training
• Deployment
• Support and Maintenance

Ineligible workloads

The following are ineligible workloads and cannot be approved:

• Teams Rooms
• Viva workloads
• Windows 365
• Power BI
• Power Automate
• Power Apps
• Sentinel

Tips for document preparation

• Read all the instructions on the template documents.
• Avoid multiple signing requests with your customer by taking advantage of the SOW prereview service from the QTM Team to ensure your SOW is approvable before asking your customer for their signature. Email your pre-signature SOW to ftspincentiveclaims@microsoft.com for review.
• To avoid having work already performed ineligible for payment, do not commence work on your engagement until SOW has been approved.
• Do not submit a POE until the SOW has been approved.
• A POE should match the approved SOW.
• Be conscious of a Voucher’s expiration date and ensure you are tracking to complete your engagement and documentation before the Voucher expires.