M365 LIFEThe license arrived before the service.
If the phrase “assigned, not provisioned” brings back a specific afternoon, you probably do not need another shirt explaining what a programmer is.
The familiar details are identity, mail flow, sharing permissions, device compliance and licensing. A shirt about creating one Team works because you know the site and mailbox came with it. A salary-spreadsheet joke works because you have already had the permissions conversation.
Developer shirts often make the code or delivery process the reference: syntax, commits, bugs and releases. That is a useful direction if the person you are buying for talks more about pull requests than Conditional Access.
These are not separate tribes. Many admins automate their work, and plenty of developers maintain a tenant. The best gift is the reference they recognize, not a label that guesses their whole job.
Think of the workload they spend time in. Teams for the accidental site owner. Exchange for the mailbox that will not retire. Entra for the sign-in investigation. Intune for the device that says it is not compliant. Start with that problem, then check the design and size guide together.
| The reference | M365 admin shirt | Developer shirt |
|---|---|---|
| The familiar objects | Tenants, mailboxes, policies, permissions | Code, commits, builds, releases |
| The conversation it starts | “That happened in our tenant.” | “That happened in our codebase.” |
| Useful gift clue | The Microsoft 365 workload they support | The language, tools or delivery work they enjoy |