Update App Service Plan SKU from F1 to S3 to match live infrastructure

[Copilot]

This PR resolves an Infrastructure as Code (IaC) discrepancy where the Bicep template was out of sync with the live Azure infrastructure.

Problem

The Azure App Service Plan for contoso-chat-net was scaled up from S2 to S3 on 2025-08-15T19:17:39Z, but the main.bicep file still specified the SKU as 'F1' (Free tier). This mismatch would cause future deployments to revert the App Service Plan back to the Free tier instead of maintaining the current Standard S3 configuration.

Solution

Updated the App Service Plan resource in main.bicep to reflect the current live infrastructure:

resource appServicePlan 'Microsoft.Web/serverfarms@2022-03-01' = {
  name: appServicePlanName
  location: location
  sku: {
    name: 'S3'        // Changed from 'F1'
    tier: 'Standard'  // Changed from 'Free'
  }
  kind: 'app'
}

Changes

• Updated SKU name from 'F1' to 'S3'
• Updated SKU tier from 'Free' to 'Standard'
• Validated Bicep syntax compiles successfully
• Generated ARM template correctly reflects the S3 Standard configuration

This ensures future Bicep deployments will maintain consistency with the current Azure infrastructure state.

Fixes #89.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: bicep build main.bicep (dns block)
  • Triggering command: bicep build main.bicep --stdout (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.