O365 Migration: OnPrem A to O365 b w/barracudanetworks
-
@dustinb3403 said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@JaredBusch OWA isn't used at all. All login to their client is through the spam filter.
Ah, while unusual, that makes it easy.
You setup a new DNS record that points to the Office's IP such as
migration.domain.comand then port forward 443 to the Exchange server.Finally go back to O365 Admin center and make a new migration. Magic will happen.
-
@jaredbusch said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@dustinb3403 said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@JaredBusch OWA isn't used at all. All login to their client is through the spam filter.
Ah, while unusual, that makes it easy.
You setup a new DNS record that points to the Office's IP such as
migration.domain.comand then port forward 443 to the Exchange server.Finally go back to O365 Admin center and make a new migration. Magic will happen.
This sounds like the way to go.
-
Will you be doing a cut over migration, hybrid, or something else?
-
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
Will you be doing a cut over migration, hybrid, or something else?
AFAIunderstand - cutover.
-
Are they dumping the Barracuda when they go to o365? I did and the spam filtering was better on the o365 side. If that's the case, just make sure you have access to their DNS to change the MX records.
-
Two domains shouldn't be an issue. If both domains are added to o365, you can powershell the addition of aliases to the users mailboxes. o365 can accept email to either domain.
