Hi @joelp,
When you have only AAD authentication enabled in your server, first it checks the user is used to authenticate is AAD user or not and Authentication types is AAD authentication or not. If it is not, then it will throw the 18456 (authentication failure error).
Authentication Flow in Azure SQL When Only AAD authentication is enabled
- Authentication Attempt: When a client tries to connect, Azure SQL first checks authentication Type and User. The user is used to authenticate is AAD user or not and Authentication types is AAD authentication or not
- Firewall Validation: If authentication fails, the process stops. However, if Everything is correct then only Azure SQL evaluate firewall rules and networking restrictions.
Why You See Error 18456 Instead of a Network Error?
- As per you have shared the logs image, The brute force attack is trying different Users which are not looking as AAD users for an existing database.
- Since the authentication process runs first, Azure SQL returns error 18456 (Login Failed) before it even checks firewall rules.
- If the authentication had passed, but the firewall blocked the connection, you would see a different error like:
- A network-related or instance-specific error occurred.