Add App Service IaC template with Linux and Windows variants

[Copilot]

This PR adds a new Infrastructure as Code (IaC) template for deploying Azure App Service using Azure Verified Modules (AVM). The template provides a simpler alternative to the existing App Service Environment (ASE) template for scenarios that don't require advanced networking and isolation features.

New Template Features

The new appservice/ directory contains a complete template suite with two variants:

Linux App Service (Default)

• Runtime: Node.js 18 LTS on Linux containers
• Files: main.bicep + appservice.bicep
• App Service Plan: Linux B1 SKU for cost-effective hosting

Windows App Service

• Runtime: .NET 8.0 on Windows
• Files: main-windows.bicep + appservice-windows.bicep
• App Service Plan: Windows B1 SKU

Both variants include:

• HTTPS-only configuration
• System-assigned managed identity
• Ready-to-deploy templates with minimal configuration
• Cost-effective B1 tier suitable for development and demo scenarios

Template Structure

Following the established repository patterns:

appservice/
├── main.bicep                    # Linux variant entry point
├── appservice.bicep             # Linux App Service resources
├── main-windows.bicep           # Windows variant entry point
├── appservice-windows.bicep     # Windows App Service resources
├── README.md                    # Comprehensive documentation
└── .cheatsheet                  # Quick deployment commands

Use Cases

This template is ideal for:

• Simple web application hosting
• Development and testing environments
• Proof of concepts and learning scenarios
• Cost-effective application deployment

For production workloads requiring network isolation and advanced features, users should continue using the existing ASE template.

Deployment

Both templates deploy at subscription level and create their own resource groups:

# Linux (Node.js)
az deployment sub create --location swedencentral --template-file main.bicep

# Windows (.NET)
az deployment sub create --location swedencentral --template-file main-windows.bicep

The templates use the latest stable versions of Azure Verified Modules and follow all established naming and tagging conventions from other templates in the repository.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

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

• aka.ms
  • Triggering command: bicep build ase.bicep --stdout (dns block)
  • Triggering command: bicep lint main.bicep (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)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.