GDAP - Read before transition!

Introduction

This article will cover the recommended setup of roles that need to be applied in order for GDAP to take precedence over DAP with permissions to will conform with CSP requirements from Microsoft and what is the correct sequence of operations that will have to be carried out from your side.

In this article:

• Basic CSP Template Roles
• Instructions and Sequence of Operations

Basic CSP Template Roles

The list of roles in the table below are based on operations that are used most frequently in common CSP Support related cases that either require light or more advanced approach. The list may vary from partner to partner, however the roles marked in RED are the ones that ensure proper precedence for GDAP over DAP. 
 

Instructions and Sequence of Operations

1. You will need to create a template that includes a list of previously specified roles.
2. You will need to ensure that the roles in RED are present on the template.
3. You will need to provision the security groups based on the data prior to the transition flow. 
- Following Instructions here: CSP Roles and Template Management
4. You can now transition your customers. 
- Following Instructions here: CSP Customer Transition

Summary

The recommended GDAP setup requires specific CSP template roles to ensure GDAP takes precedence over DAP while conforming to Microsoft CSP requirements. The basic CSP template includes 14 essential roles for common support operations: Office apps administrator, Exchange administrator, Teams administrator, Dynamics 365 administrator, Teams devices administrator, Helpdesk administrator, Cloud device administrator, Global reader, Directory readers, Password administrator, Application administrator, User administrator, License administrator, and Service support administrator. Critical roles for proper GDAP precedence are highlighted and must be included in the template. The implementation sequence requires creating a template with specified roles, ensuring critical roles are present, provisioning security groups based on template data following CSP Roles and Template Management instructions, and finally transitioning customers following CSP Customer Transition instructions. Each role is identified by its specific Role ID for accurate configuration.