Hello,
The "Create an Access Policy in Workspace ONE Access for Windows 10 Device Enrollment" described at the following URL cannot be realized.
The Office 365 IDP has configured Okta to integrate Okta and WS1 to route authentication to WS1.
Add Policy Rude
Unable to select [Windows 10 Enrollment] as Devide type in [User accessing content from] Option.
I'm not sure what the Prerequisites are, but is there anything I'm missing? I would like to be shown in diagrams and pictures.
As this functionality was announces with the June 2020 WS1 Access Cloud Release Notes: VMware Workspace ONE Access Cloud Release Notes
Windows 10 Out-of-Box Experience (OOBE) Enrollment Policy
Ability to create an enrollment access policy rule specific to Windows 10 OOBE or when joining the Azure Active Directory domain. Customers that need to ensure that only Windows 10 managed devices gain access to Office 365 can leverage this enrollment policy to separate out enrollment from post-enrollment access.
I would assume that your environment has not been updated to this latest release yet. As I am not aware of any version mapping table which explains what release VMware Workspace ONE Access™ Build 29f07739d53a1efb5deb4df38a1efc52f35f6fa3 actually is, its hard to tell.
If you find a header on your SaaS environment advertise new features, you at least be pointed to which version you are:
Would open a ticket at VMware and ask for clarification on your build and the next planned upgrade cycle.
Alex
Thank you for your reply.
I really wanted to read the release notes and realize it.
The version is match VMware Workspace ONE Access™ Build 29f07739d53a1efb5deb4df38a1efc52f35f6fa3
I'm actually configuring an Azure AD join OOBE Setting, and I want to fall down certificate authentication during enrollment.
However, I cannot do "Select Windows 10 Enrollment as the device type." I'm sorry but it is in Japanese.
I was wondering if there is a lack of prerequisites for setting.
Hi,
I think I confused you here 🙂 sorry.
The "read the release note" button on the Build 29f07739d53a1efb5deb4df38a1efc52f35f6fa3 in my case points me to this https://docs.vmware.com/en/VMware-Workspace-ONE-Access/services/rn/VMware-Workspace-ONE-Release-Note...
this is why I assume that this build is January 2020. As you have the same version as I have, you properly sit on 20.01 - what you need is 20.04 to leverage this new feature.
Hope this is more clear now.
Thank you for your reply.
We also issued a Service Request to VMware, as the new features of Workspace ONE Access and the version of the current environment are not clear.