Abhitalks
My feedback
-
136 votes
-
61 votes
An error occurred while saving the comment Abhitalks
supported this idea
·
Abhitalks
shared this idea
·
-
82 votes
Good news!
We’re currently working on adding naming policy into Office 365 Groups.
You can follow this in our roadmap here:
https://fasttrack.microsoft.com/roadmap?filters=#I-31839An error occurred while saving the comment -
126 votes
-
223 votes
Thanks for the feedback on this item. Azure Premium currently encompasses a broad array of features that span directory management for the entire organization.
-
600 votes
Thanks for all the feedback on this item. We’ve started initial thinking and investigations on possible designs for this feature.
-
489 votes
You can now use a dot in the email alias. We are working on providing the ability to edit the email address of a group after creation.
For the ability to edit the email addresses, we now have the following roadmap item: https://products.office.com/en-US/business/office-365-roadmap?filters=&freeformsearch=27891&featureid=27891Abhitalks
supported this idea
·
-
22 votes
-
64 votes
-
3,195 votesAbhitalks
supported this idea
·
An error occurred while saving the comment Abhitalks
commented
This. Is. Really. Important.
It should be possible to federate cross-tenants as seamlessly as possible. I don't know if Azure AD B2B will help or go what distance in realizing this. But, sharing contacts is unwieldy.
-
289 votesAbhitalks
shared this idea
·
-
132 votesAbhitalks
shared this idea
·
-
35 votesAbhitalks
supported this idea
·
-
857 votes
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.
Abhitalks
shared this idea
·
-
1,475 votes
Thanks for the feedback. We are considering implementation of “Secret groups” in the near future.
Abhitalks
supported this idea
·
-
1,813 votes
Thank you for your responses. We appreciate that you’ve taken the time to provide us with feedback to help make our products better.
We’re actively working on significant improvements to the end user experience with the feature across Outlook clients. This includes improvements to the UX, the classification algorithms, and controls.
Today, admins have a Power-Shell cmdlet that allows them to control the Clutter feature on a per mailbox level. Details of this can be found here: https://technet.microsoft.com/en-us/library/mt586787%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396
Our decision to provide the cmdlet based control for Clutter was based on early feedback we received on the Clutter feature.
We will continue to improve the admin controls based on the continued feedback. Considering the responses on this forum, it would be helpful to better understand the gaps in the current admin control story. Do you believe the gap here is in not having a tenant level control or not having…
An error occurred while saving the comment Abhitalks
commented
Need ability to disable "clutter" at the tenant level for the entire organisation, including new users. We want to disable it for not only all existing users, but all possible new users as well. Clutter is causing us more problems than it purportedly intends to solve. Important mails are going into clutter and users are inconvenienced having to scan two folders and miss out many. I've hardly come across any user who says that Clutter is useful and is sorting out unimportant mails for them. Do NOT force this down our throats.
Abhitalks
supported this idea
·
-
203 votesAbhitalks
supported this idea
·
This is related: https://office365.uservoice.com/forums/286611-office-365-groups/suggestions/14479938-allow-creation-of-naming-policy-for-o365-groups