@Erase4ndReuseMedia 

we have exchange mailbox agent onpremise ,hybrid, exchange online environment support

https://documentation.commvault.com/11.20/exchange_mailbox_user_mailbox.html

https://documentation.commvault.com/2023e/expert/exchange_mailbox_agent.html

please review above documentation reference once.

I am specifically referring to a traditional backup agent, rather than the clunky archive agent.

@Erase4ndReuseMedia 
I understand what you're referring to, but in terms of the Exchange mailbox agent, "archive" is just a terminology distinction. Data backup is the primary function. If you don’t perform any cleanup or stubbing on the archived data, it essentially remains the same traditional backup approach, where email data is backed up to secondary storage for restoration purposes.

when compared to traditional backup, you won’t see synthetic full or differential jobs, as this agent operates on a V2 incremental forever model.
 

Currently this is the solution Commvault is havign for mailbox agent protection.

kindly let us know what operations you are lookign forward which is missing / helps simplify so we can understand more details.
thank you!

Archive is a terminology distinction based on the mechanism, and I don’t agree that it is essentially the same as the traditional backup approach.  

The current approach requires significantly more effort to maintain over the traditional mailbox agent, and has introduced significant limitations. I would like to see a return to:

• Job-based retention so that secondary copies can be used for storage tiering purposes \ tape. 
• Subclients to allow better content targeting, storage policy distribution, and scheduling. 
• The ability to recovery backups from a secondary copy, independent of the availability of the Index Server \ Index Server Cloud
• Point-In-Time recovery capabilities that aren’t dependent on the recovery of the entire Index.