02 - First Deploy (Premium)¶

Deploy your .NET 8 isolated worker app to the Premium (EP1) plan with long-form Azure CLI commands and validate your first production endpoint.

Prerequisites¶

Tool	Version	Purpose
.NET SDK	8.0 (LTS)	Build and run isolated worker functions
Azure Functions Core Tools	v4	Start local host and publish artifacts
Azure CLI	2.61+	Provision Azure resources and inspect app state

Premium plan basics

Premium (EP1) keeps at least one warm instance, supports VNet integration, private endpoints, and deployment slots. No cold-start penalty, with up to 100 instances and no execution timeout.

What You'll Build¶

A Linux Premium Function App running the .NET 8 isolated worker on an EP1 plan, deployed from your local project with Core Tools, then validated through all HTTP endpoints.

flowchart TD
    A[az functionapp plan create EP1] --> B[az functionapp create]
    B --> C[dotnet publish]
    C --> D[func azure functionapp publish]
    D --> E[16 functions indexed]
    E --> F[HTTP endpoint validation]

Steps¶

Step 1 - Set deployment variables¶

export RG="rg-func-dotnet-prem-demo"
export LOCATION="koreacentral"
export STORAGE_NAME="stdnetprem0410"
export PLAN_NAME="plan-dnetprem-04100301"
export APP_NAME="func-dnetprem-04100301"

Step 2 - Create resource group and storage account¶

az group create \
  --name "$RG" \
  --location "$LOCATION"

az storage account create \
  --name "$STORAGE_NAME" \
  --resource-group "$RG" \
  --location "$LOCATION" \
  --sku Standard_LRS

Step 3 - Create the Premium plan¶

az functionapp plan create \
  --name "$PLAN_NAME" \
  --resource-group "$RG" \
  --location "$LOCATION" \
  --sku EP1 \
  --is-linux true

Premium plan vs Consumption

Unlike Consumption, Premium requires a dedicated plan resource. The az functionapp plan create command creates an Elastic Premium plan with always-warm instances.

Step 4 - Create the function app on the Premium plan¶

az functionapp create \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --storage-account "$STORAGE_NAME" \
  --plan "$PLAN_NAME" \
  --runtime dotnet-isolated \
  --runtime-version 8 \
  --functions-version 4 \
  --os-type Linux

Step 5 - Create trigger resources¶

az storage queue create \
  --name "incoming-orders" \
  --account-name "$STORAGE_NAME"

az storage container create \
  --name "uploads" \
  --account-name "$STORAGE_NAME"

Step 6 - Configure app settings¶

STORAGE_CONN=$(az storage account show-connection-string \
  --name "$STORAGE_NAME" \
  --resource-group "$RG" \
  --query connectionString \
  --output tsv)

az functionapp config appsettings set \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --settings \
    "QueueStorage=$STORAGE_CONN" \
    "EventHubConnection=Endpoint=sb://placeholder.servicebus.windows.net/;SharedAccessKeyName=placeholder;SharedAccessKey=cGxhY2Vob2xkZXI=;EntityPath=events"

Step 7 - Build and publish¶

cd apps/dotnet
dotnet publish --configuration Release --output ./publish

cd publish
func azure functionapp publish "$APP_NAME" --dotnet-isolated

Must pass --dotnet-isolated flag

When publishing from the compiled output directory, Core Tools cannot detect the project language. Always pass --dotnet-isolated to specify the worker runtime explicitly.

Step 8 - Verify function list¶

az functionapp function list \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --query "[].{name:name, language:language}" \
  --output table

Expected output (16 functions):

Name                                          Language
--------------------------------------------  ---------------
func-dnetprem-04100301/blobProcessor          dotnet-isolated
func-dnetprem-04100301/dnsResolve             dotnet-isolated
func-dnetprem-04100301/eventhubLagProcessor   dotnet-isolated
func-dnetprem-04100301/externalDependency     dotnet-isolated
func-dnetprem-04100301/health                 dotnet-isolated
func-dnetprem-04100301/helloHttp              dotnet-isolated
func-dnetprem-04100301/identityProbe          dotnet-isolated
func-dnetprem-04100301/info                   dotnet-isolated
func-dnetprem-04100301/logLevels              dotnet-isolated
func-dnetprem-04100301/queueProcessor         dotnet-isolated
func-dnetprem-04100301/scheduledCleanup       dotnet-isolated
func-dnetprem-04100301/slowResponse           dotnet-isolated
func-dnetprem-04100301/storageProbe           dotnet-isolated
func-dnetprem-04100301/testError              dotnet-isolated
func-dnetprem-04100301/timerLab               dotnet-isolated
func-dnetprem-04100301/unhandledError         dotnet-isolated

Premium function indexing delay

On Premium plans, az functionapp function list may return 0 functions for several minutes after the first publish. The functions are available via HTTP immediately — the indexing metadata takes longer to propagate. If you see an empty list, wait 2-3 minutes and retry.

Step 9 - Test HTTP endpoints¶

curl --request GET "https://$APP_NAME.azurewebsites.net/api/health"
curl --request GET "https://$APP_NAME.azurewebsites.net/api/hello/Premium"
curl --request GET "https://$APP_NAME.azurewebsites.net/api/info"

Verification¶

Uploading 6.82 MB [-----------------------------------------------------------]
Upload completed successfully.
Deployment completed successfully.
Syncing triggers...

App state:

State    DefaultHostName                             Kind
-------  ------------------------------------------  -----------------
Running  func-dnetprem-04100301.azurewebsites.net    functionapp,linux

Health endpoint response:

{"status":"healthy","timestamp":"2026-04-09T18:25:15.779Z","version":"1.0.0"}

Hello endpoint response:

{"message":"Hello, Premium"}

.NET upload size

The .NET isolated worker publish output is approximately 6.82 MB, larger than Java (~326 KB) because it includes the ASP.NET Core runtime dependencies.

Next Steps¶

Next: 03 - Configuration