asp.net mvc - Azure AD versus .NET Identity 2 -

what pros/cons of using .net identity 2.1 versus azure active directory (premium)?

we have mvc 5.x application using identity 2.1 registration, sign-in, password resets, etc. microsoft consultant suggesting should swap azure active directory remove complexity of "maintaining own security".

what reasons make swap , why wouldn't you?

i wouldn't 2 mutually exclusive. asp identity has functionality built in don't have use it. actually, create own userstores, managers etc. poll azure ad info. identity allows use it, override it, or skip entirely.

why wouldn't want this? not has ad. not needs it. bare-bones approach templates use application managed users , claims.

if targeting multiple applications , want sso , have ad can take advantage of it. developing own @ point redundant , more work/maintenance consultant pointed out.

you still have users table , possibly others in app database because may have business functions unrelated ad boilerplate stuff managed via ad.

another issue may run need authenticate app specific users outside ad. @ point may choose implement mixed solution. 1 half polling ad internal users, , other falling on identity external users.