azure-lighthouse

Enable cross-tenant Azure management for MSPs without guest accounts.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/tomz/agent-skills --skill azure-lighthouse-tomz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-lighthouse
Source: https://github.com/tomz/agent-skills/tree/main/azure-lighthouse
Command: npx skills add https://github.com/tomz/agent-skills --skill azure-lighthouse-tomz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Azure Lighthouse enables Managed Service Providers (MSPs) and enterprise IT teams to manage resources across multiple Azure tenants from a single control plane, without requiring guest accounts or per-subscription logins in each customer tenant.

Core Features & Use Cases

  • Delegated resource management across tenants via ARM projections
  • Just-in-time access (PIM) for elevated actions
  • Onboarding templates and cross-tenant governance for MSPs

Quick Start

Deploy the lighthouse delegation template in the customer tenant to grant access for MSPs.

Frequently Asked Questions about azure-lighthouse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Azure resources across multiple customer tenants without guest accounts?

Azure Lighthouse enables cross-tenant delegated resource management for MSPs without guest accounts. It uses ARM projections to establish a single control plane, allowing you to manage multiple customer tenants without requiring per-subscription logins or individual guest user provisioning.

How do I deploy cross-tenant delegation templates for Azure Lighthouse onboarding?

You can deploy cross-tenant delegation templates by applying ARM templates or Bicep files directly in the customer tenant. This onboarding process grants the Managed Service Provider specific RBAC boundaries and delegated access to manage the designated Azure resources.

Does Azure Lighthouse support just-in-time access for elevated cross-tenant operations?

Yes, Azure Lighthouse supports just-in-time (JIT) access through Privileged Identity Management (PIM). This allows MSPs to request temporary, elevated RBAC activations for specific cross-tenant management tasks, ensuring governance and minimizing standing access to customer resources.

What is the best way to enforce RBAC boundaries for MSPs managing multiple Azure tenants?

The best way to enforce RBAC boundaries is through Azure Lighthouse delegated access. It provides sample definitions and assignments that restrict MSP permissions strictly to the roles defined during the ARM template onboarding, ensuring ongoing operational governance across customer tenants.

Can I use Bicep and CLI commands to manage Azure Lighthouse definitions and assignments?

Yes, Azure Lighthouse supports the use of Bicep and Azure CLI commands to manage definitions and assignments. This allows you to automate the deployment of cross-tenant governance configurations and enforce delegated access boundaries programmatically across customer environments.

When do I need cross-tenant delegated access for Azure resources instead of standard directory roles?

You need cross-tenant delegated access when managing resources across multiple Azure tenants as an MSP or enterprise IT team. It eliminates the need to switch directories or use per-subscription logins, providing a single control plane for ongoing operations and governance.