You should give all Admins a CHOICE as to whether a new feature gets deployed and you should put it in the GUI.
Admins should have control over their clients' features. ESPECIALLY a Corporate User. We need to be able to turn off features globally from the GUI--not all customers are using Windows machines--some are working from tablets--and we should not have to use Power Shell to turn off features or see who is entered into our address list.
This is why we use the on-line service--so we do not have to run the mail server from our server closet--that means we need a good user interface that allows us to control the features.
Example, new CLUTTER feature was rolled out and it literally wrecked our mail--mail from people we needed to get mail from went to clutter and the ADMIN had no control to simply shut it down from a GUI without using Power Shell--this is wrong.
Sway was rolled out in the "on" position. We do not want our mail customers using it and did not know a thing about it until we found it enabled on the system. Thank goodness there was a button to turn it off for the whole account.
Nothing should be rolled out without Admin knowing about it and having the option to choose whether it is enabled or disabled for their mail clients.
I absolutely agree with this- rather than having to visit each user in the GUI to remove something, we should be able to turn things off and on at a global level. Features should be disabled by default, and then we could just assign what we choose.
To start, however, I would be satisfied with a decent powershell command to disable features, instead of this nonsense of assigning licenses AGAIN and setting a variable of $options and then using a disabled plans switch, which is hugely labor intensive, difficult, and often doesn't work because there are SO MANY PLANS and SO MANY OVERLAPPING FEATURES, and if you forget to include a filter for isAssigned for licenses, you are in trouble because now you've licensed users you never meant to license at all.
Please add an option for -enabledplans so that we could assign a license and the features we want, instead of forcing us to enable everything and then disable each feature via -disabledplans.