Why Application settings and connection strings in Azure? - Purpose & Use Cases

The Big Idea

What if changing a secret in your app was as easy as flipping a switch, without touching your code?

The Scenario

Imagine you have a web app that needs to connect to a database and other services. You write the connection details directly in your code files. Later, you want to change the database or update a password. You have to open the code, find every place with those details, and change them manually.

The Problem

This manual way is slow and risky. If you miss one spot, your app breaks. Sharing code with secrets inside is unsafe. Also, every time you deploy, you risk overwriting or exposing sensitive info. It's like writing your house keys on every door instead of keeping them in one safe place.

The Solution

Using application settings and connection strings in Azure lets you store these details securely outside your code. You can update them anytime in one place without touching your app code. Azure manages the secrets safely and injects them when your app runs, making updates fast and secure.

Before vs After

✗ Before

string dbPassword = "mypassword123";
string dbConnection = "Server=myserver;Database=mydb;User Id=myuser;Password=mypassword123;";

✓ After

var dbConnection = Environment.GetEnvironmentVariable("DB_CONNECTION_STRING");

What It Enables

You can change your app's settings anytime without redeploying code, keeping secrets safe and your app running smoothly.

Real Life Example

A company updates its database password every month for security. With Azure application settings, they just update the password in one place, and all app instances use the new password instantly without downtime.

Key Takeaways

Hardcoding settings is risky and hard to maintain.

Azure application settings keep secrets safe and separate from code.

Updating settings is quick, secure, and does not require code changes.

Practice

1. What is the main purpose of using Application settings in an Azure App Service?

easy

A. To store configuration values separately from the app code

B. To write application code directly in the Azure portal

C. To deploy the app to multiple regions automatically

D. To monitor app performance metrics

Solution

1. Step 1: Understand what application settings are

   Application settings hold configuration values like API keys or feature flags outside the app code.

2. Step 2: Identify the benefit of separation

   Separating settings allows changing them without redeploying or modifying the app code.

3. Final Answer:

   To store configuration values separately from the app code -> Option A

4. Quick Check:

   Application settings separate config from code [OK]

Hint: Settings keep config outside code for easy updates [OK]

Common Mistakes:

• Confusing settings with code deployment
• Thinking settings are for monitoring
• Assuming settings are for writing code

2. Which Azure CLI command correctly sets an application setting named MySetting with value Value123 for an App Service named MyApp?

easy

A. az webapp config appsettings set --name MyApp --resource-group MyGroup --settings MySetting=Value123

B. az webapp create appsettings add --name MyApp --settings MySetting=Value123

C. az appservice config set --app MyApp --setting MySetting=Value123

D. az webapp config connection-string set --name MyApp --settings MySetting=Value123

Solution

1. Step 1: Identify the correct Azure CLI command for app settings

   The command to set app settings is az webapp config appsettings set with parameters for app name, resource group, and settings.

2. Step 2: Check the syntax for setting a key-value pair

   The settings parameter uses key=value format, here MySetting=Value123.

3. Final Answer:

   az webapp config appsettings set --name MyApp --resource-group MyGroup --settings MySetting=Value123 -> Option A

4. Quick Check:

   Use az webapp config appsettings set with key=value [OK]

Hint: Use 'az webapp config appsettings set' with key=value [OK]

Common Mistakes:

• Using wrong command verbs like create or add
• Confusing app settings with connection strings
• Missing resource group parameter

3. Given this Azure CLI command output after setting a connection string:

{"id": "/subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Web/sites/MyApp/config/connectionstrings", "name": "MyApp", "connectionStrings": [{"name": "DbConn", "connectionString": "Server=myserver;Database=mydb;", "type": "SQLAzure"}]}

What will the app receive when accessing the connection string DbConn?

medium

A. An empty string because connection strings are not set this way

B. An error because the connection string type is missing

C. The string 'Server=myserver;Database=mydb;' as the connection string value

D. The connection string encrypted and unreadable

Solution

1. Step 1: Understand the connection string format in Azure

   The output shows a connection string named 'DbConn' with a valid connection string value and type 'SQLAzure'.

2. Step 2: Determine what the app receives

   The app reads the connection string value as plain text 'Server=myserver;Database=mydb;' to connect to the database.

3. Final Answer:

   The string 'Server=myserver;Database=mydb;' as the connection string value -> Option C

4. Quick Check:

   Connection strings provide plain text values to apps [OK]

Hint: Connection strings deliver plain text values to apps [OK]

Common Mistakes:

• Assuming connection strings are encrypted automatically
• Thinking type field is mandatory for usage
• Believing connection strings are empty if not set in code

4. You run this Azure CLI command to update an app setting:
az webapp config appsettings set --name MyApp --resource-group MyGroup --settings MySetting
But it fails with an error. What is the likely cause?

medium

A. The resource group name is incorrect

B. The setting value is missing after the key 'MySetting'

C. The app name 'MyApp' does not exist

D. The command should use 'appsettings add' instead of 'set'

Solution

1. Step 1: Check the command syntax for setting app settings

   The --settings parameter requires key=value pairs, but only 'MySetting' (key) is provided without a value.

2. Step 2: Identify the error cause

   Missing value after the key causes the command to fail due to invalid syntax.

3. Final Answer:

   The setting value is missing after the key 'MySetting' -> Option B

4. Quick Check:

   App settings need key=value pairs [OK]

Hint: Always provide key=value pairs for app settings [OK]

Common Mistakes:

• Omitting the value after the key
• Assuming 'set' is wrong command
• Ignoring error messages about syntax

5. You want to securely update a database connection string in your Azure App Service without restarting the app. Which approach is best?

hard

A. Edit the connection string directly in the app code and redeploy

B. Set the connection string as an environment variable in your local machine

C. Store the connection string in a public GitHub repo and pull it at runtime

D. Use Azure CLI to update the connection string via az webapp config connection-string set and enable slot settings

Solution

1. Step 1: Understand secure connection string management

   Updating connection strings via Azure CLI keeps secrets out of code and allows live updates.

2. Step 2: Use slot settings to avoid app restarts

   Enabling slot settings for connection strings prevents app restarts and keeps settings sticky to deployment slots.

3. Final Answer:

   Use Azure CLI to update the connection string via az webapp config connection-string set and enable slot settings -> Option D

4. Quick Check:

   Use CLI and slot settings for secure live updates [OK]

Hint: Update connection strings via CLI with slot settings [OK]

Common Mistakes:

• Changing connection strings in code causing redeploy
• Exposing secrets in public repos
• Setting local env vars which don't affect Azure app