Ability to manage Exchange Online without the requirement to have Exchange on-premise
If a company has users on-premise in AD but mailboxes in Exchange Online, the requirement to keep an Exchange server on-premises to manage Exchange related objects should be done away with. This keeps complexity in the email environment, requires on-premise system resources to support, requires SSL renewal (if hybrid relationship is enabled) and is another point of failure.
We would like to see a way to manage the Exchange Online environment without their being a necessity to maintain the on-prem Exchange server.
Clay Hampton commented
I have done serval migrations and having to tell the end-user "oh by the way you need to keep Exchange on-premise for Dirsync" is stupid and should not have to happen. So I have to keep creating new servers to do nothing in their environments, but keep us compliant with Microsoft.
Patrick Gorden commented
What happened to that 'tool we're developing' to get rid of this. There's been no update to the status of that since 2017, and when we call for support from microsoft, the support reps DON'T KNOW about the requirement. It seems that it only is a requirement for those who read tech net articles.
Please Please Please remove this requirement.
I agree 100%! Hybrid is a stop gap and should be treated as such, no one starts a hybrid setup with the plan that they would like to keep all of the old servers around forever. Im finding posts back to 2014 where people are asking to turn off their exchange servers. If your hybrid setup is connected through on premise AD (Non-exchange) servers then what is the hold up? I can make a user in AD, then make them a mailbox in office 365 and I can manage them in office 365 no problem, but if they used to be on exchange then too bad for me? even if I had to manually "Convert" my users to act like the new accounts do, that would be acceptable and probably not that hard for Microsoft to program in.