Hi,
We are having a technical challenge when using one of our vendor managed, custom application after logging onto Windows 10 devices which are Azure AD joined.
The application is installed on the Windows 10 client and the authentication/operations carried out on the application is through VPN to a server hosted in a server farm. The application doesn't use any type of OAuth2 processes and access is validated by sending the login information typed in the login screen through VPN.
Therefore, when I access the application it returns Error connecting (1312) which I suspect is talking about "a specified logon session doesn't exist". Technically speaking, we don't want the application to be linked to Azure AD as the app permissions are maintained in its own database in the server.
It feels like a moot point for Azure AD joined devices as I ended up setting some other laptop as Azure AD Registered which meant that I will create a local administrator account and simply register with Azure AD under Work or School options. This is not ideal because it doesn't give us complete control over organisation's devices (these Windows 10 devices are not BYOD).
Is there anyway to get around this problem without changing the application's architecture as that would mean additional cost for us for little benefit (as we don't own the application)? I am not sure if we are missing something either about this setup.
So please feel free to point me with all your suggestions/questions.
Thank you