Azure SQL Database Point‑Time Restore: inability to roll back individual schema objects after committed change

Goal: determine whether Azure SQL Database supports rolling back individual schema objects (e.g., a dropped column) after a committed schema change without restoring the entire database, given Point‑Time Restore (PTR) and Long‑Term Retention (LTR) constraints.

Constraints: PTR is limited by service‑tier retention (up to 35 days General Purpose, 7 days Basic/Silver) and must be available before the change; LTR can extend coverage but must be pre‑configured, and any restore operation replaces the whole database, which can introduce version skew with subsequent migrations. There is no native T‑SQL or portal feature for object‑level rollback.

Questions: Does enabling LTR after a schema change allow restoration to a pre‑change state, or must LTR be configured beforehand? When a PTR‑based restore is performed, does it automatically reapply later valid migrations, or does it leave the database version‑skewed relative to the original? Is there any supported method to roll back a single schema object without a full‑database restore?