02 - First Deploy (Dedicated)¶

Provision Azure resources and deploy the Java reference application to the Dedicated (App Service Plan B1) with repeatable CLI commands.

Prerequisites¶

Tool	Version	Purpose
JDK	17+	Compile and run Java functions locally
Maven	3.6+	Build and package Java artifacts
Azure Functions Core Tools	v4	Start local host and publish artifacts
Azure CLI	2.61+	Provision Azure resources and inspect app state
Azure subscription	Active	Target for deployment

Dedicated plan basics

Dedicated (App Service Plan) runs functions on standard App Service infrastructure with predictable pricing. B1 provides 1 vCPU, 1.75 GB memory. It supports Always On, manual/auto-scale, deployment slots, and VNet integration.

What You'll Build¶

You will provision a Linux Dedicated (B1) Function App for Java, deploy with func azure functionapp publish from the Maven staging directory, and validate HTTP endpoints.

Network Scenario Choices

This tutorial deploys with public networking (B1 tier). For private networking, upgrade to Standard (S1+):

Scenario	Description	Guide
Public Only	No VNet (this tutorial, B1)	Current page
Private Egress	VNet + Storage PE (S1+ required)	Private Egress
Private Ingress	+ Site Private Endpoint (S1+ required)	Private Ingress
Fixed Outbound IP	+ NAT Gateway (S1+ required)	Fixed Outbound

Infrastructure Context

Plan: Dedicated (App Service Plan B1) | Network: Public internet + VNet integration supported | Always On: ✅ Supported

Dedicated uses standard App Service plan pricing — you pay for the plan whether or not functions are running. This provides predictable costs and supports long-running processes.

flowchart TD
    INET[Internet] -->|HTTPS| FA[Function App\nDedicated B1\nLinux Java 17]

    FA -->|connection string| ST[Storage Account]
    FA --> AI[Application Insights]

    subgraph STORAGE[Storage Services]
        ST --- QS[Queue Storage]
        ST --- BS[Blob Storage]
    end

    VNET["✅ VNet integration available\n✅ Deployment slots supported"] -. capability .- FA

    style FA fill:#0078d4,color:#fff
    style VNET fill:#E8F5E9,stroke:#4CAF50
    style STORAGE fill:#FFF3E0

flowchart TD
    A[Set variables + login] --> B[Create RG + storage]
    B --> C[Create App Service plan]
    C --> D[Create function app]
    D --> E[Set placeholder settings]
    E --> F["Build + publish from staging dir"]
    F --> G[Validate endpoints]

Steps¶

export RG="rg-func-java-ded-demo"
export APP_NAME="func-jded-$(date +%m%d%H%M)"
export STORAGE_NAME="stjded$(date +%m%d)"
export PLAN_NAME="plan-jded-$(date +%m%d)"
export LOCATION="koreacentral"

az login
az account set --subscription "<subscription-id>"

Command/Parameter	Purpose
`export RG`	Define the resource group name for logical grouping
`export APP_NAME`	Set a unique name for the function app using a timestamp
`export STORAGE_NAME`	Define a short, unique name for the storage account
`export PLAN_NAME`	Set a unique name for the Dedicated hosting plan
`export LOCATION`	Select the target Azure region (koreacentral)
`az login`	Authenticate the Azure CLI session
`az account set`	Select the target Azure subscription for deployment

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 \
  --kind StorageV2

Command/Parameter	Purpose
`az group create`	Provision a resource group to hold all related resources
`--name "$RG"`	Name of the resource group
`--location "$LOCATION"`	Target Azure region for the group
`az storage account create`	Provision an Azure Storage account for function state and logs
`--sku Standard_LRS`	Use Standard Locally Redundant Storage for cost-effectiveness
`--kind StorageV2`	Select the general-purpose v2 storage account type

Step 3 - Create App Service plan¶

az appservice plan create \
  --name "$PLAN_NAME" \
  --resource-group "$RG" \
  --location "$LOCATION" \
  --sku B1 \
  --is-linux

Command/Parameter	Purpose
`az appservice plan create`	Provision a Dedicated App Service plan
`--sku B1`	Select the Basic B1 tier (1 vCPU, 1.75 GB memory)
`--is-linux`	Create a Linux-based plan required for Java execution

Dedicated uses az appservice plan create

Unlike Premium which uses az functionapp plan create, Dedicated plans use az appservice plan create. The --sku B1 flag selects Basic tier. Other options include S1 (Standard), P1v2 (Premium v2), etc.

Step 4 - Create function app¶

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

Command/Parameter	Purpose
`az functionapp create`	Provision a serverless Linux function app on the Dedicated plan
`--plan "$PLAN_NAME"`	Associate the function app with the pre-created App Service plan
`--runtime java`	Set the serverless execution runtime to Java
`--runtime-version 17`	Specify Java 17 as the target runtime version
`--functions-version 4`	Select the v4 Functions host runtime version
`--os-type Linux`	Target Linux for Java-based serverless execution

Auto-created Application Insights

az functionapp create automatically provisions an Application Insights resource and links it to the function app. You do not need to create one manually unless you want a custom name or configuration.

Step 5 - Set placeholder trigger settings¶

