# Least privilege for third-party identities in Azure means narrow Lighthouse authorizations and reviewed multitenant app consent

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Third-party identities in Azure are the partner users, delegated Lighthouse authorizations and multitenant application service principals that act in your tenant. Microsoft's documentation, read 16 Nov 2026, lists which roles Lighthouse supports and how consent creates service principals. This guide covers the steps and measures.

## Vendors reach Azure through Lighthouse delegation, multitenant app consent or guest accounts

Azure Lighthouse lets a service provider manage resources in a customer's tenant from the provider's own tenant. Microsoft says customers keep control over the scopes they delegate and the permissions allowed, can audit provider actions and can remove access at any time. Delegated users can be seen in the customer's activity log.

Each Lighthouse authorization pairs a principalId in the managing tenant (user, group or service principal) with a built-in role. Microsoft states Lighthouse does not support custom roles, does not support the Owner role, supports User Access Administrator only to assign roles to a managed identity in the customer tenant, and does not support roles with DataActions or with several Microsoft.Authorization write and delete actions.

A multitenant application is registered once and, when a user or admin in another tenant consents, a service principal is created in that tenant. Microsoft says app-only permissions always require tenant administrator consent, and that an administrator can revoke the app's access in Enterprise applications.

Microsoft Entra B2B collaboration represents partners as guest user objects in your directory, using their own credentials.

## Microsoft documents scope, group-based delegation and eligible authorizations as the controls

Microsoft's recommended practices for Lighthouse say to enable the minimum access needed, assign permissions to security groups using the principle of least privilege, review membership regularly and require multifactor authentication in both tenants. Microsoft states that Conditional Access policies on a customer tenant do not apply to users who reach the customer's resources through Lighthouse; only policies set on the managing tenant apply.

Microsoft also says that when you onboard through a public managed service offer, every group, user or service principal in the plan has the same permissions for every customer who buys it. Separate access needs a private plan per customer or onboarding by Azure Resource Manager template.

Eligible authorizations let users in the managing tenant temporarily activate a higher role instead of holding permanent privileged assignments; Microsoft notes licensing requirements. Microsoft also advises including an authorization with the Managed Services Registration Assignment Delete Role, so the provider can remove the delegation. Otherwise only a user in the customer's tenant can remove it.

For guests, access reviews can ask group owners to confirm that guests still have a business need, as Microsoft describes, and the [methodology page](/methodology/) explains how this site treats such provider tools.

## Steps to bring third-party access in Azure to least privilege

- List Lighthouse delegations (the Service providers page in the Azure portal), enterprise applications from other tenants, and guest users with Azure role assignments.
- For each delegation, record the provider, scope, roles and the business owner. Remove delegations with no owner.
- Replace broad built-in roles in an authorization with the narrowest built-in role that does the job, at resource group scope where possible.
- Ask providers to use Entra groups and eligible authorizations, and to require MFA for every user in their managing tenant.
- Review multitenant application service principals in Enterprise applications: check consented permissions, remove those the app no longer uses and revoke apps that are not in use.
- Turn off end-user consent where a tenant administrator should approve third-party apps, using the Consent and permissions setting Microsoft documents.
- Create recurring access reviews for guest users and for groups with guests.
- End each delegation when the contract ends.

## Roles and settings to avoid for third parties

| Role or setting | Documented reason (Microsoft, read 16 Nov 2026) | Use instead |
| --- | --- | --- |
| Owner in a Lighthouse authorization | Microsoft states Lighthouse does not support the Owner role. | A narrower built-in role. |
| Contributor for a provider that needs read access | Microsoft says to enable only the minimum access necessary to manage the resources. | Reader or a service-specific role. |
| A public plan with one group for all customers | Microsoft says every group in a public plan has the same permissions for every customer who buys it. | A private plan per customer or ARM template onboarding. |
| Relying on customer Conditional Access for provider users | Microsoft says those policies do not apply to users coming through Lighthouse. | MFA enforced in the managing tenant too. |
| Applications with unreviewed app-only permissions | Microsoft says app-only permissions require tenant administrator consent and can be revoked in Enterprise applications. | Reviewed consent and revocation of unused apps. |

## Measure delegations, consented permissions and use

Count active Lighthouse delegations, the roles each carries, and the share with an assigned business owner. Count multitenant applications with consented permissions and the number of permissions per application. Compare granted permissions with the permissions the application's sign-ins and activity show.

A delegation or app with no recorded activity in the review window is the first candidate for removal. See [privilege creep](/privilege-creep/) for how these accumulate, and [the glossary](/glossary/) for definitions.

Related guides: [AWS third-party identities](/guides/aws-third-party-identities/) and [Google Cloud third-party identities](/guides/google-cloud-third-party-identities/).

## Related pages

- [Least privilege for human users in Google Cloud](/guides/google-cloud-human-identities/)
- [Least privilege for service identities in Google Cloud](/guides/google-cloud-service-identities/)
- [Least privilege for workload identities in Google Cloud](/guides/google-cloud-workload-identities/)
- [All of them](/guides/)

## Sources

- Microsoft Learn: What is Azure Lighthouse: https://learn.microsoft.com/en-us/azure/lighthouse/overview (read 16 Nov 2026)
- Microsoft Learn: Tenants, users, and roles in Azure Lighthouse scenarios: https://learn.microsoft.com/en-us/azure/lighthouse/concepts/tenants-users-roles (read 16 Nov 2026)
- Microsoft Learn: Recommended security practices for Azure Lighthouse: https://learn.microsoft.com/en-us/azure/lighthouse/concepts/recommended-security-practices (read 16 Nov 2026)
- Microsoft Learn: Convert single-tenant app to multitenant: https://learn.microsoft.com/en-us/entra/identity-platform/howto-convert-app-to-be-multi-tenant (read 16 Nov 2026)
- Microsoft Learn: What is Microsoft Entra B2B collaboration: https://learn.microsoft.com/en-us/entra/external-id/what-is-b2b (read 16 Nov 2026)
- Microsoft Learn: What are access reviews: https://learn.microsoft.com/en-us/entra/id-governance/access-reviews-overview (read 16 Nov 2026)
- Microsoft Learn: Azure built-in roles for Privileged: https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/privileged (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://leastprivilegeprinciple.com/guides/azure-third-party-identities/
