There are other log tables that capture data unnecessary for long term retention, some of which are utilized extensively by ISV products (example: Sales Tax calculation/capture ISVs). It would be helpful if there were other tools (or better yet, a scalable framework for selecting some of these other tables for periodic purge, along with the obligatory capability for selecting the amount of history to retain by table.

Example: sysencryptionlog - this table is used extensively by common ISV sales tax solution providers, and has raised alerts as a key "offending" table during assessment of high transaction tables for purge consideration to reduce Azure license cost impact. Regrettably, there is no way out-of-the-box to cleanup this table.