Microsoft has created an alternate pathway to deliver the Modern Desktop Assessment by introducing a Type 2 of the Assessment, which looks at the broader organizational IT readiness while requiring less depth than the original Assessment. This Assessment type does not require you to deploy Windows Analytics (or similar tools) in a customer’s environment to get a detailed compatibility analysis but instead utilizes a discovery questionnaire-based approach to determine the customer’s IT readiness. Also, a key difference is in the Proof of Execution (POE) documents that you are required to submit on successful completion of the engagement. 

You can choose either of the two Assessment types depending on your customer’s scenario. 

There are no changes to the customer eligibility criteria, application process, and funding amounts. Furthermore, if you already have the customer engagement approved, you can choose either of the two types for delivery and the approved funding will remain as-is. Please note in the documentation you will see the seat size set at a minimum of 1000, but for Atea Microsoft is continuing with the reduction to 500 seats in order to qualify.

Both variations of the Assessments address two basic objectives:
1. Presenting the value of Windows 10 and Office 365 ProPlus
2. Educating the customer about Windows and Office EOL scenarios, and related impact

In addition to the above, each of the two Assessments includes different scope items defined below. Microsoft understands that customer conversations may take different forms and thus have crafted different guidance and deliverables accordingly.

Use this pathway for a conversation around compatibility and use of Analytics. This is the original design of the Assessment kit. 

• Basic scope, as described above
• Provide a summary of existing versions of Windows OS and Office clients in the customer’s organization
• Review the compatibility of the customer’s Application and Device portfolio to deploy Windows 10 and Office 365 ProPlus
• Provide a summary of issues and blockers based on the compatibility analysis

Final deliverables and proof of execution: pre-assessment  and post-assessment surveys, a copy of compatibility analysis report (see report guidelines) 

Review the Overview and Delivery Timeline guidance for more details 

Use this pathway for a conversation around organizational awareness and readiness for Modern Desktop deployment.  

• Basic scope, as described above
• Educate the customer about the detailed multi-step Desktop Deployment Wheel process to enable deployment of the Modern Desktop, and
• Conduct a detailed discovery of the customer’s IT readiness for Modern Desktop deployment, using the Microsoft provided ‘Discovery Questionnaire’
• Provide a summary of issues and blockers based on the discovery

Final deliverables and proof of execution: pre-assessment and post-assessment surveys, copy of Discovery Questionnaire 

Review the Overview and Delivery Timeline guidance for more details 

1. The partner does not require to use Windows Analytics (or a similar tool) deployment, hence there is less customer push-back due to customer security concerns or missing data storage in Azure;

2. The partner does not have to deal with technical issues and blockers of tool deployment;

3. It does not require L400 technical architect to deliver, can be delivered by pre-sales consultant;

4. Although ‘active’ delivery time remains the same, since no deployment or waiting data population is required – overall it will take less time to complete (2-3 days straight);

5. The proof of execution provides a summary of issues and blockers based on the discovery from the Microsoft “Discovery Questionnaire” that includes no application/device portfolio inventory, thus should be easier to be shared with Microsoft.