MS Entra – Groups – Remove Group Owner

Remove an owner from a group in Entra ID.

Action details

Property	Value
Action label	MS Entra – Groups – Remove Group Owner
Category	CloudTools
Apex class and method	DeleteEntraGroupOwner.deleteGroupOwner
Input type	DeleteEntraGroupOwner.DeleteEntraGroupOwnerInput
Output type	List<DeleteEntraGroupOwner.DeleteEntraGroupOwnerOutput>
Authorization	Microsoft 365 connector; supported authorization depends on the endpoint and target.
Microsoft Graph request	DELETE /groups/{groupId}/owners/{ownerId}/$ref

Prerequisites and permissions

Configure a CloudTools Connector with Connector Type set to Microsoft 365. Complete sign-in for OAuth Delegated (Authorization Code). For supported OAuth Application (Client Credentials) requests, grant application permissions and administrator consent. The identity must have access to the selected resource; directory operations can also require Microsoft Entra roles. Use Creating an Entra ID App and Integration Connectors for setup.

The action permission provider declares these alternatives. They are not cumulative requirements or universally interchangeable; check the Microsoft reference for endpoint, target, and property restrictions.

Permission type	Declared alternatives
Delegated	Group.ReadWrite.All, Directory.ReadWrite.All
Application	Group.ReadWrite.All, Directory.ReadWrite.All

Endpoints: /groups/{groupId}/owners/{ownerId}/$ref.

See the Microsoft operation and permissions reference.

Inputs

Input	Apex field	Type	Required	Description
Group Id	groupId	String	Yes	Group identifier
User ID	ownerId	String	Yes	User principal name (UPN) or object ID for the owner

Supply a nonempty list with a non-null first request. Graph actions process only that first request. Global inputs do not expose connectorId; subscriber Apex and Flow use CloudTools connector selection. Use Microsoft Graph resource IDs or the specifically documented user identifier, and resolve dynamic values before invocation.

Outputs

Returns one operation result after the call returns. Inspect success and message; an accepted or started operation may still require completion checks. Exceptions are generally thrown for failures rather than returned as success=false.

Output	Apex field	Type	Description
Success	success	Boolean	Whether the delete succeeded
Message	message	String	Result message

Behavior and limits

The request deletes the membership/ownership reference using /$ref, rather than deleting the directory object. Member and owner IDs identify the directory object whose reference is removed.

Use in Flow

Use MS Entra – Groups – Remove Group Owner where supported. Use a Microsoft 365 application connector configured as Set as default for Flow automations only if the endpoint and target support application access. Supply required values, retain useful outputs, and add fault handling. Delegated connections are not supported for CloudTools Flow automation. The action processes only the first input request.

Use in custom Apex

This subscriber-org example uses the Apptigent namespace. Replace identifiers and example values before use. Configure the connector, complete authorization first, run in a context permitting callouts, and handle exceptions, empty results, and unmapped fields.

Apptigent.DeleteEntraGroupOwner.DeleteEntraGroupOwnerInput request =
    new Apptigent.DeleteEntraGroupOwner.DeleteEntraGroupOwnerInput();
request.groupId = 'f11f1340-30b1-4f1d-91ec-c853b7245646';
request.ownerId = 'user@example.com';



List<Apptigent.DeleteEntraGroupOwner.DeleteEntraGroupOwnerOutput> results =
    Apptigent.DeleteEntraGroupOwner.deleteGroupOwner(
        new List<Apptigent.DeleteEntraGroupOwner.DeleteEntraGroupOwnerInput>{ request }
    );
System.debug(results);

Use in a Lightning Web Component

Use deleteEntraGroupOwner from msEntraConnectorLib through MSEntraConnectorController. These c/ imports apply in the same namespace. Set request.connectorId for direct MSEntraAction calls. The controller captures the request selection for MSEntraAction.

Global input	LWC request mapping
groupId	request.groupId
ownerId	request.ownerId

entraActionExample.js

import { LightningElement } from 'lwc';
import { deleteEntraGroupOwner } from 'c/msEntraConnectorLib';

export default class EntraActionExample extends LightningElement {
    result = null;
    errorMessage = '';
    isRunning = false;
    completed = false;

    async handleRun() {
        if (this.isRunning || this.completed) return;
        this.isRunning = true;
        this.errorMessage = '';
        try {
            const request = { connectorId: 'REPLACE_WITH_CONNECTOR_RECORD_ID' };
            request.groupId = 'f11f1340-30b1-4f1d-91ec-c853b7245646';
            request.ownerId = 'user@example.com';
            this.result = await deleteEntraGroupOwner(request);
            this.completed = true;
        } catch (error) {
            this.errorMessage = error.requiresInteractiveAuthorization
                ? 'Sign in to Microsoft for the connector, then try again.'
                : error.message || 'The Entra action failed.';
        } finally {
            this.isRunning = false;
        }
    }
}

entraActionExample.html

<template>
    <lightning-button label="Run action" onclick={handleRun}
        disabled={isRunning}></lightning-button>
    <p role="alert">{errorMessage}</p>
</template>

The library returns one mapped DTO or null. The controller can flatten nested fields, serialize data, or map an action result into an operation DTO. rawJson contains serialized mapped Apex data rather than the untouched Graph response.

Use getMSEntraAuthorizationState, beginMSEntraAuthorization, and createMSEntraOAuthMessageHandler to arrange delegated sign-in. The library normalizes errors but does not automatically sign in or retry. Reset completed for a new deliberate operation, and inspect resource state before retrying a mutation with an uncertain outcome.

Error handling and troubleshooting

Symptom	What to check
Required fields error	Supply a nonempty request list and required or conditionally required inputs. For LWC, use the mapped field names.
Authorization or access denied	Check connector selection, sign-in, endpoint/target permission support, administrator consent, directory roles, and resource access.
Resource not found	Check Microsoft IDs and parent resource relationships. Preserve group/drive/item associations and mailbox/calendar/event IDs.
Missing or unexpected output	Check query support, pagination, wrapper versus item models, public-only properties, and mapped DTO fields.
Operation rejected	Inspect the Microsoft error, supported writable fields, group/calendar restrictions, recipient/license data, and file transfer limits.

See Entra connector introduction.