Office 365 Group structure and Migration

%3CLINGO-SUB%20id%3D%22lingo-sub-1354786%22%20slang%3D%22en-US%22%3EOffice%20365%20Group%20structure%20and%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1354786%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20Readers%2C%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20employer%20gave%20me%20the%20assignment%20to%20use%20just%20Microsoft%20Teams%20within%20Office%20365.%20So%20we%20enabled%20AD%20sync%2C%20bought%20licenses%20and%20set%20up%20Teams%20%22Lite%22%20Basically%20chat%20and%20that's%20it.%26nbsp%3BThis%20means%20we%20did%20not%20migrate%20Exchange%20or%20any%20other%20service%20yet.%26nbsp%3B%20It's%20just%20for%20our%20internal%20organization%2C%20no%20guest%20or%20externals%20are%20allowed%20yet.%20From%20that%20point%20they%20want%20to%20extend%20step%20by%20step%20to%20full%20Office%20365.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20aware%20of%20Office%20365%20groups%20and%20that%20you%20can%20upgrade%20on%20prem%20hybrid%20Distribution%20Lists%20to%20Office%20365%20groups.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20we%20have%20our%20organization%20divided%20in%20teams%2C%20they%20are%20part%20of%20on%20prem%20security%20groups%20and%20on%20prem%20distribution%20groups.%26nbsp%3BCan%20anyone%20advise%20me%20into%20creating%20Office%20365%20groups%20to%20reach%20this%20goal%20without%20breaking%20exchange%2C%20teams%20and%20distribution%20lists%20after%20migrating%20everything%20to%20365.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20main%20headache%20is%20that%20when%20you%20create%20a%20team%20you%20automatically%20get%20an%20email%20with%20it.%20What%20if%20I%20create%20an%20office%20365%20team%20HR%20with%20e-mail%20%3CA%20href%3D%22mailto%3Ahr%40comapny%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehr%40domainname.tld%26nbsp%3B%3C%2FA%3E%26nbsp%3Band%20then%20migrate%20exchange%20to%20365%20with%20team%20HR%20it's%20DL%20with%20e-mail%26nbsp%3B%3CA%20href%3D%22mailto%3Ahr%40domainname.tld%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehr%40domainname.tld%3C%2FA%3E%3C%2FP%3E%3CP%3EHow%20can%20I%20avoid%20conflicts%20and%20seamlessly%20merge%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1354786%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1395080%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Group%20structure%20and%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1395080%22%20slang%3D%22en-US%22%3Eone%20option%20is%20to%20enable%20automatic%20naming%20conventions%20so%20that%20when%20people%20create%20Teams%2C%20it%20appends%20%22Teams_%22%20to%20the%20front%20of%20whatever%20name%20they%20use%2C%20so%20that%20it%20could%20not%20conflict%20with%20the%20groups%20on-premises.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fusers-groups-roles%2Fgroups-naming-policy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fusers-groups-roles%2Fgroups-naming-policy%3C%2FA%3E%3CBR%20%2F%3EAnother%20option%20is%20to%20restrict%20Teams%20creation%20to%20only%20Exchange%20admins%20who%20can%20verify%20that%20the%20group%20gets%20created%20without%20conflicting%20with%20a%20group%20on-premises.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fadmin%2Fcreate-groups%2Fmanage-creation-of-groups%3Fview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fadmin%2Fcreate-groups%2Fmanage-creation-of-groups%3Fview%3Do365-worldwide%3C%2FA%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Dear Readers,  

My employer gave me the assignment to use just Microsoft Teams within Office 365. So we enabled AD sync, bought licenses and set up Teams "Lite" Basically chat and that's it. This means we did not migrate Exchange or any other service yet.  It's just for our internal organization, no guest or externals are allowed yet. From that point they want to extend step by step to full Office 365. 

 

I am aware of Office 365 groups and that you can upgrade on prem hybrid Distribution Lists to Office 365 groups.  

 

Currently we have our organization divided in teams, they are part of on prem security groups and on prem distribution groups. Can anyone advise me into creating Office 365 groups to reach this goal without breaking exchange, teams and distribution lists after migrating everything to 365. 

 

My main headache is that when you create a team you automatically get an email with it. What if I create an office 365 team HR with e-mail hr@domainname.tld  and then migrate exchange to 365 with team HR it's DL with e-mail hr@domainname.tld

How can I avoid conflicts and seamlessly merge them.

 

 

 

 

 

 

 

 

1 Reply
Highlighted
one option is to enable automatic naming conventions so that when people create Teams, it appends "Teams_" to the front of whatever name they use, so that it could not conflict with the groups on-premises.
https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-naming-policy
Another option is to restrict Teams creation to only Exchange admins who can verify that the group gets created without conflicting with a group on-premises.
https://docs.microsoft.com/en-us/microsoft-365/admin/create-groups/manage-creation-of-groups?view=o3...