> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/extensions/microsoft-cloud-solution-provider/azure-lighthouse.md).

# Azure Lighthouse

Azure Lighthouse is a Microsoft solution that enables seamless multi-tenant management. It lets service providers, such as SoftwareOne, manage multiple environments in one place without switching accounts.&#x20;

SoftwareOne uses Azure Lighthouse to provide management and support services across customer Azure environments while maintaining customer control, visibility, and security.

### Benefits <a href="#why-azure-lighthouse-is-crucial-for-your-business" id="why-azure-lighthouse-is-crucial-for-your-business"></a>

Azure Lighthouse helps you maintain control of your Azure environment while enabling SoftwareOne to deliver management and support services efficiently.

* **Access control** – You control which users can access your environment, which resources they can manage, and which actions they can perform.
* **Transparency** – Actions performed by SoftwareOne are logged in the Azure Activity Log, providing visibility into changes made within your environment.
* **Security and governance** – SoftwareOne has read-only access by default, unless elevated permissions are granted through your explicit approval.

### How SoftwareOne uses Azure Lighthouse

Azure Lighthouse enables SoftwareOne to manage customer Azure environments through a centralized management model.&#x20;

This approach helps SoftwareOne:

* Manage multiple Azure environments efficiently.
* Apply standardized operational processes.
* Follow role-based access protocols.
* Deliver support while maintaining customer-defined access controls.

### Impact of not activating Azure Lighthouse

Without Azure Lighthouse, SoftwareOne may have limited ability to manage and support your Azure environment efficiently.

**For customers**

* Reduced visibility into delegated access and management activities.
* Increased administrative effort for managing service provider access.
* Less streamlined support and operational management.

**For SoftwareOne**

* More complex management of customer Azure environments.
* Reduced operational efficiency.
* Additional administrative overhead when providing support and managed services.

### Support

If you have any questions about the Azure Lighthouse activation process, contact the **SoftwareOne Services Support** team. For details, see [Contacting SoftwareOne Services support](/extensions/microsoft-cloud-solution-provider/additional-resources/support-options-for-csp.md#how-can-i-contact-softwareone-services-support).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform.softwareone.com/extensions/microsoft-cloud-solution-provider/azure-lighthouse.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
