Edit

Share via

Understand deployment statuses in Microsoft 365 Lighthouse

  • Article

When a tenant's onboarding status becomes Active or when you access a tenant within Microsoft 365 Lighthouse, Lighthouse queries the tenant for existing configurations. The deployment status is assigned to each task based on the status of each setting included in the subtask and, where applicable, for each user to which the subtask is assigned.

Lighthouse automatically determines deployment statuses when detection is possible. When detection isn't possible, Lighthouse relies on the status you manually set.

Tasks can have the following statuses:

Task Status Description
Compliant
  • All settings included in the subtask are Compliant.
  • There are no settings that are Not compliant.
  • There are no settings that are Missing from all existing configurations. A task can be Compliant if a setting is Compliant in one or more existing configurations without being Not compliant in another.
  • There may be Extra settings detected within existing configurations.
Not compliant
  • One or more settings included in the subtask are Not compliant.
  • One or more settings are Missing from all existing configurations.
  • There may be Extra settings detected within existing configurations.

    • Note: Doesn't apply to subtasks that are Not licensed.

Not licensed The tenant isn't licensed for the services required to deploy the configuration associated with the subtask.
Dismissed The subtask was dismissed by a Lighthouse user.

Note: A Lighthouse user can dismiss Not licensed subtasks.

Lighthouse will stop detecting or reporting deployment status for subtasks that have been dismissed.

To determine the status of each subtask, Lighthouse detects the status of each setting included in the subtask.

Settings can be assigned the following statuses:

Setting Status Description
Compliant The value detected in the existing configuration deployed to the customer tenant is equivalent to the value in the deployment plan for all targeted users.
Not compliant The value detected in the existing configuration deployed to the customer tenant isn't equivalent to the value in the deployment plan for one or more targeted users.
Missing There's no value detected in the tenant for a setting that is included in the deployment plan.
Extra There's a value detected in the tenant for a setting that isn't included in the deployment plan.

Where applicable, Lighthouse detects the status of each user for the applicable subtask.

Users can be assigned the following statuses:

User Status Description
Compliant
  • The user is targeted for the subtask.
  • The user has been assigned licenses for all services required by the subtask.
  • All settings included in the subtask are Compliant.
  • There are no settings that are Not compliant.
  • There are no settings that are Missing from all existing configurations. A user can be Compliant if a setting is Compliant in one or more existing configurations without being Not compliant in another.
  • There may be Extra settings detected within existing configurations.
Not compliant
  • The user is targeted for the subtask.
  • The user has been assigned licenses for all services required by the subtask.
  • One or more settings included in the subtask are Not compliant.
  • One or more settings are Missing from all existing configurations.
  • There may be Extra settings detected within existing configurations.

    • Note: Doesn't apply to subtasks that are Not licensed.
Excluded The user has been excluded from the subtask.

Note: When a user is Excluded from a subtask, status detection and reporting will be updated accordingly, but existing configurations won't be affected.
Not licensed The user isn't licensed for the services required to deploy the prescribed configuration.

Note: Doesn't apply to users with Not targeted status.
Not targeted The user isn't the intended target for the subtask. For example, a user that isn't an admin is reported as Not targeted for a subtask that is assigned only to admins.

Related content

Overview of deployment tasks in Microsoft 365 Lighthouse (article)
Overview of using Microsoft 365 Lighthouse baselines to deploy standard tenant configurations (article)
Overview of permissions in Microsoft 365 Lighthouse (article)
Configure Microsoft 365 Lighthouse portal security (article)
Microsoft 365 Lighthouse FAQ (article)