Skip to content
Copy as Markdown

Licence requirements

ScopeTenant

Some baselines only work when the client tenant holds a particular Microsoft licence.

The requirement is always on a service plan rather than a bundle name: Octiga checks for “Entra ID P1”, not for “Microsoft 365 Business Premium”. It doesn’t apply a baseline to a tenant that lacks its licence. A user who lacks a licence a baseline needs is excluded from that baseline’s checks rather than reported as failing. Octiga doesn’t warn you when a licence is missing; the lists below and the Service plans fact on every baseline show what each baseline needs.

Five groups of Microsoft licences gate baselines.

Needed by every Conditional Access baseline, and by dormant-account detection. Either Entra ID P1 or Entra ID P2 satisfies this; no baseline in Octiga requires P2 specifically.

Conditional Access Policy

Access Management

Needed by every device compliance and device configuration baseline.

Intune

Needed by external sharing, link expiry and storage-warning baselines.

Sharing

Remote Access

Needed by Safe Links and Safe Attachments, and by the SharePoint infected-file-download baseline.

Email Security

Sharing

Needed by the Customer Lockbox baseline alone.

Access Management

Every baseline picker has a Service plans column. A dash means no licence is required; a number opens a tooltip listing the specific plans, and any one of them satisfies the requirement.

The Add Baselines dialog's Service plans column, showing a tooltip listing the Microsoft licences a Conditional Access baseline requires
The Service plans column in the Add Baselines picker
  1. The Service plans column: a dash means no licence is required; a number opens the tooltip

The same fact appears on the baseline’s own page, in its metadata header row.

When you deploy a scheme, the result shows how many baselines were skipped for licence. This is a quiet exclusion, not a failure: the tenant (or the user) doesn’t hold a licence one of the incoming baselines needs, so Octiga left it out rather than apply something it can’t check. Deploying a scheme covers the rest of the deploy result, and Deviations shows what an excluded user looks like day to day.