Lighthouse Health

Microsoft 365 Lighthouse Tenant Health

This skill provides comprehensive knowledge for managing multiple Microsoft 365 customer tenants via Lighthouse, with focus on health scoring, GDAP relationship management, and remediation planning for MSPs/CSPs.

Integration Context Contract

• Canonical contract: docs/integration-context.md

* Use sovereign cloud values from the canonical contract when applicable.

Fail fast before scanning tenants when required context is missing or invalid. Redact partner/customer IDs in outputs.

Base URL

https://graph.microsoft.com/beta/tenantRelationships/managedTenants

All Lighthouse endpoints below are relative to this base URL. GDAP endpoints use a different base path.

API Endpoints

Tenant Management

Security & Compliance Baselines

User & Authentication Health

Device Compliance

Risky Users

GDAP Relationships (v1.0 — separate base path)

Base URL for GDAP: https://graph.microsoft.com/v1.0

MFA Registration Summary Response Example

{
  "value": [
    {
      "id": "customer-tenant-id_summary",
      "tenantId": "customer-tenant-id",
      "tenantDisplayName": "Contoso Customer",
      "totalUserCount": 150,
      "mfaRegisteredUserCount": 142,
      "mfaExcludedUserCount": 3,
      "securityDefaultsEnabled": false,
      "mfaConditionalAccessPolicyState": "enabled",
      "adminsMfaRegisteredCount": 8,
      "adminsMfaNotRegisteredCount": 0,
      "adminsCount": 8,
      "lastRefreshedDateTime": "2026-02-28T12:00:00Z"
    }
  ]
}

Health Scoring Criteria

Security Score (Green/Yellow/Red)

Account Hygiene

Device Compliance

Licensing

GDAP (Granular Delegated Admin Privileges)

Key GDAP Roles for Health Scanning

Filter Active GDAP Relationships

GET https://graph.microsoft.com/v1.0/tenantRelationships/delegatedAdminRelationships
  ?$filter=status eq 'active'
  &$select=id,displayName,customer,accessDetails,status,duration,autoExtendDuration,endDateTime
  &$orderby=endDateTime asc

GDAP Relationship Status Values

Create GDAP Relationship Body

{
  "displayName": "Contoso MSP - Security Management",
  "duration": "P730D",
  "autoExtendDuration": "P180D",
  "customer": {
    "tenantId": "customer-tenant-id"
  },
  "accessDetails": {
    "unifiedRoles": [
      { "roleDefinitionId": "5d6b6bb7-de71-4623-b4af-96380a352509" },
      { "roleDefinitionId": "f2ef992c-3afb-46b9-b7cf-a126ee74c451" }
    ]
  }
}

Authentication

Lighthouse operations use the partner tenant credentials with GDAP:

import { ClientSecretCredential } from "@azure/identity";
import { Client } from "@microsoft/microsoft-graph-client";
import { TokenCredentialAuthenticationProvider } from
  "@microsoft/microsoft-graph-client/authProviders/azureTokenCredentials";

const credential = new ClientSecretCredential(partnerTenantId, clientId, clientSecret);
const authProvider = new TokenCredentialAuthenticationProvider(credential, {
  scopes: ["https://graph.microsoft.com/.default"]
});
const client = Client.initWithMiddleware({ authProvider });

// Access customer tenant data via Lighthouse API
const tenants = await client.api(
  "/tenantRelationships/managedTenants/tenants"
).get();

Required Permissions

Error Handling

GDAP-Specific Errors

• 403 GDAP Expired: The delegated admin relationship has expired — renew or create a new relationship before accessing customer data
• 404 Not Onboarded: Customer tenant is not onboarded to Lighthouse — verify the tenant has an active GDAP relationship and meets eligibility requirements (at least one M365 Business Premium, E3, or E5 license)
• 403 Missing Role: The GDAP relationship exists but does not include the required role — create a new access assignment with the needed role

OData Filter/OrderBy Examples

# MFA summaries for a specific tenant
/credentialUserRegistrationsSummaries?$filter=tenantId eq '{tenantId}'

# Tenants with low MFA coverage (custom calculation from response)
/credentialUserRegistrationsSummaries?$orderby=mfaRegisteredUserCount asc

# Device compliance for a specific tenant
/managedDeviceCompliances?$filter=tenantId eq '{tenantId}'

# Active alerts ordered by severity
/managedTenantAlerts?$filter=status eq 'active'&$orderby=severity desc

# GDAP relationships expiring soon
/tenantRelationships/delegatedAdminRelationships?$filter=status eq 'active'&$orderby=endDateTime asc&$top=10

# Tenants with specific tag
/tenantTags?$filter=displayName eq 'Priority'

Common MSP Patterns

Pattern 1: Monthly Health Report Generation

1. GET /tenants — list all managed tenants
2. For each tenant:
   • GET /credentialUserRegistrationsSummaries?$filter=tenantId eq '{id}' — MFA coverage
   • GET /managedDeviceCompliances?$filter=tenantId eq '{id}' — device compliance
   • GET /windowsProtectionStates?$filter=tenantId eq '{id}' — security status
   • GET /riskyUsers?$filter=tenantId eq '{id}' — risky users
3. Calculate health scores using the scoring criteria tables
4. Generate customer-ready PDF/markdown report with Green/Yellow/Red indicators
5. Include trend comparison with previous month

Pattern 2: GDAP Relationship Lifecycle

1. GET /tenantRelationships/delegatedAdminRelationships?$filter=status eq 'active'&$orderby=endDateTime asc — find relationships nearing expiration
2. For expiring relationships: POST /tenantRelationships/delegatedAdminRelationships — create replacement with appropriate roles
3. Customer approves the new relationship in their admin portal
4. POST .../accessAssignments — assign partner security groups to GDAP roles
5. Verify access: test API calls to customer tenant data
6. Document relationship in partner management system

Pattern 3: Security Baseline Deployment

1. GET /managementTemplates — list available baseline templates
2. GET /managementTemplateStepTenantSummaries — check deployment status across tenants
3. Identify tenants with missing or partially deployed baselines
4. For each gap: generate remediation task with specific steps and GDAP role required
5. Track deployment via GET /managementActionTenantDeploymentStatuses
6. Re-score tenants after remediation

Pattern 4: Cross-Tenant Alert Triage

1. GET /managedTenantAlerts?$filter=status eq 'active'&$orderby=severity desc — get active alerts
2. Group alerts by tenant and severity
3. For critical alerts (risky users, malware): prioritize immediate remediation
4. For warning alerts (low MFA, compliance drift): schedule for next maintenance window
5. Update alert status after remediation
6. Log actions in partner ticketing system

Remediation Planning

For each Red/Yellow finding, generate an actionable remediation item:

1. What: Plain-language description of the issue
2. Why: Risk if not addressed (with severity classification)
3. How: Specific Graph API calls or admin portal steps
4. Effort: Estimated complexity (Quick Fix / Moderate / Complex)
5. Impact: Which users/systems are affected
6. GDAP Role: Which delegated role is required to remediate

Progressive Disclosure — Reference Files