02 - First Deploy (Dedicated)¶

Provision resources and publish your first Node.js v4 function app to an App Service (Dedicated) plan.

Prerequisites¶

You completed 01 - Run Locally.
You are signed in to Azure CLI and have Contributor access.
You already exported: $RG, $APP_NAME, $PLAN_NAME, $STORAGE_NAME, $LOCATION (use koreacentral for this guide).

What You'll Build¶

A Linux Node.js Function App on Dedicated B1 with Always On support.
A first deployment pipeline (func azure functionapp publish) and endpoint verification.
All 20 functions indexed and serving requests on Dedicated infrastructure.

Infrastructure Context

Plan: Dedicated (B1) | Network: Public | Always On: ✅

Dedicated deploys on a traditional App Service Plan. Unlike Premium, there are no pre-warmed instances or elastic scaling — you get a fixed compute allocation. Storage uses connection string authentication by default. No content file share is required (WEBSITE_RUN_FROM_PACKAGE=1).

flowchart TD
    INET[Internet] -->|HTTPS| FA[Function App\nDedicated B1\nLinux Node.js 20]

    subgraph PLAN["App Service Plan\nB1 Basic"]
        FA
        ALWAYS["Always On ✅"]
    end

    FA --> ST["Storage Account\nBlob + Queue"]
    FA --> AI[Application Insights]
    FA -.->|System-Assigned MI| ENTRA[Microsoft Entra ID]

    style FA fill:#ff8c00,color:#fff
    style PLAN fill:#E3F2FD,stroke:#1976D2
    style ST fill:#FFF3E0
    style ALWAYS fill:#FFF3E0,stroke:#FF9800

Steps¶

Set environment variables for the deployment.
```
export RG="rg-func-node-ded-demo"
export LOCATION="koreacentral"
export STORAGE_NAME="stnddedi0410"
export PLAN_NAME="plan-ndded-04100022"
export APP_NAME="func-ndded-04100022"
```
Globally unique names required

Both $APP_NAME and $STORAGE_NAME must be globally unique across all Azure subscriptions. If you get a naming conflict, append a random suffix (e.g., func-ndded-04091234).

Authenticate and set subscription context.

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

Create resource group.

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

Expected output (abridged):

{
  "name": "rg-func-node-ded-demo",
  "location": "koreacentral",
  "properties": {
    "provisioningState": "Succeeded"
  }
}

Create storage account.

az storage account create \
  --name "$STORAGE_NAME" \
  --resource-group "$RG" \
  --location "$LOCATION" \
  --sku "Standard_LRS" \
  --kind "StorageV2" \
  --allow-blob-public-access false

Expected output (abridged):

{
  "name": "stnddedi0410",
  "location": "koreacentral",
  "kind": "StorageV2",
  "provisioningState": "Succeeded"
}

Create the App Service Plan (B1, Linux).

Dedicated uses az appservice plan create

Unlike Premium which uses az functionapp plan create, Dedicated plans use az appservice plan create. This is because Dedicated plans are standard App Service Plans, not elastic function-specific plans.

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

Expected output (abridged):

{
  "name": "plan-ndded-04100022",
  "location": "koreacentral",
  "sku": {
    "name": "B1",
    "tier": "Basic"
  },
  "kind": "linux",
  "provisioningState": "Succeeded"
}

Create the Function App on the Dedicated plan.
```
az functionapp create \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --plan "$PLAN_NAME" \
  --storage-account "$STORAGE_NAME" \
  --runtime "node" \
  --runtime-version "20" \
  --functions-version "4" \
  --os-type "Linux"
```
Node.js 20 EOL approaching

Azure CLI warns: Use node version 24 as 20 will reach end-of-life on 2026-04-30. Consider using --runtime-version 22 or later for new projects.

Expected output (abridged):
```
{
  "name": "func-ndded-04100022",
  "state": "Running",
  "kind": "functionapp,linux",
  "defaultHostName": "func-ndded-04100022.azurewebsites.net"
}
```
Application Insights auto-created

az functionapp create automatically creates an Application Insights resource with the same name as the function app (e.g., func-ndded-04100022), not $APP_NAME-ai. The APPLICATIONINSIGHTS_CONNECTION_STRING app setting is auto-configured.

No content file share needed

Unlike Premium and Consumption plans, Dedicated does not require WEBSITE_CONTENTAZUREFILECONNECTIONSTRING or WEBSITE_CONTENTSHARE. Deployments use WEBSITE_RUN_FROM_PACKAGE=1 (set automatically) which stores the package in blob storage.

Set required app settings for triggers.

az functionapp config appsettings set \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --settings \
    "EventHubConnection__fullyQualifiedNamespace=placeholder.servicebus.windows.net" \
    "QueueStorage=$(az storage account show-connection-string --name $STORAGE_NAME --resource-group $RG --query connectionString --output tsv)"

EventHub placeholder required

If your app includes an Event Hub trigger, the function host may fail to start without a valid EventHubConnection setting. Set a placeholder namespace to allow function indexing.

Publish the app.

cd apps/nodejs
func azure functionapp publish "$APP_NAME"

Expected output (abridged):

Getting site publishing info...
Uploading package...
Uploading 49.36 MB [##############################################################]
Upload completed successfully.
Deployment completed successfully.

Validate deployment.

az functionapp function list \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --output table

Function indexing delay

After the first publish, it may take 30–60 seconds for all functions to appear in the ARM API. If the list is empty, wait and retry.

Expected output (abridged — showing key functions):

Name                                          Language
--------------------------------------------  ----------
func-ndded-04100022/helloHttp                 node
func-ndded-04100022/health                    node
func-ndded-04100022/info                      node
func-ndded-04100022/queueProcessor            node
func-ndded-04100022/blobProcessor             node
func-ndded-04100022/scheduledCleanup          node

Language field

The Language column shows node, not Javascript. This is the actual value returned by the ARM API for Node.js v4 apps.

Test the deployed endpoints.

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

Expected output:

{"status":"healthy","timestamp":"2026-04-09T16:05:04.222Z","version":"1.0.0"}

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

Expected output:

{"message":"Hello, Dedicated"}

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

Expected output:

{
  "name": "azure-functions-nodejs-guide",
  "version": "1.0.0",
  "node": "v20.20.0",
  "environment": "production",
  "functionApp": "func-ndded-04100022"
}

Verification¶

The output confirms that Azure indexed your function definitions and the app serves requests. Verify:

az functionapp function list shows functions with language node
curl to the health endpoint returns 200 OK with {"status":"healthy",...}
curl to /api/hello/Dedicated returns {"message":"Hello, Dedicated"}

02 - First Deploy (Dedicated)¶

Prerequisites¶

What You'll Build¶

Steps¶

Verification¶

See Also¶

Sources¶