From c29f379386ae45262725c57bcae2605ebbba7674 Mon Sep 17 00:00:00 2001 From: Ross Scroggs Date: Tue, 29 Apr 2025 06:58:22 -0700 Subject: [PATCH] Update Using-GAM7-with-a-delegated-admin-service-account.md --- wiki/Using-GAM7-with-a-delegated-admin-service-account.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Using-GAM7-with-a-delegated-admin-service-account.md b/wiki/Using-GAM7-with-a-delegated-admin-service-account.md index cf78ee26..4664cc42 100644 --- a/wiki/Using-GAM7-with-a-delegated-admin-service-account.md +++ b/wiki/Using-GAM7-with-a-delegated-admin-service-account.md @@ -23,7 +23,7 @@ GAM7 version 6.50.00 or higher is required. ## Disadvantages * DASA accounts can only be delegated admins. [If a task requires super admin rights to perform](https://support.google.com/a/answer/2405986#:~:text=Only%20super%20administrators%20can...), DASA accounts won’t be able to do it. -Not all Google Admin APIs work with DASA right now. For example, Google Vault API calls will fail with a DASA account. +Not all Google Admin APIs work with DASA right now. For example, Google Vault API calls will fail with a DASA account; Classroom API calls do not return data. * DASA is a delegated admin and can make Workspace / Cloud Identity admin API calls, it does not replace domain-wide delegation (DwD) when using GAM7 commands that interact with Gmail, Drive and Calendar user data. * GAM7 support for DASA is still experimental and some things may fail. Please report your findings to the [GAM group](https://groups.google.com/g/google-apps-manager).