As I’m doing the same with different ldap policies via aaa group filtering, same should work with radius policies. Another option is to bind your nps radius auth. policy with a higher priority so there are two radius policy bound to your gw. Users can login with both radius options at the same time. If first radius accepts, auth. flow ends. If first radius fails, next radius policy will hit. If more and more users migrated to Azure mfa, switch the priority so Azure mfa is your first primary radius.