SDADM
My feedback
-
45 votes
An error occurred while saving the comment -
243 votes
An error occurred while saving the comment SDADM commented
Out of votes, but supporting
-
1,111 votes
An error occurred while saving the comment SDADM commented
Out of votes, but supporting
-
75 votes
An error occurred while saving the comment SDADM commented
Out of votes, but supporting
-
4,315 votes
We have heard the feedback and we’ve added it to our upcoming investments. While we do not have a date for this yet, we hope to be able to provide one soon. Thank you for the continued feedback.
SDADM supported this idea ·
-
7 votes
-
12 votes
An error occurred while saving the comment -
52 votes
SDADM supported this idea ·
-
13 votes
SDADM supported this idea ·
-
228 votes
An error occurred while saving the comment SDADM commented
Yes, and be able to set the time too, as you can in PowerShell with Set-ADAccountExpiration
SDADM supported this idea ·
-
711 votes
-
247 votes
An error occurred while saving the comment SDADM commented
Out of votes, but supporting. Especially the "Created By".
-
1,503 votes
SDADM supported this idea ·
An error occurred while saving the comment 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.
-
2,508 votes
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.
An error occurred while saving the comment SDADM commented
It's got 1300+ votes. How many more before it gets added to the roadmap?
-
121 votes
An error occurred while saving the comment SDADM commented
Agreed
-
56 votes
An error occurred while saving the comment SDADM commented
Yes
-
72 votes
SDADM shared this idea ·
-
5 votes
An error occurred while saving the comment SDADM commented
There is a weekly digest they send out
-
892 votesthinking about it ·
AdminMicrosoft 365 Groups Feedback (Product Owner, Microsoft Office 365) responded
Following up on the previous update, if a workload (such as Planner) is enabled for Outlook by default, we don’t plan on hiding those groups from the GAL. The only other scenario currently under consideration where we would hide groups by default is “Secret Groups”. “Secret Groups” would be hidden from everywhere unless you are a member. “Secret groups” is on the Microsoft 365 Groups backlog, but there is no delivery date available at this time.
An error occurred while saving the comment 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 ·
-
1,635 votestry this instead ·
AdminMicrosoft 365 Groups Feedback (Product Owner, Microsoft Office 365) responded
We’ve recently shipped the ability to change the SharePoint Site URL associated with a Microsoft 365 Group (formerly Office 365 Group). https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=56205. This can be done via the SharePoint Admin Center. The site URL can be changed on a per-site basis, but currently we don’t have plans to allow admins to change the global default from “/sites” to something different.
An error occurred while saving the comment SDADM commented
Agreed!
out of votes, but supporting