Zed

Thanks Akito, Powershell is disabled as per your screenshot but when configuring MEM settings it is a required field to select the ACC to use, even though it does let you continue. I think Omnissa need to make that as optional in the MEM settings to make it crystal clear.

As organisations migrate to Entra ID and no longer rely on connectors e.g. ACC. How do we manage and secure Exchange Online? as Powershell config (in UEM) requires an ACC. Granted this goes into Exchange / Email and the second part is do MS have an equivalent Email Management option / security best practice?

Thanks guys, much appreciated.

I have confirmed, the client uses Identity Engine (not Classic) and it seems we need to do it both ways, do you agree? Thanks!

Integrating Okta with Workspace One (WS1). I know I need to add Okta as an Idp in WS1. Do I need to also add (which is causing confusion as which is then the Idp) WS1 as an Idp INSIDE Okta? To achieve SSO, Trust and unified apps etc. Thanks in advance! https://help.okta.com/en-us/content/topics/device-trust/saml/mobile/enforce-device-trust-mobile-sso-with-okta-vmware-ws1.htm