Dawn
My feedback
58 results found
-
1 vote
Dawn shared this idea ·
-
12 votes
An error occurred while saving the comment Dawn shared this idea ·
-
9 votes
Dawn supported this idea ·
-
4 votes
Dawn supported this idea ·
An error occurred while saving the comment Dawn commented
Please restore the ability to exclude specific groups from Inactivity reviews (by group names, not by purpose or security settings) to reduce the risk of them getting accidentally deleted, especially in cases where they are dependencies for business solutions. If an owner doesn't read the inactivity email correctly and confuses groups with similar names, or doesn't understand that the group is being used with a solution or something else critical, they can too easily delete it and cause breakage or data loss. This functionality was previously available but was removed during recent update to automate adding all groups to all reviews.
-
5 votes
Dawn supported this idea ·
-
2 votes
Dawn supported this idea ·
-
2 votes
Dawn supported this idea ·
-
2 votes
Dawn supported this idea ·
-
2 votes
Dawn supported this idea ·
-
4 votes
Dawn supported this idea ·
-
41 votes
An error occurred while saving the comment Dawn commented
Any updates on whether this feature will be on the roadmap in the future? This is an essential capability for governance. We'd like to know if it is planned for the future or not before expending resources to implement a custom solution.
An error occurred while saving the comment Dawn commented
Any updates on the status of this feature?
An error occurred while saving the comment Dawn commented
We are also awaiting this feature to enforce 2 Minimum Owner Policy.
Dawn supported this idea ·
-
8 votes
Dawn supported this idea ·
-
7 votes
Dawn supported this idea ·
-
6 votes
Dawn supported this idea ·
-
8 votes
An error occurred while saving the comment Dawn commented
The recipient account setting does not allow adding a group or distribution list and is limited to a single individual. We would like capability to add more than one person, or add a group or distribution list so that more than one person can get notification emails and bot posts.
Dawn supported this idea ·
-
112 votes
An error occurred while saving the comment Dawn commented
Any update on being able to customize the emails further to prevent them being reported as phishing or ignored as spam? Any possibility of sending them with a digital certificate? The customization text box is very limiting and most users don't look at it close enough or scroll enough to even see or read it, when it The teams bot is not a viable workaround for our scenario and would likely have the same issues. Once the review period passes, there is no way to generate another email or sent a user a link to review directly from an IT team member, which makes it very difficult to try to follow-up on the unanswered reviews.
An error occurred while saving the comment Dawn commented
Editing the text is definitely a priority for us as well. Secondly, we'd like to see the inactive emails show which workload the group is being used with and potentially provide a link to the team and/or the SP site. When a group has been inactive, many times the end user will not know what it is being used with or how to review it in order to make their decision.
Dawn supported this idea ·
-
17 votes
Dawn supported this idea ·
-
4 votes
Dawn shared this idea ·
-
5 votes
Dawn supported this idea ·
-
1 vote
Any plans in the roadmap for ShareGate to display/support/prevent conflict with M365 sensitivity labels versus classic AAD classification (legacy method)? M365 sensitivity labels still don't even display in the ShareGate UI for viewing. The Sharegate "sensitivity tags" are not the same thing and only exist within ShareGate and using these interferes with the native sensitivity labels which are policy driven. Similar feedback from others has been closed in error as launched due to confusion between sensitivity "tags" in sharegate and the actual m365 labels.