Impliancy connects directly to your Microsoft Power Platform tenant using a service principal.
Each connected tenant is treated as an isolated governance space with its own environments, artifacts, settings, and compliance rules.

Tenant vs subscription

Tenant

A Microsoft Entra ID tenant is the identity and directory boundary of your organization. It contains:

• All Power Platform environments
• All users
• All service principals
• All Power Apps, Flows, Bots
• All Dataverse instances

Impliancy connects at the tenant level, because this is where governance needs to happen.

Subscription

An Azure subscription is a billing container for Azure resources such as VMs, storage accounts, and databases. It is not the boundary used by the Power Platform.

Power Platform environments do not belong to an Azure subscription. They belong to the tenant.

This is why subscriptions do not play a role in Impliancy:

• You can have several Azure subscriptions in the same tenant
• You can have no Azure subscriptions at all
• Power Apps, Flows, Dataverse, and Copilot Studio Bots do not live inside subscriptions
• Governance of the Power Platform is always tenant based

Impliancy therefore only cares about tenants → environments → artifacts, and subscriptions are irrelevant for governance.

Tenant independence

Each tenant connected to Impliancy has:

• Its own environment list
• Its own compliance configuration
• Its own inventory and inactivity settings
• Its own ownership structure

Multiple tenants never overlap, ensuring clean separation for service providers (upcoming).

Multi tenant mode (upcoming)

If you are a service provider, you can onboard several client tenants into a single Impliancy instance and switch between them instantly.
Each tenant remains fully isolated.