Feedback by UserVoice

SDADM

My feedback

  1. 3,570 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    146 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM supported this idea  · 
  2. 7 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 →
  3. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  4. 52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General » Users, Photos, Contacts  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM supported this idea  · 
  5. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM supported this idea  · 
  6. 192 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  General » Users, Photos, Contacts  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    Yes, and be able to set the time too, as you can in PowerShell with Set-ADAccountExpiration

    SDADM supported this idea  · 
  7. 522 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 →
  8. 127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    Out of votes, but supporting. Especially the "Created By".

  9. 1,408 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    64 comments  ·  Office 365 Admin » Apps and App Launcher  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM supported this idea  · 
    SDADM commented  · 

    Yes, yes, a thousand times YES!

    Flipping the switch to ON for some new feature (as was done for Video, O365 Groups, and more) is a bad enough idea, but those applications by default were made available to ALL users with no restrictions.

    We'd much prefer to set our own pilot teams and have them test so we understand all aspects of the new features, can set policies on usage and naming, can set roles and permissions, can prepare our help desk, can host training, etc. prior to rollout.

    I'd imagine any organization would want the same, but it's far worse when you do this to your government clients, Microsoft.

  10. 2,221 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    81 comments  ·  Office 365 Admin » SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! We’re reviewing your suggestion. Remember, the more votes a suggestion gets, the more likely it is that we’ll do it. You can see what’s happening with Office 365 on the Office 365 Roadmap.

    SDADM commented  · 

    It's got 1300+ votes. How many more before it gets added to the roadmap?

  11. 120 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Office 365 Admin » Message Center  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    Agreed

  12. 56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin » Message Center  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    Yes

  13. 63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin » Message Center  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM shared this idea  · 
  14. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin » Message Center  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    There is a weekly digest they send out

  15. 827 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    62 comments  ·  Office 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    We’ve completed work to hide groups from Outlook (GAL, left nav, and name resolution) that were created as a result of a new Team in Microsoft Teams. Additional Groups can also be hidden using the HiddenFromExchangeClientsEnabled flag. We’re now evaluating if there are additional scenarios that need to be supported.

    SDADM commented  · 

    I fully agree with the poster who said, "User created groups of any kind should not show in the GAL."

    In addition in cluttering the GAL, we recently discovered that since there are no naming controls, users can potentially create groups (public or private) that have the same name as an official mailbox (an office, department, or employee). Then they show up in the GAL because they are not hidden...

    Do you realize what a HUGE security hole it is when any internal user can create an O365 Group called "Human Resources" or make one named after [Government Agency's] director in the GAL? When other users start to pick the wrong name in the GAL and now suddenly information is being sent to the wrong recipient(s)?

    SDADM supported this idea  · 
  16. 223 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Office 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    We recently discovered that since there are no naming controls, users can potentially create groups (public or private) that have the same name as an official mailbox (an office, department, or employee). Then they show up in the GAL...

    Do you realize what a HUGE security hole it is when any internal user can create an O365 Group called "Human Resources" or make one named after [Government Agency's] director in the GAL? When other users start to pick the wrong name in the GAL and now suddenly information is being sent to the wrong recipient(s)? We need to be able to control naming.

    SDADM supported this idea  · 
  17. 1,601 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    thinking about it  ·  40 comments  ·  Office 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    Agreed!

  18. 1 vote
    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 →
    SDADM shared this idea  · 
  19. 4,668 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    197 comments  ·  Office 365 Admin » Apps and App Launcher  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    As a corollary, allow Admins to REMOVE tiles from the App-launcher for all tenant users.

    We did not have oneDrive enabled initially, as IT wanted to test it and develop policies on bit's use before rolling it out. Granting a SharePoint Online license automatically made the oneDrive tile appear. If we could have removed/concealed it until we were ready, that would probably have helped limit the number of frustrated users calling our help desk.

  20. 1,037 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    63 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    SDADM commented  · 

    Out of votes, but supporting

← Previous 1 3

Feedback and Knowledge Base