解决.NET Core Web应用操作Azure SQL数据库时的“登录失败”问题

Hey there, let's work through this login failure issue step by step—this is super common with Azure SQL, and usually boils down to a small configuration detail you might have missed. Let's start with the most likely culprits:

1. Double-Check Azure SQL Firewall Rules #

First off, even if your admin credentials are correct, Azure SQL will block you if your IP isn't in the firewall whitelist. Here's how to fix that:

• Head to the Azure Portal, navigate to your SQL Server, then go to Firewalls and virtual networks.
  • If you're developing locally: Click "Add client IP" to add your current public IP, save changes, and wait 1-2 minutes for the rule to take effect.
  • If your app is deployed to Azure App Service: Make sure the "Allow Azure services and resources to access this server" checkbox is checked.
• Pro tip: This is the #1 cause of login failures I see—don't skip this step!

2. Verify Your Connection String (Don't Hand-Write It!) #

Never type your Azure SQL connection string manually—grab the official one from the Azure Portal to avoid typos:

• Go to your SQL Database, click Connection strings, select the ADO.NET format, and copy the full string.
• Replace the placeholders properly:
  • Critical note: The User ID must be in the format your-admin-username@your-sql-server-name (e.g., dbadmin@mysqldbserver01). A lot of people forget the @server-name suffix, which will definitely cause login failures.
  • Make sure Initial Catalog matches your database name exactly.
• Here's what a correct connection string in appsettings.json should look like:

  "ConnectionStrings": {
    "DefaultConnection": "Server=tcp:yourservername.database.windows.net,1433;Initial Catalog=YourDbName;Persist Security Info=False;User ID=youradmin@yourservername;Password=YourStrongPassword;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;"
  }
  

3. Confirm EF Core Configuration #

Make sure your DbContext is registered correctly with the right connection string:

• In .NET 6+ (Program.cs):

  builder.Services.AddDbContext<YourDbContext>(options =>
      options.UseSqlServer(builder.Configuration.GetConnectionString("DefaultConnection")));
  

• If you're using migrations, ensure you ran Add-Migration and Update-Database with the same Azure connection string (not a local SQL Server one—mixing these up is another common pitfall).

4. Test Admin Credentials Outside EF Core #

Rule out EF Core as the issue by testing your admin login directly:

• Use SQL Server Management Studio (SSMS) to connect to your Azure SQL Server with the same username and password.
  • If SSMS can't connect: The problem is with Azure SQL itself—check if the admin account is enabled, reset the password in the Azure Portal, or verify the server name is correct.
  • If SSMS connects fine: Then the issue is in your app's configuration (go back to steps 2 and 3).

5. Local Development Quirks #

If you're working locally, try these fixes:

• Use Azure Active Directory authentication instead of username/password for smoother access: Modify your connection string to use Authentication=Active Directory Integrated (this uses your Visual Studio/Azure CLI logged-in account, so make sure that account has access to the SQL DB).
• Check if a local proxy is blocking the connection—some corporate proxies interfere with Azure SQL's TCP connection on port 1433.

6. Get Detailed Error Logs #

Enable EF Core debug logging to see exactly what's going wrong:

• Add this to your Program.cs to log to the console:

  builder.Logging.AddConsole();
  builder.Logging.SetMinimumLevel(LogLevel.Debug);
  

• Run your app and look for the full error message—often it'll hint at the real issue (like IP blocked, invalid username format, etc.).

Start with steps 1 and 2 first—those are the most frequent fixes for this exact error. Let me know if any of these resolve your issue!

内容的提问来源于stack exchange，提问作者Dora Jurievna Dusyn