Forum Discussion
Modern external network migration, how to sign into new tenant with admin account.
Hi there
I'll try and explain this as best I can, I'm getting confused about what to do myself now!!! we managed to get an extension from MS to migrate a Yammer external network site to Viva until 31st August.
I am following this guide https://learn.microsoft.com/en-us/viva/engage/configure-your-viva-engage-network/modern-external-networks
I have used my global admin account e.g. myadmin@existing_tenant.onmicrosoft.com from my current tenant to create a new entra work_force tenant (aaa_vivaengage.onmicrosoft.com) so far so good.
I can't seem to figure out how to sign into the NEW TENANTs viva engage page with my admin account to generate the association token, I need to use myadmin@existing_tenant.onmicrosoft.com on engage.cloud.microsoft according to the instructions, when I try and do that I am taken to the engage management interface for my existing tenant and all its current content not the new one I've created (aaa_vivaengage.onmicrosoft.com).
Essentially, how do I do this bit:
- As the Viva Engage Global Administrator, go to engage.cloud.microsoft and sign into Viva Engage on the new Microsoft Entra tenant.
I can't see a way of switching engage tenants once signed in or beforehand.
I am able to create a new global admin account in the new entra tenant and sign into the associated new engage tenant with that but I can't generate the association token using that account and pair the parent and new tenants as the token needs to be created using the admin account that created the new tenant in the first place (myadmin@existing_tenant.onmicrosoft.com). If I try doing that I get an invalid token error when trying to redeem the code in the parent tenant.
Any suggestions much appreciated.
Ok, so it turns out the Viva engage implementation of the parent tenant is in a different geographical location to the one I chose when creating the new tenant.
The confusing thing is that if I go to "365 Admin > Settings > Org Settings > Organization Profile > Data location" it tells me all my services are located the UK, yet Microsoft themselves (there is no way for a customer to check) have checked an tell me my Viva data is homed in the US. I can migrate Viva to the UK but all my Viva data and communities are lost and I have to start from scratch. To me this is a massive oversight especially with GDPR etc. and UK public organisation needing to keep data within the EU.
4 Replies
Also the best way I found to sign into the new tenant was to make sure the global admin that gets created in the new tenant is added as a 'member' rather than guest, reset their password.
Go to engage.cloud.microsoft and sign in with first.last_homedomain_#email address removed for privacy reasons using the password you set above.
Dont forget before this you'll need to add an E5 license to the new tenant and assign it to the above account. I found it easiest to create a new global admin to add an E5 trial license to carry this out.
Another observation is that the token code that gets generated doesn't change no matter who generates it, it seems to be unique to the new tenant rather than the user that generates it so needing to use the initially added account in the new tenant I think is incorrect.
This just seems like a mess to be frank, I'm now into the licensing battle of needing to know if someone from another tenant with an E3 license that is added to the new tenant as a guest needs a licenses in that tenant as well to access Viva.
Ok, so it turns out the Viva engage implementation of the parent tenant is in a different geographical location to the one I chose when creating the new tenant.
The confusing thing is that if I go to "365 Admin > Settings > Org Settings > Organization Profile > Data location" it tells me all my services are located the UK, yet Microsoft themselves (there is no way for a customer to check) have checked an tell me my Viva data is homed in the US. I can migrate Viva to the UK but all my Viva data and communities are lost and I have to start from scratch. To me this is a massive oversight especially with GDPR etc. and UK public organisation needing to keep data within the EU.
I'm in the exact same boat! I setup my external tenant a couple of days ago and still can't login to get the code. Following this thread to see if anyone has found a solution
The actual error trying to redeem the token is - Invalid code, please enter a correct code to redeem an external network
