domainwidedelegation.comStart free

Use cases → Admin and governance

Bulk creation and removal of user email aliases

Add or remove hundreds of user aliases across a domain in one operation, avoiding manual errors and missed accounts.

Who it is forIT admins managing mass rebranding, mergers, or standardising address formats.
APIsAdmin SDK
Typical scopesadmin.directory.user.alias

The problem

Alias management through the admin console is tedious and error-prone at scale, especially when handling organisational changes or correcting naming conventions. Manual steps lead to inconsistent state and missed users, and bulk import tools do not support removals. Automation via domain-wide delegation is the only way to guarantee coverage and auditability.

How it works

  1. Enumerate target users from the directory, filtering by criteria such as org unit or existing aliases.
  2. For each user, use the service account to create or remove the specified alias via the Admin SDK.
  3. Batch requests where possible, but handle per-user failures explicitly.
  4. After each operation, re-fetch the user's aliases to confirm the change took effect.
  5. Log both successes and failures with enough detail to support a retry.

What changes

Alias changes are applied consistently across the organisation, with a verifiable audit trail and no manual intervention required.

The trap in this one. The Admin SDK's alias create and delete endpoints are eventually consistent; a newly created alias may not appear on a subsequent read for up to several minutes, and attempting to re-create or remove in this window will return confusing HTTP 409 or 404 errors. Bulk jobs that retry too aggressively can get stuck in a loop or misreport success—always implement backoff and treat a 409 on create or a 404 on delete as a signal to re-check after delay, not as final state.

Questions people ask

Can I create and remove aliases in the same batch job?

Yes, but avoid creating and deleting the same alias for the same user in a single run, as propagation delays can produce race conditions and transient errors.

How long does it take for alias changes to propagate?

Alias changes are usually visible within a few minutes, but in large domains or during peak times, delays of up to 10 minutes are common.

Want this built?

This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.

Talk to us Or read the setup guide

Related use cases

Audit which third-party apps can read your mail

List every OAuth grant across the domain and find the retired tools still holding access.

Automate joiners, movers and leavers

Create accounts, set group membership, provision Drive and hand over mailboxes without a manual checklist.

Continuously verify your delegation still works

A scheduled probe that proves every API still answers under every tenant, before a customer finds out otherwise.