Forum Discussion
Office 365 Hybrid Migration iPhone Native Mail Stopped Working
Unit2777 so mail routing is not relevant to the profile config, MX just says where to send the mail, your exchange server then forwards onto Exchange online. What matters is where the users mailbox is hosted, so Maas support were correct - the profile needs to point at where the mailbox resides, so once they are in O365 it should be there. This is where the mobile mail client needs to connect to in order to download the mail.
I expect you need a new profile for migrated users, and then change the profile when they get migrated. I know it can be done because I have seen this working (although I don't know Maas technically) but I do know the migrate can be done without setting up the phones again. But you could set up a new Maas email profile pointing to outlook.office365.com and just see if you can get that working. Then as you migrate users, switch the profile.
Another idea is to get rid of Maas you migrate and use Intune instead.
Unit2777 are you changing user UPNs when migrating them? We found that Maas profiles would break if you do that.
Have you tried removing and adding the Mass profile on affected phones, does that resolve the issue?
Thanks
Their UPNs have remained the same during the migration.
I spoke to MaaS support and they suggested a new policy and to change the ActiveSync settings from mail.domain.com to outlook.office365.com.
I mentioned that the mail hostname would be the same as we are routing all traffic through the on-prem server however they wouldn't budge until I tested this.
Unfortunately, it didn't seem to help the issue.I haven't tried removing the profile and re-adding yet as this would take a long time to apply to each migrated user, and ideally would like it to be a policy change.
Knowing MaaS though, it won't be so easy 😞
Unit2777 so mail routing is not relevant to the profile config, MX just says where to send the mail, your exchange server then forwards onto Exchange online. What matters is where the users mailbox is hosted, so Maas support were correct - the profile needs to point at where the mailbox resides, so once they are in O365 it should be there. This is where the mobile mail client needs to connect to in order to download the mail.
I expect you need a new profile for migrated users, and then change the profile when they get migrated. I know it can be done because I have seen this working (although I don't know Maas technically) but I do know the migrate can be done without setting up the phones again. But you could set up a new Maas email profile pointing to outlook.office365.com and just see if you can get that working. Then as you migrate users, switch the profile.
Another idea is to get rid of Maas you migrate and use Intune instead.
- It was like you mentioned, where the mailbox is hosted not mailflow.
We created a new policy with outlook.office365.com and the other relevant details, then applied it.
Weirdly, it half applied over the top of the previous policy.
The server hostname had updated to Office365, however the domain was still the previous one and not domain.com.
We figured out a workaround to this which was to apply a policy that didn't have EAS setup, which removed the email profile.
After which, we assigned the updated Office 365 profile and it deployed properly.
