Feedback by UserVoice

Dros M

My feedback

  1. 6 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 →
    Dros M shared this idea  · 
  2. 48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    Dros M supported this idea  · 
    An error occurred while saving the comment
    Dros M commented  · 

    This is a feature that is desperately needed in some way shape or form. Modifying AD Objects like this is a poor solution because now every account touched shows that an admin as modified an account leading to a very long audit log to explain.

  3. 170 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Dros M supported this idea  · 
    An error occurred while saving the comment
    Dros M commented  · 

    While the newer NDR is clean and clear, users see it as an NDR and ignore it/don't read it. So while one can insert text into the message, the end user who receives it blames IT for a broken email system. Having the ability to have a custom message sent instead of the NDR for emails that are rejected by transport rules would allow for a more clear message to the end user resulting in taking proper action.

  4. 1,499 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    67 comments  ·  Office 365 Admin » Apps and App Launcher  ·  Flag idea as inappropriate…  ·  Admin →
  5. 394 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Dros M supported this idea  · 
    An error occurred while saving the comment
    Dros M commented  · 

    Would be great in Education where you want business data to not be accessible by students but need them to be able to be in the same tenant under the same domain.

  6. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
  7. 40 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 →
  8. 45 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 →
    Dros M supported this idea  · 
  9. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Dros M commented  · 

    This should be something that end users can enable on their own without involvement from an Admin. Having end users with the ability to turn on themselves would likely see a greater uptake of this additional security.

    Dros M supported this idea  · 
  10. 27 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Office.com Home Page  ·  Flag idea as inappropriate…  ·  Admin →
    Dros M supported this idea  · 
    An error occurred while saving the comment
    Dros M commented  · 

    For organizations that do not have Azure AD Premium and are federated with ADFS, why not have all password change requests be redirected back to the organizations ADFS server by default. There is already functionality built into there to handle the password changes with a known URL. Optionally provide the ability for the tenant admin to specify a location where a user should go to change their password to provide more flexibility for the tenant admins. Giving the user an error message to contact their administrator is frustrating for users and gives users the impression that something is broken because they couldn't change their password.

  11. 3,682 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    200 comments  ·  Office 365 Security & Compliance  ·  Flag idea as inappropriate…  ·  Admin →

    Azure Active Directory Conditional Access has functionality for “Countries/Regions” – see https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition

    That said, the most effective protection you can have against password spray attacks is to enable MFA and disable basic authentication. If you cannot do this for your entire organization, then blocking user access to legacy protocols like POP, EWS, IMAP and SMTP is another step you can take. Exchange Online Client Access Rules can help you to further customize (https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/client-access-rules/client-access-rules). For additional recommendations, please see Office 365 Secure Score.

    That said, please know that we are listening to feedback and working on solutions to help make Office 365 users more secure. Thank you for the feedback.

    Dros M supported this idea  · 
  12. 3,285 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    116 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Dros M supported this idea  · 
  13. 1,506 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    56 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    Dros M supported this idea  · 
  14. 4,293 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    193 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    Hi! As we announced during Ignite this year, we are releasing an open source tool by the end of the year that can be used to pull in one or more security groups (nested or not) into the membership of large Microsoft 365 Groups. The membership will be pulled in as a flat list and kept in sync with the security group membership. Having Azure subscriptions is a pre-requisite to using this tool. If you have an urgent and immediate need for the tool, please reach out to GMMSupport@service.microsoft.com for a download link. Microsoft is releasing the tool without support, other than answering questions about how we use it internally. Link to the demo video: https://aka.ms/Admin1011

    An error occurred while saving the comment
    Dros M commented  · 

    I agree, this is required. Our group memberships are already controlled locally with our HR and SIS systems. Therefore it doesn't make sense to have to then manually update groups for every group to add or remove staff or students.in our Office 365 tenant manually since we already have that automated. This could result in thousands of manual changes throughout the year not to mention significantly increasing the risk for a privacy breach if someone no longer should have access to their former groups data. This is not an efficient nor practical option.

    Dros M supported this idea  · 

Feedback and Knowledge Base