LicenseWise One Microsoft 365 or Google Workspace licensing tip, every morning.
Field note 001 · October 20266 min read

Stop buying every user the same license.

A practical way to separate access, security, retention, and productivity—before your next renewal turns yesterday’s assumptions into another annual commitment.

The lead

Offboarding is a licensing decision, not just an HR ticket.

The expensive default is to leave a former employee on a full subscription because someone may need their files or mail later.

Start with the retention requirement, not the old job title. Microsoft and Google both provide ways to preserve former-user data without treating that person as an active worker—but the mechanics and feature boundaries differ.

Before changing anything, document who needs access, how long the data must remain searchable, whether legal hold applies, and whether the old address must continue receiving mail. Those four answers determine the right path.

01 / PRESERVE

Define the record.

Mail, files, calendar, audit history, and legal hold are separate requirements.

02 / RESTRICT

Remove sign-in.

Data preservation should not leave an old credential active.

03 / REASSIGN

Recover the seat.

Verify the platform’s timing and the destination user before reallocation.

Platform notes

Three checks worth making this week.

Microsoft 365 · Offboarding

Shared does not always mean unlicensed.

A shared mailbox can avoid a separate license within Microsoft’s limits. Larger storage, archiving, hold, and advanced compliance features can change the requirement.

Read Microsoft’s limits →
Google Workspace · Offboarding

Archive the user, then watch the clock.

Google says an archived user cannot sign in, and the active Workspace license becomes available to reassign within 24 hours. Returning users need a matching license.

Read Google’s guidance →
Google Workspace · Mixed editions

Feature scope can follow the license—or the policy.

When editions are mixed, confirm which controls follow each user and which settings can affect an organizational unit more broadly. Test before assuming isolation.

Review mixed-edition behavior →
Seat audit

Put a price on “we’ll clean it up later.”

Use your contracted per-seat amount—not a public list price—to estimate the annual spend attached to seats that still need an owner or rationale.

Annual spend represented$0
This is a prioritization aid, not a savings claim. Enter the effective amount from your invoice or reseller agreement.
Next issues

The decision runway.

Issue 002

Annual vs. flexible

How to match commitment terms to headcount volatility without turning every renewal into a scramble.

Issue 003

Security add-on math

When a bundle is cleaner than a stack of point licenses—and when it is not.

Issue 004

AI seat readiness

A permission and data-access checklist to run before buying productivity AI broadly.

Issue 005

Renewal evidence

The usage, exception, and ownership records that make a licensing decision defensible.

A deeper read

Build the license around the work—not the other way around.

Olive + Goose lays out a progressive Microsoft 365 onboarding path for small businesses, from core collaboration through security and management.

Continue at Olive + Goose →
Source desk

Sources reviewed 14 October 2026. Vendor terms and capabilities change; verify the applicable agreement and current documentation before changing production licenses.