Beck
My feedback
-
36 votes3 comments · Office 365 Security & Compliance » Advanced Security Management · Flag idea as inappropriate… · Admin →Beck
shared this idea
·
-
6,603 votesBeck
commented
Please add this feature natively! We had to write a powershell script and assign a license to a generic user.
-
209 votesBeck
commented
Please help Microsoft! This is still an issue a year and a half later. I still have to use a Windows 7 machine because of this and there's less than one year before Windows 7 is EOL.
Beck
shared this idea
·
-
3,488 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.
-
1,591 votesBeck
commented
What would be great would be if the SPO URL for sites created by Office 365 groups had /groups in the path instead of /sites. That would be another way to avoid this conflict. I was asked to create a /sites/marketing SPO site however I was getting an access denied message as a global admin. Turns out there was an Office 365 group created 2 months ago called Marketing and since sites created automatically for groups use the /sites URL they in essence squatted on the URL 1st. My global admin account did not have access to the group, hence the access denied message when trying to create the new site collection with the sites/marketing URL. *facepalm*
Beck
supported this idea
·
-
3,353 votes
Azure Active Directory Conditional Access has functionality for “Countries/Regions” – see https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition
Beck
commented
THIS SHOULD BE STANDARD!!! WE SHOULDN'T HAVE TO PAY EXTRA FOR AZURE AD PREMIUM TO DO THIS!!
impossible travel 2nd sign in Nigeria - OF COURSE ITS IMPOSSIBLE BECAUSE WE HAVE NO ONE THAT TRAVELS THERE!!!
-
1,329 votes
-
88 votesBeck
shared this idea
·
-
191 votesBeck
supported this idea
·
-
1,765 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…
Beck
supported this idea
·
Beck
commented
Please give us the option to disable it for our entire organization. If that cannot be allowed, please give us a way to prevent it on new users, perhaps by adding a parameter to the New-MsolUser cmdlet. Something like -ClutterEnabled that we could set to $false and when the mailbox is created, clutter would be disabled.
Please add this feature Microsoft!