I don't believe the AzureAD is supposed to show from the Z-Icon as a logon option because for Azure, ZCM verifies who is actually logged into Windows versus sending a UID/PWD to Azure...Similar to how we do Kerberos but not quite the same.  Try logging out of Windows and logging into Windows directly as your Azure User, which is likely different than your AD User (Even if the CN of the name matches, the account itself is likely not the same account under the hood.)

Hi Craig,

I have the device azure ad joined and logged in with the Azure Ad account. But the Microfocus popup window for Login never comes up like in the documentation shown.

Did you create a Service Request?  I thought I saw one come in......I can try and follow add any input I may have.

Unfortunately, as its a new feature I have limited troubleshooting experience.

Case number 02657684

Have anyone tested this in the meantime?

Does anyone know th exe of the alternative login windows?

Is it an additioal client o install?

Nothing is in the docu.

There is no additional EXE to login.  In fact, the concept of "LOGIN" does not really even exist.  What happens look at who is we check your OS Login details and consume that.  We do not do any additional authentication.  Similar to "KERBEROS" Only setup where there is no additional login dialogues.

We have many AD user sources also in the zone. Maybe this is a problem. I cant see the windows like in the docu shown.

I see the ZAPP windows and the login option. And there I see all other user sources, but not the Azure AD.

There will never be a "LOGIN" option to "AZURE" from ZAPP like other user sources.  It will consume an existing Windows Azure Connection similar to but not exactly like how Kerberos Works.

Hi Craig,

the only thing I want to have is to see witch user is logged in to the workstation and vice versa. But nothing happened.

If we can pull from the local event logs, there is some audit info that may help.  Otherwise, the MS way is from the Azure side of things