well, add AAM as a managed element to it. So, in AAM, make a "trusted server" of name "smgr" and password "whatever" with the SMGR IP. You can use that to point SMGR to AAM to grab its config.
In SMGR, under "admnistrators" you can build out granular permissions. You can make sure they can't add/delete mailboxes, only change existing. Not sure if you can avoid people being able to change the password but not class of service - poke around.
And, I hope you're on latest SMGR/AAM. There's an "enhancement" in there where when clicking on a user, it grabs it's mbx state live from AAM. It didn't do that in 6.3 and only sync'd at night.
To say, if you locked out after 4am and phoned in a ticket to your helpdesk, AAM's webpage would show the mbx locked, SMGR would show "locked? no!". Upon saving the page with a new password and the lock parameter not changing, SMGR would save the new password but with the lock state having not changed, it didn't unlock it. You'd have to lock the mbx and then unlock+change password.