Azure SQL Database automatic growth near configured maximum size

This question clarifies how Azure SQL Database handles automatic storage growth as a vCore-based General Purpose database approaches its configured maximum size. Service limits indicate that automatic growth occurs in 10 GB increments for vCore databases under General Purpose and Business Critical, while the tier maximum is 4 TB per database. It is unclear whether a growth increment can exceed the configured maximum size, or whether the database stops growing once the current size reaches the configured limit even if space remains below the tier cap.

The purchasing model and configured maximum size must be interpreted separately from the absolute tier limit. Operators need to know whether automatic growth pauses at the configured maximum or attempts the next 10 GB increment and fails when the limit is reached.

Does automatic growth stop at the configured maximum size, or can the final increment temporarily exceed it before enforcement? Is the configured maximum size the authoritative boundary for growth, or does the 4 TB tier cap govern behavior independently?