🌱 PoC Azure FrontDoor

PoC to secure Azure Function behind an Azure FrontDoor, gaining load balancing, DSA and WAF capabilities.

TL/DR

Concept

Expose azure apps and functions through a secure FrontDoor instead of direct access (which is insecure) or API Gateway setup (which is a bit more complex, but combining both is a common approach).

Client  Azure FrontDoor  Azure Functions

[File: b5315926-c0ec-43c0-aa3c-99e4eaab82f1]

Deployment

Create a resource group and deploy the template:

az group create --name poc-frontdoor --location "East US"

az deployment group create \
    --resource-group poc-frontdoor \
    --template-file poc.bicep \
    --parameters appName=poc

All parameters are optional:

All other resources are deployed using a auto-generated string or its own name, eg:

resource frontDoorOriginGroup 'Microsoft.Cdn/profiles/originGroups'
  name: 'frontDoorOriginGroupName'

resource hostingPlan 'Microsoft.Web/serverfarms'
  name: 'hpe${uniqueString(resourceGroup().id)}'

Testing

Clean Up

Delete the entire resource group to prevent waste:

az group delete --name poc-frontdoor

Next

Resources


🌱 Seedlings são ideias que recém tive e precisam de cultivo, não foram revisadas ou refinadas. O que é isso?