Domain migration question

%3CLINGO-SUB%20id%3D%22lingo-sub-2645086%22%20slang%3D%22en-US%22%3EDomain%20migration%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2645086%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-subject-wrapper%20lia-component-subject%20lia-component-message-view-widget-subject-with-options%22%3E%3CSPAN%3EDue%20to%20an%20recent%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Eacquisition%2C%20the%20company%20that%20I%20work%20for%20(Company%20A)%20needs%20to%20migrate%20another%20company's%20tenant%20(Company%20B)%20into%20ours.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-body%20lia-component-message-view-widget-body%20lia-component-body-signature-highlight-escalation%20lia-component-message-view-widget-body-signature-highlight-escalation%22%3E%3CDIV%20class%3D%22lia-message-body-content%22%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ECompany%20B%20is%20running%20Azure%20AD%20%2B%20M365%2C%20including%20several%20other%20services%20such%20as%20Azure%20DevOps.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ENow%20to%20my%20question%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ELet's%20assume%20that%20once%20we%20have%20successfully%26nbsp%3Bmigrated%20all%20data%20residing%20in%20Azure%20AD%20and%20M365%2C%20set%20up%20the%20domain%2C%20migrated%20all%20mail%2C%20aliases%20and%20set%20up%20the%20necessary%20DNS-records%20and%20such....should%20we%20be%20expecting%20any%20problems%20(such%20as%20authentication%2C%20sync%20etc)%20once%20the%20companyB-users%20will%20try%20to%20log%20into%20Azure%20DevOps%20with%20their%20old%20login%20credentials%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20so%2C%20how%20do%20we%20prevent%20this%20from%20happening%3F%20Any%20feedback%20is%20greatly%20appreciated%2C%20thanks!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2645086%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2648170%22%20slang%3D%22en-US%22%3ERe%3A%20Domain%20migration%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2648170%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F975185%22%20target%3D%22_blank%22%3E%40TH_%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CDIV%3EIf%20cx%20follows%20the%20proper%20instructions%20provided%20by%20MSFT%20he%20won't%20be%20facing%20any%20issues.%3C%2FDIV%3E%3CDIV%3EClick%20on%20the%20following%20link%3A%3CBR%20%2F%3E%3CA%20title%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Forganizations%2Faccounts%2Fchange-azure-ad-connection%3Fview%3Dazure-devops%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Forganizations%2Faccounts%2Fchange-azure-ad-connection%3Fview%3Dazure-devops%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Forganizations%2Faccounts%2Fchange-azure-ad-connection%3Fview%3Dazure-devops%3C%2FA%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EAs%20per%20this%20article%2C%20below%20are%20the%20pre-requisites%3A%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CUL%3E%3CLI%3EYou're%20in%20the%20Project%20Collection%20Administrator%20group%20for%20the%20organization.%3C%2FLI%3E%3CLI%3EYou're%20a%20member%20or%20a%20guest%20in%20the%20source%20%3CA%20href%3D%22https%3A%2F%2Fbit.ly%2F3CLWIrQ%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EAzure%20AD%3C%2FA%3E%20and%20a%20member%20in%20the%20destination%20Azure%20AD.%20For%20more%20information%2C%20see%20how%20to%3CSPAN%3E%26nbsp%3Bconvert%20an%20Azure%20AD%20guest%20into%20member.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3EYou%20have%20100%20or%20fewer%20users%20in%20your%20organization.%20If%20your%20organization%20has%20more%20than%20100%20users%2C%20contact%20support%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Efor%20help%20with%20changing%20your%20Azure%20AD.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EDo%20the%20following%20task%3A%3C%2FP%3E%3CUL%3E%3CLI%3ERequest%20that%20SSH%20keys%20be%20manually%20cleared%20by%3CSPAN%3E%26nbsp%3BSupport.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CDIV%3E%3CDIV%3EBTW%2C%20there%20are%20many%20migration%20tools%20available%20in%20VS%20Marketplace%20which%20can%20automatically%20generate%20access%20tokens%2C%20rename%2Fadjust%20the%20accounts%20with%20VS%20subscriptions%20in%20destination%20tenant.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CA%20title%3D%22https%3A%2F%2Fmarketplace.visualstudio.com%2Fitems%3Fitemname%3Dnkdagility.vsts-sync-migration%22%20href%3D%22https%3A%2F%2Fmarketplace.visualstudio.com%2Fitems%3FitemName%3Dnkdagility.vsts-sync-migration%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%22%3Ehttps%3A%2F%2Fmarketplace.visualstudio.com%2Fitems%3FitemName%3Dnkdagility.vsts-sync-migration%3C%2FA%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
New Contributor
Due to an recent acquisition, the company that I work for (Company A) needs to migrate another company's tenant (Company B) into ours.

 

Company B is running Azure AD + M365, including several other services such as Azure DevOps. 

 

Now to my question:

Let's assume that once we have successfully migrated all data residing in Azure AD and M365, set up the domain, migrated all mail, aliases and set up the necessary DNS-records and such....should we be expecting any problems (such as authentication, sync etc) once the companyB-users will try to log into Azure DevOps with their old login credentials?

 

If so, how do we prevent this from happening? Any feedback is greatly appreciated, thanks!

 

1 Reply

@TH_ 

 

If cx follows the proper instructions provided by MSFT he won't be facing any issues.
 
As per this article, below are the pre-requisites:
 
  • You're in the Project Collection Administrator group for the organization.
  • You're a member or a guest in the source Azure AD and a member in the destination Azure AD. For more information, see how to convert an Azure AD guest into member.
  • You have 100 or fewer users in your organization. If your organization has more than 100 users, contact support for help with changing your Azure AD.

Do the following task:

  • Request that SSH keys be manually cleared by Support.
 
BTW, there are many migration tools available in VS Marketplace which can automatically generate access tokens, rename/adjust the accounts with VS subscriptions in destination tenant.