Microsoft Power Platform
TMA-POWERPLATFORM-TENANT-ISOLATION
Ensure Power Platform tenant isolation is enabled
HighLevel 2Automatedpower-platform
Description
Tenant isolation blocks connectors from authenticating to (and moving data to or from) other Microsoft Entra tenants. Set PP_TENANT_ID to the tenant GUID. Requires Microsoft.PowerApps.Administration.PowerShell and an authenticated session (Add-PowerAppsAccount) as a Power Platform administrator; the audit throws if the module is missing.
How it is checked
Audit method: Shell command
shell
$ErrorActionPreference = 'Stop'; if (-not (Get-Command Get-TenantSettings -ErrorAction SilentlyContinue)) { throw 'Microsoft.PowerApps.Administration.PowerShell is not loaded: run Add-PowerAppsAccount first' }; if (-not $env:PP_TENANT_ID) { throw 'Set PP_TENANT_ID' }; $p = Get-PowerAppTenantIsolationPolicy -TenantId $env:PP_TENANT_ID -ErrorAction Stop; if ($p.properties -and $p.properties.isDisabled -eq $false) { 'compliant' } else { 'noncompliant' }- Expected output
compliant
How it is fixed
Fix method: Guidance or infrastructure patch
Power Platform admin center > Security > Identity and access > Tenant isolation > On, adding allowed inbound/outbound tenants as needed (or Set-PowerAppTenantIsolationPolicy with properties.isDisabled = $false).
Properties
- Operating systems
- Any
- Tags
- power-platformdata-loss
- Reference
- CIS Microsoft Dynamics 365 Power Platform Benchmark v1.0.1 - Tenant isolation (no dedicated CIS benchmark exists for Power Platform)
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
shell
tmaegis scan --target power-platform --level 2