The value I wrote in the tenant was refused: the higher scope's floor
You wanted to change a configuration value, and inlorus said the value cannot be weaker than the higher scope's. A floor can be tightened, not loosened.
For: Tenant administrator, Account administrator, Platform administrator
What happened
On the tenant's Configuration screen you wrote a new value for a setting and got this answer: “"lifecycle.tenantRetentionDays" cannot be weaker than the higher scope's value — this key has a floor set by a higher scope. You can write a stricter value, but not a looser one.”
Why it happens
For some settings the platform or the account sets a floor. A floor is the limit below which lower scopes cannot loosen that setting; for example, for a retention period a tenant can write a longer period but not a shorter one. The purpose of a floor is to make sure a rule is applied at least at a certain strictness in every tenant.
What inlorus does
- It compares the value with the floor before writing it and refuses it if it is weaker.
- It offers no exemption path; the floor cannot be overridden in the tenant.
- In the refusal message it tells you what you can still do: you can write a stricter value.
What you do
- On the account's Policies screen (or the platform's Policies screen), read this setting's floor and the higher scope's value.
- If what you need stays within the floor, write a stricter value.
- If a looser value is really needed, discuss it with the admin of the scope that set the floor; the change is made there.
How to keep it from happening again
- Before changing a setting, check on the Configuration screen where the value comes from and whether there is a floor.