Convert existing O365 groups from one domain to another without issues / problems

New Contributor

Hi guys,


I'm looking at converting some O365 groups which have been created with to something@domain2 without causing the end-users too much interruption or any problems with Teams sites.


The infrastructure is local AD using AAD connect to sync.


I haven't done this before and ANY information you can provide would be much appreciated - hyperlinks ETC-  just need a starting point.


I am not very experienced with Teams so I'd like to reduce t he risk for something going wrong to be as small as possible.

9 Replies

Hi @nostalgic

Considering your AAD Connect, are your Office 365 groups synced to local AD or are they cloud only? I find most Office 365 groups are cloud only even though the users are synced with AAD

If Cloud only, and assuming that the second domain is validated within the 365 tenant then the following article should work for you.

As always would recommend testing on a test group to ensure that it works before doing it on live groups.

Let me know how you get on - or if the groups are synced from local AD.

Best, Chris

@Christopher Hoard 


Thanks Chris,


The groups are synced from local AD.

Hi @nostalgic,

Just want to double check - the Office 365 groups are synced back to Local AD using the writeback feature and your organisation is in Hybrid. See article

Just want to be 100% sure before making the recommendation!

Best, Chris

@Christopher Hoard 




Hi Chris,


I have checked the AAD Connect configuration and all the " write back " features are disabled.


The AAD Connect client does have the attribute " groups " selected when running a sync my understanding is that because of this - the groups are synced to O365.


To my understand I would need to modify the attributes of the groups on local AD but I'm not sure if I can change the domain in the group properties and if that would have bad side effect on Teams.


The domain we want to change it to is verified in O365.


Looking forward to your  reply.


Are you sure we are talking about Office 365 groups here?
Hi @nostalgic

It is difficult to say without looking at this in your tenant and as Adam says there are several different types of groups - could be distribution lists syncing to your Office 365 tenant not actual Office 365 groups

A good way to check is this - can you go into the Microsoft 365 Admin Centre ( and go to Admin > Groups > Groups. Are the groups which are Office 365 groups also groups on your local AD and in an OU which is syncing via Azure AD Connect? If they are not present in any of the OU's which are syncing then this means that they were created in the 365 Tenant.

Let us know how you get on.

Best, Chris

@adam deltinger @Christopher Hoard 


Hi Adam & Chris


Thank you for pointing this out - I was confused in my first post with regards to exactly what was syncing from where.


Yep I am talking about Office 365 groups - I found a power shell command that lets me do what I need to which is


I tested changing the domain from using the PS command in the above link and it works fine and does not seem to have a negative effect on user experience at all. ( If the user is logged into the teams group and you change the domain name of the group )


I'm happy to create another post for this but I was wondering if there is a way to manage teams permissions so that only one persons has the permissions? not everyone.. had a look at this yesterday and it looks like to my understanding you need a Azure premium sub.




Hi! How do you mean “only one person has permissions” ?? I’d suggest that you create a new post and explain your issue or scenario :)

As Adam said probably better in a new post.

But making a whole load of assumptions then you can control who creates Teams by controlling who can create Office 365 groups

If you can control who can create Teams you can ensure the same owner for all Teams and therefore control the permissions on all Teams. This would, I imagine, be be the global admin/Teams Administrator who has access to the Teams Admin Centre.

Hope that helps

Best, Chris