Huntress Explains Microsoft GDAP Migration and Least-Privilege Setup

· Original article ↗

Summary

Huntress explains how service providers can migrate from DAP to Microsoft GDAP, assign granular roles, and address integration requirements. The guide emphasizes reducing over-privileged access and notes the transition deadline was suspended in some regions.

Key points

  • The article says DAP's broader permissions can leave service providers with more tenant access than necessary; GDAP allows more granular role assignments.
  • Suggested migration options include Microsoft's bulk migration tool, CIPP, and manual setup through Partner Center.
  • Manual setup involves creating an admin relationship, obtaining customer approval, assigning Azure AD roles to security groups, and selecting least-privileged roles.
  • The article recommends nested groups to organize permissions by role or job function.
  • At the article's June 2023 publication, Microsoft had suspended the May 22 transition deadline except in specific regions or countries.
  • Organizations are advised to review third-party integrations and update trust relationships, workflows, and partner training for GDAP.
  • Huntress says its Managed Identity Threat Detection and Response integration requires GDAP and Microsoft MFA for the service account.

Article Details

Defense Focus
Reduce excessive delegated access by moving from DAP to granular, least-privilege GDAP relationships and securing the service-account integration with conditional access and MFA.
Defensive Actions
  • Migrate existing DAP relationships to GDAP using the Microsoft bulk migration tool, CIPP, or a manual process.
  • Have customers remove DAP roles before approving a GDAP relationship, because DAP may override GDAP.
  • Assign the least-privileged built-in roles needed for each task and grant them to appropriate security groups.
  • Use nested groups to associate role groups with position-based groups, such as a Technician II group.
  • Review and update external integrations to align with GDAP permissions and workflows.
  • For the Huntress integration, use a dedicated service account, configure Microsoft MFA, and establish the required policy and exclusions from existing policies, including tenant policies.
  • Terminate partner or customer relationships when they are no longer needed.

Vendors

Products

Tools

Related Articles