Forum Discussion
Manage automatic creation of direct reports group
THANK YOU all for your feedback, please see an update in this new thread: https://techcommunity.microsoft.com/t5/Office-365-Groups/Update-Auto-creation-of-Direct-Reports-group-in-Outlook-MC96611/m-p/55318#M2740
Can someone please explain what will happen for a automated group where the manager leave the company, also whant will happen when a replacement of the manager is assigned with the direct reports.
Thanks in advance.
- cfiessinger
Microsoft
The content stays behind, the replacement will have access to all the content https://support.office.com/en-us/article/Assign-a-new-owner-to-an-orphaned-group-86bb3db6-8857-45d1-95c8-f6d540e45732
Carlos Gomez wrote:Can someone please explain what will happen for a automated group where the manager leave the company, also whant will happen when a replacement of the manager is assigned with the direct reports.
Thanks in advance.
It's answered earlier in the thread, but the thread is getting long and fragmented.
Basically, it will be a manual process (rename/re-assign existing group, or create new group and move members to new group), from what I've understood of the replies from Microsoft so far.
Thanks Paul Cunningham,
I'll take a note on this, but would be nice if Microsoft updates their documentation to add this case scenario at least for the ones that do not read this thread.
Regards.
- David Rosenthal
Had a good discussion with cfiessinger and BenSchorr on documentation on Twitter, if you can call 140 characters a discussion. They clarified a lot for me, and made some updates to the documentation already as a result of our conversation. Give it a look: https://support.office.com/en-us/article/Manage-automatic-creation-of-direct-reports-group-Admin-help-8387f129-19cc-4426-9911-e36fa0a01043?ui=en-US&rs=en-US&ad=US
- David Rosenthal
Unrelated to the main topic, but equally important to many of us. jeffmedford the way replies and threading work in here is making very active posts like this very difficult to follow. I'm left scrolling through the entire thing to find the new replies, and other than the time they were posted it is very hard to pick them out from the crowd. Maybe a known thing you're working on, but wanted to give the feedback and a real life example.
This is a very good question Carlos Gomez I would also like to know the answer... cfiessinger can you help here?
Yikes what a nightmare:
Beginning in April 2017, managers who have 2-20 direct reports, do not already have a direct reports group, and have permissions to create groups in Outlook, will automatically have a private group created for them with their direct reports. The manager will be added as an owner, and the direct reports of the manager will be added as members by default. The group will be named "<Manager's Name>'s direct reports", but that can be edited.
And also all the governance with quitting, new members etc. If there's one roll out which should have been opt-in, it's this one. Are Microsoft trying to bump adoption numbers somehow with this plethora of auto creation of groups? I know we will inform our customers about this and make sure they do the needed Posh.
- I respect what Microsoft is doing here with trying to drive adoption of Groups. I think direct reports is a great use case for Groups, so I get the idea behind it.
I have issues with how it is being implemented though, mainly the non dynamic nature. I've read the reasonings for it in this thread, but remain unconvinced. IT at most organizations already have enough things to maintain; now you're asking them to maintain group memberships or to teach end users to do it themselves.
Here's my main piece though; all of us on here stay updated with these changes. We will turn this on or off as needed. In reality, most admins never read their message center messages and won't see this. Instead, it will roll out for them next month, there will be a crazy period where they try to disable it while end users are confused. No one looks good in this scenario; not the IT team, not Microsoft, and certainly not Groups. Let's not tarnish the name of Groups this way.
We've been told many times (see almost every Ignite slide deck) that Microsoft will listen to our feedback. Well please listen now; hold this change back, at least for now. Not for the people on this thread, but for the ones who won't see this until it's too late.I agree with many points mentioned in this thread. From the engagement in this thread, I believe that it is very clear that Microsoft a struck a nerve here with the community, possibly mostly admins and respective community managers in their organizations.
I hope they deduct that this feature is not release ready in its current state. When you start to auto populate stuff it gets very tricky, as there is not a "one size fits all" approach for every organization out there, therefore additional customization options are necessary for this work, which simply do not exist yet.
The current documentation and comment like "you can change the displayname later" are just highlighting the stuff that DOES work, but do not the stuff does still NOT work since the very inception of Office 365 Groups, like changing URLs, alias, ... the devil's always in the details ;)
