Feedback by UserVoice

Jeremy

My feedback

  1. 9,379 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    543 comments  ·  General » Uncertain topic  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy supported this idea  · 
  2. 727 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    53 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy supported this idea  · 
  3. 1,857 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    65 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy supported this idea  · 
  4. 4,156 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    192 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks to everyone for your feedback and votes on this item. We’re working through a couple of options and hope to have more information shortly. It’s a very difficult problem to solve since group membership is consumed across many different aspects of Microsoft 365. Thanks for your patience and keep the feedback coming!

    Jeremy supported this idea  · 
    An error occurred while saving the comment
    Jeremy commented  · 

    TELL US MORE:

    Say you have 4 O365 groups: support_1@, support_2@, support_3@, and support@

    support@ contains support_1
    support_1 contains support_2
    support_2 contains support_3

    Each support_$ contains users at that support level. So emailing support_2 will email support_2 and support_3, but will not email support_1. The users in support_1 will not receive the email, nor will they be able to access it. If someone emails support, they will email the entire support team.

    Likewise, Support is also a SharePoint site. It has 3 subfolders within, which are named support_1, support_2, and support_3.

    The O365 group support_3 has contribute access to all 3 subfolders. support_2 has contribute to support_2 and support_1, but has read-only to the support_3 folder. Thus support_1 has contribute to support_1 folder, is able to read support_2, but does not have access to the support_3 folder.

    Likewise, support@ has a dedicated support mailbox "company_support@". The only visible O365 group who has access to it is support_1, but because of the nesting support_2 and support_3 also have access to it. support_2 also has a mailbox they manage: "critical_support@" which both support_2 and support_3 have access to because of the nesting, but support_1 will not. Finally support_3 has a little shared mailbox named "escalations_support" which neither support_2 nor support_1 have access to.

    escalations_support is also able to email the "sysadmins" hidden and restricted mailbox (or O365 group) - likewise, support_3 is able to email this hidden restricted mailbox/O365 group. This way, support_2 and support_1 essentially must email support_3 before escalating the issue further.

    As you can see, this allows for better communication and escalation support within a company. The above was just a random example I made, but I know I for one use nested groups to help with SharePoint and shared mailbox inheritances. Without it, I have a lot of redundant work to do. Hopefully, this will give you insight of the /why/ it's needed, as well as the /what/ we mean.

  5. 1,469 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    123 comments  ·  Office 365 Admin » Apps and App Launcher  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeremy commented  · 
    An error occurred while saving the comment
    Jeremy commented  · 

    I personally have been using Microsoft To-Do for the past month. It's not quite the same and indeed needs a bit more involvement, but it's a nice alternative. If you flag something for "Follow up" in outlook, it will appear in the "To-Do" list in tasks. Then move/copy that to the folder in Tasks "Tasks - your.email@company.com" and it'll generate a copy of the email thread for comments/notes and place it into the To-Do app.

    Right now my only complaint is that flagged items don't show up in Tasks and only in To-Do (which is kinda backwards), but if I take an extra second to move it it seems to work okay. I'm sure there's a Macro way to move things as well.

    Just sorta annoying it took 2 years to get to this point, but alas - at least we're close.

  6. 1,193 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    131 comments  ·  Office 365 Admin » Message Center  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy supported this idea  · 

Feedback and Knowledge Base