Feedback by UserVoice

rayco

My feedback

  1. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    rayco supported this idea  · 
  2. 1,999 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    80 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    rayco commented  · 

    This was adversely affecting us as well and believe I found a workaround. Try this….

    1. Remove all delegated permissions
    2. Wait for it to drop from Outlook folder list (set from Automapping) and/or remove direct access setup through File/Account Settings
    3. Re-add permissions - Add-MailboxPermission -Identity sharedmbx@domain.com -User delegate@domain.com -AccessRights FullAccess -AutoMapping:$FALSE
    4. Manually re-add to Outlook – File/Add Account - authenticating with delegate users creds
    5. Can you see the private emails now? It appears there's a difference in access with Automapping vs. manual config as this is also the same fix I need to setup a rule in a shared mailbox that requires the action: have a server reply using a specific message.

    I forgot to add - this is an unacceptable workaround as most of us have too many shared mailboxes to work through. Seems obvious Microsoft that this needs to be resolved with a better solution.

    rayco supported this idea  · 
  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    rayco shared this idea  · 
  4. 51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    rayco supported this idea  · 
  5. 169 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    rayco supported this idea  · 
  6. 246 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Office 365 Security & Compliance » Reports  ·  Flag idea as inappropriate…  ·  Admin →

    1. Click into “details”.
    2. Choose “connector report”.
    3. Choose “request report”.
    4. Answer the questions in the wizard, clicking “Next”, “Next”, and “Save”.
    5. Wait for the report to come to the email address specified. It will contain the following fields:
    message_id, direction, sender_address, recipient_address, connector_name, connector_type, tls_version, tls_cipher

    With the Message_Id value, you can combine this with MessageTrace to get the Subject.

    If this does not help, please provide more information as to the scenario and detail that is missing. Thank you for the feedback!

    An error occurred while saving the comment
    rayco commented  · 

    hi @scott landry. as mentioned, i can't seem to find the following fields: message_id, direction, sender_address, recipient_address, connector_name, connector_type, tls_version, tls_cipher in my connector report.

    am i missing something? thanks!

  7. 69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
  8. 55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    rayco commented  · 

    seriously need this feature for both Exchange/Outlook and AAD. it would sure be nice so employees can validate names when dynamic groups are being used for access.

  9. 43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Office 365 Security & Compliance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    rayco commented  · 

    is this really the intended functionality? i've now wasted too much time troubleshooting and there should not be any difference between creating the rule in Outlook or OWA. the alert should trigger either way!

    rayco supported this idea  · 

Feedback and Knowledge Base