Using the AirWatch Provisioning Adapter with Windows 10 AAD Join

Using the AirWatch Provisioning Adapter with Windows 10 AAD Join

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

 

https://TheIdentityGuy.ca

 

 

Comments

Is this a limitation of UEM that it will not map to user if the ImmutableID is base64 encoded (vZ/lGAC9bUWiA7Egpw5fqg==)? Will it be updated in the future to be more flexible to also take valies like "vZ/lGAC9bUWiA7Egpw5fqg=="

What if all my O365 Immutable ID's are stored as vZ/lGAC9bUWiA7Egpw5fqg== and I am using Okta SCIM provisioning without AD? The ImmutableID's were originally generated via AD to O365.

Also, it looks like Okta only stores the base64 encoded value. For example if you map appuser.externalId to an Okta variable, the value is base64 encoded and which result in the following from your table

vZ/lGAC9bUWiA7Egpw5fqg==vZ/lGAC9bUWiA7Egpw5fqg==NO

Version history
Revision #:
2 of 2
Last update:
‎06-15-2021 07:36 AM
Updated by:
 
Contributors