Renewals and instance lifecycle

When enabled, automatic renewal is attempted 24 hours before the current term expires. The renewal must create only one charge for that billing period, even if a scheduled job is delivered more than once.
Link to this answer ↗

The instance continues until the paid term ends, then stops. Its reservation and local data remain in a 72-hour grace period before final release; no partial renewal or negative balance should be created.
Link to this answer ↗

The intended lifecycle allows renewal while the instance remains in grace if sufficient eligible balance is available. Once release has completed, the former instance and its local data cannot be restored.
Link to this answer ↗

Stopping is reversible and does not pause or extend the paid term. Release is permanent in the account workflow; infrastructure data deletion depends on the provisioning integration and published retention policy.
Link to this answer ↗

Yes. Automatic renewal can be disabled before the renewal attempt, and a manual renewal can be requested while the instance remains eligible. The account should always show the resulting term end and charge.
Link to this answer ↗