Feedback by UserVoice

Tom S

My feedback

  1. 13,254 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    499 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tom S commented  · 

    Our tenant domain has my name embedded in it! I don't know who did it or why, but didn't think it mattered since we could apply our own domain(s) to Exchange and set the default. Not until we started working with SharePoint and OneDrive did we realize it would be an issue. Also, the current setup allows people not associated with a company to "steal" its domain so that if they try to move to O365, they cannot have their proper name on SharePoint or OneDrive.

    Tom S supported this idea  · 
  2. 744 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    46 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →

    Our service is designed to protect the resources and ensure that certain users will not overwhelm it and cause latency for others. This limit is in place to protect against spike sending that we wish to discourage. As such, we have no plans to change the limit for regular mailboxes.

    Where possible, we encourage customers who have these requirements to seek solutions that do not send emails all at once, can make use of DLs, or use services like Dynamics or third-party services to send large volumes of emails to customers or student and parents.

    However, we are thinking about alternatives we can provide to solve this issue of higher sending for automated email scenarios to address this customer need.

    An error occurred while saving the comment
    Tom S commented  · 

    Microsoft is not applying the limit properly, or it's description of the limit is wrong. A 30 message per minute limit should apply the "554 5.2.0" exception to the MESSAGE, not some of the recipients for that message. Our problem is that If we send a message to several recipients and hit the limit, it may fail one or two of them but send to the rest. If I re-submit the email, it'll cause duplicates for some of the recipients (bad). If I delete the recipients that already received the message, then the other recipients will not see those on their copy of the email (also bad).

Feedback and Knowledge Base