There are still older ARM specs that use interface templates, which can result in confusing deprecation messages, and inexact usage of suppressions to get rid of the warnings (because suppressions cna only happen at the interface definition).
Add a section to troubleshooting describing the deprecation messages and options for how to deal with them
Talk to breaking change folks about promoting breaking changes that do not represent API changes, such as removing 200 responses for asynchronous APIs.
There are still older ARM specs that use interface templates, which can result in confusing deprecation messages, and inexact usage of suppressions to get rid of the warnings (because suppressions cna only happen at the interface definition).