Office365 Domains
-
@BRRABill said in Office365 Domains:
@JaredBusch said in Office365 Domains:
@BRRABill have you actually migrated any mail from your first service to office 365
Yes, migrated over fine.
I think at one point someone here on ML said I would have an issue fully moving over. I don't perceive one, but just wanted to be sure I wasn't missing anything.
I am assuming I can slowly migrate people over as I have done myself, and then once we are all on O365, just point our MX record there.
We migrated everybody as we wanted. We had to create 2 bridges from our Exchange server, one for each direction. Then we had to make the O365 server the master exchange server before we could migrate. Once done with all of the migrations, we shutdown the on premise exchange server and haven't turned it back on.
As far as legal stuff, I'm not understanding. Do you mean litigation hold?
-
@BRRABill Once you make the MX record change, make sure you keep MDaemon up for a bit until you're sure the MX change has propagated and MDaemon is no longer receiving traffic.
We migrated from MDaemon to Exchange Online a couple of years ago. It was a pretty smooth process -- especially using the IMAP migration for preserving mailbox contents.
-
@BRRABill said in Office365 Domains:
Question #2 is:
Does anyone have a chart of the Business Essentials plans vs the E plans?
I just want to be sure that things like legal hold and stuff are available. It's impossible to find on their site.
eDiscovery & Litigation hold is a function of the Enterprise plans.
The sight is quite simple to read. They did remove the super easy table comparison with check boxes though.
Enterprise: https://products.office.com/en-us/business/compare-more-office-365-for-business-plans
Business: https://products.office.com/en-us/compare-all-microsoft-office-products?tab=2
Exchange Online: https://products.office.com/en-us/exchange/compare-microsoft-exchange-online-plans -
As you note you can move slowly from local to Office 365. Just make sure that the attributes don't change internally otherwise any communications from internal to the users in office 365 will be having problems. Enterprise plans as noted by Jared are the ones with archiving and legalhold. you can also make the domain.com as the default login for the users, they still will get emails on the on.microsoft.com email address.
-
@JaredBusch said
The sight is quite simple to read. They did remove the super easy table comparison with check boxes though.
Me like pretty tables. Me miss table, find site hard to follow.
Me sad.
-
@BRRABill said in Office365 Domains:
@JaredBusch said
The sight is quite simple to read. They did remove the super easy table comparison with check boxes though.
Me like pretty tables.
-
@scottalanmiller said in Office365 Domains:
@BRRABill said in Office365 Domains:
@JaredBusch said
The sight is quite simple to read. They did remove the super easy table comparison with check boxes though.
Me like pretty tables.
Me agree.
-
This is also a nice little link.
https://technet.microsoft.com/en-us/library/exchange-online-service-description.aspx
-
@BRRABill said in Office365 Domains:
We have an Office365 account set up. We are either Business Essentials (for just e-mail) or Business Premium (for e-mail and apps).
The main domain is domain.onmicrosoft.com We can log into that fine.
We also have domain.com set up.
I am currently the only user on the system, but want to start adding other shortly for various reasons, and eventually want to move the whole company over for e-mail and apps.
Right now, my e-mail goes to our on-premises MDaemon server, which forwards it to [email protected]
When I decide I want to move everyone over, will there (should there) be any issues with making a total jump to Office365?
As I did something similar recently I would recommend using the hybrid mail routing. You can have mailboxes on 0365 and your premise server without having Exchange as your premise server.
Skimming through the replies I didnt see this mentioned.
-
@bigbear said
As I did something similar recently I would recommend using the hybrid mail routing. You can have mailboxes on 0365 and your premise server without having Exchange as your premise server.
Skimming through the replies I didnt see this mentioned.
Pretty sure that is how I set things up.
It's been a while, but in a nutshell that is how things work.
-
I have things set up so that even if I am using my [email protected] address to log in, it still sends from [email protected]
Is there any downside to setting things up using that onmicrosoft account? I know they are in theory the same, also just confirming this. Like if I were to set up (in the migration phase) my Outlook profile using the onmicrosoft account, will it keep just working fine after the migration is done?
I've had some issues with autodiscover, and trying to figure out the best way moving forward.
-
@BRRABill There should not be any problems besides the autodiscover.
-
Use your real domain for the log you don't use the on Microsoft otherwise everything will have to get changed or just have problems in the future
-
@JaredBusch said in Office365 Domains:
Use your real domain for the log you don't use the on Microsoft otherwise everything will have to get changed or just have problems in the future
The only issues I had was getting the iPhone to connect. But I figured out if I just put in the wrong password, I can then edit the server to the correct O365 entry.
MDaemon requires autodiscover to work at all so I have to leave it be for now.
Also had to make entries to the registry to get Outlook to work, but that seems to be working fine with the registry changes.
