connection string updates

Author: alexwolfmsft

articles/app-service/tutorial-dotnetcore-sqldb-app.md

@@ -174,7 +174,7 @@ To see the entirety of the command output, drop the `--query` in the command.
 
 ## 5 - Generate the Database Schema
 
-To generate our database schema, set up a firewall rule on the SQL database server. This rule lets your local computer connect to Azure.
+To generate our database schema, set up a firewall rule on the SQL database server. This rule lets your local computer connect to Azure. For this step, you'll need to know your local computer's IP address. For more information about how to find the IP address, see here.
 
 ### [Azure portal](#tab/azure-portal)
 
@@ -195,6 +195,15 @@ az sql server firewall-rule create --resource-group msdocs-core-sql --server <yo
 
 ---
 
+Next, update the name of the connection string in appsettings.json file to match the `AZURE_SQL_CONNECTION` name generated by the service connector. When the app is deployed to Azure, the `LocalDb` connection string value will be overridden by the connection string stored in Azure.
+
+```json
+"ConnectionStrings": {
+    // This local connection will be overridden with an Azure connection string after deployment
+    "AZURE_SQL_CONNECTION": "Server=(localdb)\\mssqllocaldb;Trusted_Connection=True;MultipleActiveResultSets=true"
+  }
+```
+
 From a local terminal, run the following commands to install the necessary CLI tools for Entity Framework Core, create an initial database migration file, and apply those changes to update the database. Make sure to pass in the connection string you copied from the Azure SQL database for the `connection` parameter, which will override the `localdb` connection string in the `appsettings.json` file.
 
 ```dotnetcli