At my current company we're running an on-prem Exchange 2016 email server, and when we have to manage email forwarding for employee absences in certain departments that need coverage, we have users' Outlook clients set up with an automatic reply forwarding rule to forward emails to a shared mailbox for the department so emails from customers don't go unanswered. This is great for planned absences obviously, but sometimes we need to turn the automatic replies and forwarding on for unplanned absences as well. Normally I just toggle the automatic replies and thus the forwarding rule on through Exchange Powershell using Set-MailboxAutoReplyConfiguration. However, I've noticed that when I do this, once the user comes back and turns off automatic replies in their Outlook client, their mail forwarding rule is still being applied until I go back into Exchange Powershell and disable the automatic replies using Set-MailboxAutoReplyConfiguration again. The odd thing is that when the user turns off the automatic replies in their client, the automatic replies turn off right away without issue. It's just the forwarding rule that sticks around until I disable the already-disabled automatic replies on the server end.
So I'm wondering if there's a step or something I'm missing in this process/setup where something is not telling Exchange to disable the forwarding rule from the client side, even though the automatic replies are turned off. Anyone encountered anything like this before?
I suppose I could use Powershell to manually remove the automatic reply rule and then just use Powershell to forward at the same time I turn on the automatic replies, but I really love the convenience of just toggling the automatic replies on to enable the forwarding.