STORAGE_CONN=$(az storage account show-connection-string \
  --name "$STORAGE_NAME" \
  --resource-group "$RG" \
  --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=placeholder"

Command/Parameter	Purpose
`az storage account show-connection-string`	Retrieve the connection string for the storage account
`az functionapp config appsettings set`	Update function app configuration settings
`--settings "QueueStorage=$STORAGE_CONN"`	Configure the real storage connection for the queue trigger
`--settings "EventHubConnection=..."`	Provide a placeholder for the Event Hub trigger to prevent indexing errors

Placeholder settings prevent host crashes

The Java reference app includes triggers for Queue, EventHub, Blob, and Timer. If connection settings are missing or use an invalid format, the Functions host enters an error state and cannot index any functions.

For QueueStorage: Use a real storage connection string, not a placeholder. A fake AccountKey causes 403 errors when the queue listener starts, crashing the entire host and returning 502 on all HTTP requests.

Step 6 - Create trigger resources¶

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

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

Command/Parameter	Purpose
`az storage queue create`	Create the storage queue for the queue-triggered function
`az storage container create`	Create the blob container for the blob-triggered function
`--account-name "$STORAGE_NAME"`	Target the storage account created in Step 2

Step 7 - Build and publish¶

cd apps/java
mvn clean package

Command/Parameter	Purpose
`cd apps/java`	Change directory to the Java reference application root
`mvn clean package`	Clean build and package the Maven project into a JAR

Must publish from Maven staging directory

Java function apps must be published from the Maven staging directory, NOT from the project root. The azure-functions-maven-plugin generates function.json files in target/azure-functions/<appName>/. Publishing from the project root uploads the package but functions will not be indexed (0 functions found).

cd target/azure-functions/azure-functions-java-guide
func azure functionapp publish "$APP_NAME"

Command/Parameter	Purpose
`cd target/azure-functions/...`	Change directory to the Maven-generated staging folder
`func azure functionapp publish`	Deploy the Java JAR and configuration to Azure

Expected output:

Getting site publishing info...
Uploading 326.21 KB [--------------------]
Upload completed successfully.
Deployment completed successfully.

Step 8 - Validate deployment¶

# Check app state
az functionapp show \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --query "{state:state, defaultHostName:defaultHostName, kind:kind}" \
  --output table

# List deployed functions
az functionapp function list \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --output table

# Test the health endpoint
curl --request GET "https://$APP_NAME.azurewebsites.net/api/health"

# Test the hello endpoint
curl --request GET "https://$APP_NAME.azurewebsites.net/api/hello/Dedicated"

# Test the info endpoint
curl --request GET "https://$APP_NAME.azurewebsites.net/api/info"

Command/Parameter	Purpose
`az functionapp show`	Verify that the app is in the `Running` state on the Dedicated plan
`az functionapp function list`	Verify that all expected functions are indexed
`curl --request GET`	Test the HTTP endpoints for functionality

Step 9 - Review Dedicated-specific notes¶

Dedicated uses az appservice plan create with --sku B1, not az functionapp plan create.
Always On is enabled by default on Dedicated plans — no cold starts.
Dedicated plans do NOT use Azure Files content share (unlike Premium and Consumption).
Scaling is manual or rule-based (auto-scale), not event-driven like Consumption/Premium.
Function app indexing is typically faster on Dedicated than on Premium.
Use long-form CLI flags for maintainable runbooks.

Verification¶

App state output:

State    DefaultHostName                       Kind
-------  ------------------------------------  -----------------
Running  func-jded-04100220.azurewebsites.net  functionapp,linux

Function list output (16 functions):

Name                                     Language
---------------------------------------  ----------
func-jded-04100220/blobProcessor         java
func-jded-04100220/dnsResolve            java
func-jded-04100220/eventhubLagProcessor  java
func-jded-04100220/externalDependency    java
func-jded-04100220/health                java
func-jded-04100220/helloHttp             java
func-jded-04100220/identityProbe         java
func-jded-04100220/info                  java
func-jded-04100220/logLevels             java
func-jded-04100220/queueProcessor        java
func-jded-04100220/scheduledCleanup      java
func-jded-04100220/slowResponse          java
func-jded-04100220/storageProbe          java
func-jded-04100220/testError             java
func-jded-04100220/timerLab              java
func-jded-04100220/unhandledError        java

Health endpoint response:

{"status":"healthy","timestamp":"2026-04-09T17:27:54.901Z","version":"1.0.0"}

Hello endpoint response:

{"message":"Hello, Dedicated"}

Info endpoint response:

{"name":"azure-functions-java-guide","version":"1.0.0","java":"17.0.14","os":"Linux","environment":"production","functionApp":"func-jded-04100220"}

Next Steps¶

Next: 03 - Configuration

02 - First Deploy (Dedicated)¶

Prerequisites¶

What You'll Build¶

Steps¶

Step 2 - Create resource group and storage account¶

Step 3 - Create App Service plan¶

Step 4 - Create function app¶

Step 5 - Set placeholder trigger settings¶

Step 6 - Create trigger resources¶

Step 7 - Build and publish¶

Step 8 - Validate deployment¶

Step 9 - Review Dedicated-specific notes¶

Verification¶

Next Steps¶

See Also¶

Sources¶

02 - First Deploy (Dedicated)¶

Prerequisites¶

What You'll Build¶

Steps¶

Step 1 - Set variables and sign in¶

Step 2 - Create resource group and storage account¶

Step 3 - Create App Service plan¶

Step 4 - Create function app¶

Step 5 - Set placeholder trigger settings¶

Step 6 - Create trigger resources¶

Step 7 - Build and publish¶

Step 8 - Validate deployment¶

Step 9 - Review Dedicated-specific notes¶

Verification¶

Next Steps¶

See Also¶

Sources¶