A healthcare company must guarantee that a new AuditLog table in an Azure SQL Database can only ever have rows appended — never updated or deleted — and must provide cryptographic proof to external auditors that no historical records have been tampered with. The team wants a native feature that requires no application-layer hashing logic. Which feature should you configure when creating the table?