Thank you for your post and I apologize for the delayed response!
When it comes to your BAV2ROPC sign in attempts being marked as failure, can you share where you're seeing this - are you seeing these failures within the Azure AD Sign-in logs? If so, when it comes to the sign-in attempt(s) being marked as Failure (Success, Failure, or Interrupted), this wouldn't be the same thing as Blocked since this term would relate to a Conditional Access Policies grant control. For more info - Common Conditional Access policy: Block legacy authentication.
I hope this helps!
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
- Block legacy authentication with Azure AD with Conditional Access
- Troubleshoot sign-in errors using Azure Active Directory reports
- Suspicious password spray-related IP activity
- User agent in Azure AD Sign-in logs
If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.
@Hlynur Þór Gunnarsson
I just wanted to check in and see if you had any other questions or if you were able to resolve this issue?