[pbedat]

Wait until you have to deal with the admin web apps.

To enable mail forwarding to another domain I had to install powershell and a plugin to install a plugin to allow forwarding in my org.

Then there are times when it says : „To change this setting please enable the legacy UI“

And everything of this convoluted UX hell is documented in a dizzying but highly accurate documentation. I have to give them that!

Switched to protonmail and not looking back.

[firexcy]

Since you mentioned this could you please give some hints on how to enable external forwarding at all? Spent hours on the issue last month before finally giving up deciphering the maze of the legacy UI. Thanks in advance.

[pbedat]

I also lost many hours and nerves until I figured it out. But it let me get a glimpse on the true and frightening nature of Microsoft.

Okay so step 1: you try to enable forwarding, but the UI gives you an error about some policy that has to be set

https://docs.microsoft.com/en-us/exchange/recipients-in-exch...

Step 2: you have to find the anti spam settings in a UI called „defender something“ and turn the automatic forwarding polic on.

https://docs.microsoft.com/en-us/microsoft-365/security/offi...

Again the UI doesn‘t allow this because some setting in your organisation is disabled.

Step 3: the hard part. This setting can only be disabled through powershell. Google the name of it and you will find some docs about it.

There might be other ways to achieve forwarding. At least it sounds like that in the docs, but then they must be buried deep below the legacy UIs.

Good luck!