Migrating Exchange 2013 from On Premise to Azure

%3CLINGO-SUB%20id%3D%22lingo-sub-1798134%22%20slang%3D%22en-US%22%3EMigrating%20Exchange%202013%20from%20On%20Premise%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1798134%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Experts!%3C%2FP%3E%3CP%3EI%20am%20looking%20to%20migrate%20Exchange%202013%20running%20on%20Onpremise%20to%20migrate%20on%20Azure%20or%20new%20different%20datacenter.%26nbsp%3B%202%20VMs%20for%20CAS%2BMbx%20(DAG1)%2C%202%20VMs%20for%20Mbx(DAG2)%2C%202%20VMs%20for%20SMTP%2C%202%20VMs%20for%20Edge%20Transport%20running%20on%20esx%20host.%3C%2FP%3E%3CP%3EI%20will%20have%20express%20route%20VPN%20and%20requirement%20infrastructure%20deployed.%20I%20have%20below%202%20queries-%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CUL%3E%3CLI%3EOnce%20co%20existence%20configured%20and%20Exchange%202013%20Infrastructure%20running%20on%20IaaS%20promoted%20as%20Internet%20facing%20CAS%2C%20will%20there%20by%20any%20redirection%20required%20to%20legacy%20on-premise%20Exchange%202013%20infrastructure%20will%20this%20work%20smooth%20or%20any%20issues%20are%20expected%3F%3C%2FLI%3E%3CLI%3EIf%20I%20deploy%202%20Servers%20(CAS%2FMBX)%20having%20both%20the%20roles%2C%20can%20I%20use%20DAG%20for%20mailbox%20server%20high%20availability%20and%20Azure%20LB%20for%20CAS%20Load%20balancing.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EI%20know%20Exchange%20running%20on%20Azure%20IaaS%20is%20less%20recommended%20due%20to%20cost%20and%20other%20factors%20and%20O365%20is%20recommended%20solution%20but%20this%20is%20one%20of%20requirement%20hence%20please%20suggest%20if%20we%20have%20any%20other%20solution.%3C%2FP%3E%3CP%3EI%20went%20thru%20this%20article%20and%20we%20don't%20have%20hyper%20v%20as%20of%20now%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fexchange-2013-virtualization-exchange-2013-help%3Fredirectedfrom%3DMSDN%23bkmk_prereq%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fexchange-2013-virtualization-exchange-2013-help%3Fredirectedfrom%3DMSDN%23bkmk_prereq%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1798134%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hello Experts!

I am looking to migrate Exchange 2013 running on Onpremise to migrate on Azure or new different datacenter.  2 VMs for CAS+Mbx (DAG1), 2 VMs for Mbx(DAG2), 2 VMs for SMTP, 2 VMs for Edge Transport running on esx host.

I will have express route VPN and requirement infrastructure deployed. I have below 2 queries-

  • Once co existence configured and Exchange 2013 Infrastructure running on IaaS promoted as Internet facing CAS, will there by any redirection required to legacy on-premise Exchange 2013 infrastructure will this work smooth or any issues are expected?
  • If I deploy 2 Servers (CAS/MBX) having both the roles, can I use DAG for mailbox server high availability and Azure LB for CAS Load balancing.

I know Exchange running on Azure IaaS is less recommended due to cost and other factors and O365 is recommended solution but this is one of requirement hence please suggest if we have any other solution.

I went thru this article and we don't have hyper v as of now: https://docs.microsoft.com/en-us/exchange/exchange-2013-virtualization-exchange-2013-help?redirected...

 

Thank you.

0 Replies