Introduction
An environment entitlement is bound to one Business Central environment and one Microsoft Entra tenant. When a project ends, a sandbox is rebuilt or a customer changes, and the entitlement needs to move, this process needs to be applied. This article sets out exactly when that is allowed and what deactivation changes inside the product.
Read it before you plan a move rather than after, because the timing is crucial.
The 90-day rule
The three statements below cover the rules around this process:
- An environment entitlement can move to another environment or tenant only after 90 days have passed since its most recent activation.
- Deactivating does not immediately free the licence. If you deactivate before the 90-day period has ended, the entitlement remains consumed and linked until 90 days from the most recent activation have passed.
- Once that point is reached, a deactivated entitlement can be reassigned to another environment or tenant.
This idea is similar to how Microsoft Visual studio subscriptions works, where a subscription can only be reassigned to a different person after a minimum number of days have passed.
The legal rules mentioned above are defined in clause 4.3 of the Bluefort Intelligence EULA. This article explains how it works in practice and the authority encapsulated by the EULA itself.
Examples
The clock always runs from the most recent activation, not from the date of deactivation.
| Activated | Deactivated | When the entitlement can be reassigned |
| 1 March | 30 March | 30 May — 90 days after the 1 March activation. Deactivating on 30 March does not release it early. |
| 1 March | 1 October | Immediately — more than 90 days had already passed since activation. |
What deactivation changes inside ARVO Studio
Deactivation is not equivalent to an uninstall process – It changes what the environment can do, not what is stored within it.
- AI actions stop for that environment. No new analysis, generation or testing work can be started there.
- Existing projects, findings and records remain readable together with designs, test cases, generated documentation and the approval history, these all remain available.
- A deactivated or lapsed licence puts the sandbox into a reduced mode. It does not uninstall ARVO Studio and it does not delete project history.
[ Screenshot placeholder — an ARVO Studio environment in reduced mode, showing that projects remain readable while AI actions are unavailable. ]
Before you move an entitlement
Check the date of the most recent activation first, then work out the earliest date the entitlement can be reassigned. If that date has not been reached, plan around it: deactivating early does not bring it forward. Where the move is part of a customer transition, agree the timing with your Bluefort contact person in advance so that the new environment can be provisioned as soon as the entitlement becomes free.