Subscription transfers in and out of the Microsoft Entra tenant should be blocked for everyone
This check looks at the subscription policy that controls whether Azure subscriptions can be moved into or out of your Microsoft Entra tenant. The safe setting is to permit no one to do either, with changes made only through a deliberate exception.
Why it matters
A subscription holds your resources, your data and your role assignments. When it is moved to another Entra tenant, the directory that governs who can sign in to it changes. An owner who can move a subscription out can, in effect, take its workloads away from your identity controls, your Conditional Access rules and your monitoring.
The reverse also matters. Moving an outside subscription into your tenant can bring resources and role assignments that nobody on your team reviewed. Microsoft documents a subscription policy that lets a tenant administrator decide who may do each of these. Setting both directions to "Permit no one" turns a risky action available to many owners into one that needs a conscious policy change first.
Treat it as a guardrail that costs nothing day to day, since legitimate transfers are rare and planned.
How to check it yourself
Portal: Azure portal → Subscriptions → Advanced options → Manage Policy. Read the values for "Subscriptions leaving the Microsoft Entra directory" and "Subscriptions entering the Microsoft Entra directory". You need to be a Global Administrator who has elevated access to see the page.
Read-only command (Azure CLI, a GET request only):
az rest --method get --url "https://management.azure.com/providers/Microsoft.Subscription/policies/default?api-version=2021-01-01-privatepreview"The safe result shows both directions blocked and no exempted principals, unless you have a documented exception. The API version is a preview version at the time of writing, so confirm it in Microsoft Learn if the call fails.
How to fix it
Portal: on the same Manage Policy page, set both options to "Permit no one". If a small group of administrators must keep the ability, add them as exempted principals instead of opening it to everyone, and write down who and why.
Script (this changes tenant policy, so review it and run it yourself):
az rest --method put --url "https://management.azure.com/providers/Microsoft.Subscription/policies/default?api-version=2021-01-01-privatepreview" --body '{"properties":{"blockSubscriptionsLeavingTenant":true,"blockSubscriptionsIntoTenant":true}}'ConfigCobra reads this setting and never writes it.
What changes when you fix it
Subscription owners lose the ability to move a subscription to or from your tenant on their own. Anyone planning a merger, a hand-over to a customer or a tenant consolidation will need an administrator to lift the block or use an exempted account for the duration of the move.
Existing subscriptions, resources and role assignments are not touched. Nothing stops working. The effect shows up only when someone tries a transfer, so tell subscription owners and your cloud team about the new rule and where to request an exception.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft Azure Foundations v6.0.0 | 5.6 | Level 2 |
Check this on your Microsoft Azure
ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, read-only.