Feedback by UserVoice

prossum

My feedback

  1. 607 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    31 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    prossum supported this idea  · 
  2. 701 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    prossum supported this idea  · 
  3. 13,743 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    519 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    prossum supported this idea  · 
  4. 4,621 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    126 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    Hi, As announced at Ignite Sep 2020, we will be making this functionality available as an open source tool by the end of the year. It can be used to pull in 1 or more security groups (nested or not) to drive the membership of a M365 Group. The membership will be pulled in as a flat list and kept in sync with the security group membership. However, if you have a pressing need for it before then, please reach out to GMMSupport@service.microsoft.com for a download of the tool. There is no support provided for the tool from Microsoft, other than answering any question around how we use it here. Link to the tool demo at Ignite: Making IT more efficient with improvements to Microsoft 365 Groups – https://aka.ms/Admin1011

    prossum supported this idea  · 
  5. 51 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    prossum supported this idea  · 
  6. 70 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    prossum supported this idea  · 
  7. 12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    prossum supported this idea  · 
  8. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    prossum supported this idea  · 
  9. 242 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    prossum supported this idea  · 
  10. 4,290 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    193 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    Hi, As announced at Ignite Sep 2020, we will be making this functionality available as an open source tool by the end of the year. It can be used to pull in 1 or more security groups (nested or not) to drive the membership of a M365 Group. The membership will be pulled in as a flat list and kept in sync with the security group membership. However, if you have a pressing need for it before then, please reach out to GMMSupport@service.microsoft.com for a download of the tool. There is no support provided for the tool from Microsoft, other than answering any question around how we use it here. Link to the tool demo at Ignite: Making IT more efficient with improvements to Microsoft 365 Groups – https://aka.ms/Admin1011

    prossum supported this idea  · 
  11. 442 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Office 365 Admin » SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →
    prossum supported this idea  · 
  12. 17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    prossum commented  · 

    Agree to use AIP labels for DLP, but it's not a good idea to synchronise AIP labels and O365 labels as I saw at a recent Ignite session. Protection and Retention must be kept separated. Sure, some relation (optional) should be there, but no integration.

  13. 109 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    prossum commented  · 

    I do not agree with this.
    At a recent Ignite session about AIP I saw that Microsoft intents to synchronise the O365 labels and the AIP labels. That is a mistake! Do not do that!
    Why? O365 labels should be used for retention policies only. The option to use O365 labels in DLP is a wrong step, instead you should use AIP labels in DLP and leave O365 labels for retention purposes only.
    So, my advise: use AIP and DLP for protection and use O365 labels for Retention. Sure there can be a relation to each other if you like, but do not integrate!

  14. 120 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    prossum supported this idea  · 

Feedback and Knowledge Base