Microsoft 365 Governance and Licensing

For a tenant that was set up quickly and never revisited, or a licensing bill nobody has reconciled against the people on it.

We put a fast-grown Microsoft 365 tenant in order: sharing and guest access, meeting settings, and default retention. Licenses are assigned by group and trimmed to what people use.

How we help

We put the tenant’s settings right and keep them that way through change control, and assign licenses by group.

Tenant settings

External and guest access, sharing, meetings, and default retention reviewed against Microsoft’s recommended settings and set through change control.

What you get

  • Sharing, guest, and meeting settings for Teams, SharePoint, and OneDrive
  • Enterprise app consent and expiring app secrets reviewed
  • Default retention policies for mail, Teams, and SharePoint

Best for

A tenant that grew by hand since the first rollout, with settings nobody has reviewed.

Admin roles, emergency access, and Conditional Access: Identity and Access

Group-based licensing and license review

Licenses assigned by group from documented standards, reclaimed from leavers, and reviewed against what people use.

What you get

  • Licensing groups and standards documented
  • Unused licenses and add-ons reclaimed
  • Usage reviewed by workload
  • A monthly license review if we run the tenant

Best for

A bill that has grown faster than the headcount, with no written standard for who gets which license.

Case studies

All case studies

Questions we get

We rolled out Microsoft 365 fast. What usually needs fixing?

Administrator roles never trimmed, guest and external sharing left open, no retention, MFA on some accounts and not others, and licenses assigned one at a time. The Assess phase lists what applies to your tenant and the order to fix it.

Will you cut our licensing bill?

Usually there are licenses to reclaim from leavers and add-ons that go unused, and group-based licensing stops the drift from coming back. We don’t quote a saving in advance. The review shows what changed and what it saved.

Is this the same as the Microsoft 365 Security Assessment?

No. The Microsoft 365 Security Assessment looks at the tenant for security risk. This service puts the settings and licensing right, and the deeper security work sits under Security & Compliance.

See Security Assessment and Roadmap

How do you make changes without breaking things?

Through change control, one setting at a time, with a pilot group for anything users would notice. Each change is recorded with its reason, so the next administrator knows why it is set that way.

What sets the scope of a governance and licensing project?

Users, licenses, and the workloads in scope set most of it. The number of settings the Assess phase flags counts as well.

Do you set up litigation holds and records retention?

That’s Data Security and Compliance, where litigation holds and retention mapped to your records schedule are designed. This service sets the default retention only.

See Data Security and Compliance

Can you keep it that way afterwards?

Yes. Under Managed Azure and Microsoft 365 the tenant gets a monthly license review and a quarterly review of access and Conditional Access, and changes keep going through the same change control.

See Managed Azure and Microsoft 365

Talk to us about Microsoft 365 Governance and Licensing

It starts with a 60-minute call. If we need more to scope it, a short questionnaire follows. Then a written proposal and statement of work. Once you approve, we begin with the Assess phase.