Today at Microsoft Ignite in Orlando we announced several changes that we hope will help Exchange Online Administrators get their admin tasks completed more efficiently and effectively. We’re bringin...
Updated Nov 05, 2019
Version 2.0
Blog Post
Here I am, back again with yet more complaints (so sorry, but I just can't get past these issues). This one is to do with the new Exchange Admin Center, under Recipients > Resources > with a resource mailbox selected > Resource Delegates.
Resource Delegates need Send on Behalf, so they can respond with accept/tentative/decline on forwarded meeting requests (when forwarding to delegates is set to True). What they DON'T need is FullAccess and Send-As. At best, they would need the Editor permission on JUST the Calendar.
The new interface shows us that now even the Exchange developers are confusing this, and now we have "Resource Delegates" being confused with FullAccess and Send-As permissions. What this will do, is tell Admins and therefore users, that "Resource Delegates" should have FullAccess and Send-As, but in reality we still know here and now that this is wrong and bad. It's a big huge error that needs to be corrected. What you will end up doing is setting the path to bad resource mailbox practices world-wide. Meetings will get created from the Resource mailboxes themselves, and the resources will end up being the Organizer of meetings (which is very bad, just look at the "Important" note here - Create and manage room mailboxes).
Last thing - where the heck are the GUI options for AllBookInPolicy, BookInPolicy, AllRequestInPolicy, RequestInPolicy ? These have been missing since (and including) Exchange 2013. It tells me that you forgot about these, or are just boycotting them in favor of FullAccess and Send-As, thinking they accomplish the same things. They don't, this is just bad bad bad. Can't state it enough, it's bad. It's a real problem that will spread all around the world and filthy up Exchange Online deployments everywhere (on-premises deployments too).
The other issue with FullAccess on resources is that now the users with FullAccess will by default have AutoMapping enabled, and their precious cycles in Outlook will be used up. Not only in Outlook though, also their quota against their assigned throttling policy will be needlessly used up. And not only that, just a huge waste of time and resource for these users accessing/synchronizing the other folders in the resource mailboxes, when all these "Resource Delegates" need is, like I said - at best, Editor access to the Calendar.
This one is just as bad (actually way worse) as the issues I mentioned in my earlier reply. You are teeing admins and users up for very bad practices, against even your own recommendations. This is not good.