Mind if I ask, what exactly is your use case for using both Office 365 / Exchange Online, AND the Email Routing, at the same time?
Such kind of set up that you describe is technically possible, but will requires some sort of fiddling.
See for example:
Each service, when configured to accept messages for @example.com
, will likely request the MX
records for the example.com
domain. Both of the above threads may provide a possible workaround for that.
The more stuff you stack on top of other stuff, the more fragile the overall setup will be, so I would normally advice against playing around with it like that.
According to your initial post, I see absolutely no reasons to stack the “Email Routing” on top of other stuff, such as e.g. Office 365 / Exchange Online.