Microsoft Exchange 2013 iApp - Can't login to OWA or ECP if more than one server is active in pool

I don't have enough insight into the process to be able to tell you if it will get escalated by then. The engineer who gets the case will need time to review it, as well.

Also, I'd open a case with Microsoft on this, since it's very possible that something is going on with the CAS that's causing this.

You can work around the problem and still get the EAC restriction by adding the command "persist cookie insert 0" to the "/owa*" case in the pool assignment iRule that was created by the iApp. You'll need to go into the properties of the iApp and disable strictness first.