Awesome

App Service Landing Zone Accelerator

This repository provides both enterprise architecture guidelines and a reference implementation for deploying Azure App Service solutions in multi-tenant and App Service Environment scenarios. It includes best practices, considerations, and deployable artifacts for implementing a common reference architecture.

Table of Contents

• App Service Landing Zone Accelerator
  • Table of Contents
  • Enterprise-Scale Architecture
  • Prerequisites
  • Getting Started
    • Step 1. Reference implementations
    • Step 2. Configure and test the deployment in your own environment
      • Deploy with Azure Portal (Bicep/ARM)
      • Locally deploy with Bicep
    • Step 3. Configure GitHub Actions
    • App Patterns
  • Got a feedback
  • Data Collection
    • Telemetry Configuration
  • Contributing
  • Trademarks

Visit EnterpriseScale-AppService for more information.

Enterprise-Scale Architecture

The enterprise architecture is broken down into six different design areas, where you can find the links to each at:

Prerequisites

Before you begin, ensure you have met the following requirements:

• Azure Subscription: You need an Azure subscription to create resources in Azure. If you don't have one, you can create a free account.

• Azure CLI or Azure PowerShell: You need either Azure CLI or Azure PowerShell installed and configured to interact with your Azure account. You can download them from here and here respectively.

• Terraform or Bicep: Depending on your preference, you need either Terraform or Bicep installed to deploy the infrastructure. You can download Terraform from here and Bicep from here.

• Knowledge of Azure App Service: This project involves deploying and managing Azure App Service resources. Familiarity with Azure App Service and its concepts is recommended.

Please replace the links and the software versions with the ones that are relevant to your project.

Getting Started

Follow the steps below to get started with the App Service Landing Zone Accelerator.

Step 1. Reference implementations

In this project, we currently have the following reference implementations:

Scenario	Description	Documentation	Pipeline Status
:arrow_forward: Scenario 1: App Service Secure Baseline Multi-Tenant	This scenario deploys a multi-tenant App Service environment with a Hub and Spoke network topology.	README

Note
Currently, the App Service Secure Baseline Multi-Tenant is the only reference implementation available. However, both the Terraform and Bicep configuration files have feature flags available to accommodate additional scenarios. More reference input files will be provided to accommodate additional reference implementations in the future.

Step 2. Configure and test the deployment in your own environment

With the selected reference implementation, you can now choose between Bicep or Terraform to deploy the scenario's infrastructure.

Deploy with Azure Portal (Bicep/ARM)

Locally deploy with Bicep

For additional information, view the Bicep README here.

The Bicep configuration files are located in the scenarios/secure-baseline-multitenant/bicep directory.

Before deploying the Bicep IaC artifacts, you need to review and customize the values of the parameters in the main.parameters.jsonc file.

Note
Azure Developer CLI (azd) is also supported as a deployment method. Since azd CLI does not support parameter files with jsonc extension, we provide a simple json parameter file (which does not contain inline comments)

The expandable table below summarizes the available parameters and the possible values that can be set.

Step 3. Configure GitHub Actions

Note
The GitHub Actions pipelines are currently configured to deploy the Terraform hub and spoke deployments. The Bicep pipelines are currently in development.

GitHub Actions pipelines are located in the .github/workflows directory with templates stored in the .github/actions directory.i

1. Create an Microsoft Entra ID Service Principal for OIDC Authentication
   • Reference the following documentation to configure your Microsoft Entra ID Service Principal: OIDC authentication to Azure.
2. Configure your GitHub Actions Secrets
   • In your forked repository, navigate to Settings > Secrets and variables > Actions.
   • Create the following secrets:

     Secret Name	Description	Example Value
     AZURE_CLIENT_ID	GUID value for the Client ID of the service principal to authenticate with	00000000-0000-0000-0000-000000000000
     AZURE_SUBSCRIPTION_ID	GUID value for the Subscription ID to deploy resources to	00000000-0000-0000-0000-000000000000
     AZURE_TENANT_ID	GUID value for the Tenant ID of the service principal to authenticate with	00000000-0000-0000-0000-000000000000
     AZURE_TF_STATE_RESOURCE_GROUP_NAME	[Optional] For Terraform only: override value to configure the remote state resource group name	rg-terraform-state
     AZURE_TF_STATE_STORAGE_ACCOUNT_NAME	[Optional] For Terraform only: override value to configure the remote state storage account name	tfstate
     AZURE_TF_STATE_STORAGE_CONTAINER_NAME	[Optional] For Terraform only: override value to configure the remote state storage container name	tfstate
     ACCOUNT_NAME	[Optional] The Azure DevOps organization URL or GitHub Actions account name (see Example Value column) to use when provisioning the pipeline agent on the self-hosted DevOps Agent VM	https://dev.azure.com/ORGNAME OR github.com/ORGUSERNAME OR none
     PAT	[Optional] Personal Access Token for the DevOps VM to leverage on provisioning the pipeline agent on the self-hosted DevOps Agent VM	asdf1234567

App Patterns

Looking for developer-focused reference implementation? Check out Reliable Web Patterns for App Service.

:arrow_forward: Reliable web app pattern for .NET

Got a feedback

Please leverage issues if you have any feedback or request on how we can improve on this repository.

Data Collection

The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of Microsoft's privacy statement. Our privacy statement is located at https://go.microsoft.com/fwlink/?LinkId=521839. You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices.

Telemetry Configuration

Telemetry collection is on by default.

To opt-out, set the variable enableTelemetry to false in Bicep/ARM file and disable_terraform_partner_id to false on Terraform files.

Contributing

See more at Contributing

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.

Any use of third-party trademarks or logos are subject to those third-party's policies.