View Current Automapping setting
Currently there is no way to view whether Automapping of a mailbox is enabled or disabled in office 365. It would be nice to be able to view this value in either powershell or the GUI.
Additionally it would be nice to be able to turn automapping on or off via the EMC instead of only powershell.
Anonymous
shared this idea
42 comments
-
Chris
commented
Please and thank you!
-
Michael Burke
commented
Admin's should expect to have to use PowerShell to properly admin the tenant. Let's not get lazy. Learn PS!
-
Jason
commented
So many years for exchange and online, still can't check this.
It should not be so hard to add this in PS -
Anonymous
commented
This is rediculous. We are unable to check auto mapping status via PS.
-
David Abrgel
commented
will it happen eventually or it will never happen ?
-
Anonymous
commented
We've been begging for this for YEARS! When will it be implemented?
-
Chris
commented
yes please!
-
Jeremy Lutze
commented
I agree def needed.
We have a staff with 15+ shared mailboxes they cannot even open MS Outlook without it having issues from Crashing Outlook, Out-of-Memory Errors or not allowed to send/receive emails.
They advised disabling "MAPI" under mail features which would affect everyone from not seeing the mailbox, using distribution groups or powershell feature.
In a way I am amazed MS Outlook never fixed have multiple shared mailboxes open as this bug has been around since Outlook 2007
(Advised by Microsoft too many connections)
-
Anonymous
commented
I absolutely agree on this. At this moment it is impossible to know if automapping is true or false. Not even with powershell. We need to check now and then the status on a mailbox.
-
Alxeander Sentyurin
commented
Really annoyng dumb remove-add permission procedure just for check automapping. It would be nice to be able to view this value in either powershell.
-
Anonymous
commented
I agree. Being able to view this on a per shared mailbox basis would be very essential to us.
-
Edwin Lloyd-Jones
commented
Please add this feature the inability to confirm if the setting is there when users report issues with auto-mapping is a real pain. All we can do is re-run the command and see if it helps.
-
Anonymous
commented
Please expose these attributes in the Exchange Management Console and allow their management there. For me, because I rarely have to use it and thus am not very familiar with it, PS is a real pain to use, especially if I just want to make one tiny change like this to a single user account. As it is, when I set up a new user I have to then start a PS session, figure out the syntax of the commands, and run one or more scripts to get the job done. It should be a simple checkbox in the console: Automapping for this user ON/Off. Status would show in the console, and life would be easy. Thanks.
-
Steve
commented
On premise you can check the back links on a user account, we moved to group membership only having full access to guarantee no automapping.
-
Phil Shand
commented
Automapping settings have really caused a lot of issues with shared mailboxes. Not being able to check this setting when your dealing with hundreds of users when dealing with important company shared office365 mailboxes such as payroll and accountspayable is becoming an essential value to know
-
JH
commented
Would certainly be helpful to view the state of AutoMapping per mailbox. I can understand it might not be worth the effort to extend it to the Web UI but it should be available via PS!
-
Clayton Gibson
commented
Please add this. Can't believe I can't get this data from PS.
-
Anonymous
commented
I needed this today and I'm absolutely bafelled that it isn't possible! %-/
-
Patrick J. McDonnell III
commented
Please fix this and/or add the feature in O365! Very strange that verify a user has automapping enabled, you have to use powershell to remove and then add the permissions! And still there's no way to confirm!
-
Daniel Cooper
commented
Weird that it can be SET using set-mailboxpermission ($true/$false) yet there is no way to get- automapping settings ... *sigh* ... MS, really? Please fix.