Jan 22, 2019 07:29 PM|DanielAnderson|LINK
I should clarify - we also want to avoid extensive hand-written authentication code as that may be just as problematic and time consuming as upgrading from 3.5. Given that .NET 3.5 doesn't have native OWIN support, this gives me the impression that we would
either need a separate and newer application to perform the authentication using built-in libraries or we would have to effectively upgrade the applications.
Hypothetically one could create the authentication code necessary for the legacy applications to work with Azure AD directly. However, if that is the only viable option, it would be better to upgrade the applications and use existing .NET libraries to facilitate
the Azure AD authentication. We're trying to avoid both upgrading and extensive coding if at all possible, hence the question.