Separate update eligibility from license validity
Current inspected release: beta17, private Premium preview. Read the current workflow and acceptance limits. Earlier beta references describe the retained feature history, not a newer public/stable stamp.
Products define future-purchase site limits1–1000 and update days0–36500;0 update days means unlimited. New purchases/grants snapshot the current policy. Changing the product does not silently rewrite existing licenses. Old pre-policy licenses retain unlimited updates and one management slot until the owner explicitly changes them.
For an existing license, the owner can set an updates-through UTC date (ends23:59:59) or leave it blank for unlimited. Releases originally published by that cutoff remain eligible; newer ones disappear/refuse delivery. Extending updates does not re-sign a key, expire perpetual use rights or renew an already expired use license.
Reducing site limits below current registrations is refused: remove the excess sites first. Suspended/revoked/refunded/expired-use licenses do not become valid merely because their update window is extended. Both portal and direct machine downloads need the same eligibility checks.
