SEG Server and On-Premise Exchange moving to Exchange Online

[mdasmall]

What are the best options for still controlling email access and restricting it to only enrolled devices when moving away from Exchange On-Premise to Exchange Online when a SEG server is currently being used to perform this function?

In other words, I need to retain the ability to only allow AirWatch enrolled devices access to corporate email but I do not want to have all the devices contact an on-premise SEG server just to forward to the cloud and Exchange Online. It seems to defeat the purpose of migrating to Exchange Online.

We need the SEG server presently to prevent unenrolled personal devices from gaining access to company email.

What is the best way to continue to have this type of control or conditional access when making this transition?

Thank you in advance.

[EMMJunkie]

Where is your UEM (AirWatch) Server located - SaaS/On-premise?

[mdasmall]

We use SaaS Airwatch with on-prem SEG

[EMMJunkie]

You can make use of the Powershell option for Mobile Email Management. There are some usage differences between SEG & Powershell, so I would make sure you understand those.

PowerShell Integrated Deployment Overview

[mdasmall]

Do they offer a SaaS SEG?

[EMMJunkie]

No SaaS SEG, Powershell is the SaaS version, tied into the Workspace ONE UEM Console.

[mdasmall]

I’ll have to read up on this as it is totally new/different from SEG.

Thanks!

[UiliamFoschiera]

Hi all,

Although VMware support recommends (?) not using SEG for Office365 (saying that in the cloud there are compensatory controls for email), in our company we created a new SEG specifically for connections to accounts migrated to Office365. Thus, we maintained the controls that the WS1 SEG offers.

Hope this helps.

Regards

Uiliam Mello