1# Azure Functions Deployment
2 
3Deployment workflows for Azure Functions using AZD.
4 
5## Prerequisites
6 
7- Azure Functions project prepared with azd template
8- `azure.yaml` exists and validated
9- `.azure/deployment-plan.md` status = `Validated`
10- Azure Functions Core Tools (optional, for local debugging or when using `func` commands outside azd workflows)
11 
12## AZD Deployment
13 
14### Full Deployment (Infrastructure + Code)
15 
16```bash
17# Deploy everything
18azd up --no-prompt
19```
20 
21### Infrastructure Only
22 
23```bash
24# Provision infrastructure without deploying code
25azd provision --no-prompt
26```
27 
28### Application Only
29 
30```bash
31# Deploy code to existing infrastructure
32azd deploy --no-prompt
33```
34 
35### Preview Changes
36 
37```bash
38# Preview changes before deployment
39azd provision --preview
40```
41 
42## Environment Configuration
43 
44### Set AZD Environment Variables
45 
46These are for azd provisioning, not application runtime:
47 
48```bash
49azd env set AZURE_LOCATION eastus2
50azd env set VNET_ENABLED false
51```
52 
53> ⚠️ **Important**: `azd env set` sets variables for the azd provisioning process, NOT application environment variables.
54 
55## Verify Deployment
56 
57### Check Function App Status
58 
59```bash
60# Show deployment details
61azd show
62```
63 
64## Testing HTTP Endpoints
65 
66> ⚠️ **Never use `curl -I` (HEAD) to test Azure Functions endpoints.**
67>
68> Azure Functions `[HttpTrigger]` with `"get"` does **not** automatically handle HEAD requests. HEAD returns 404 from the routing layer even when GET works correctly, causing false-negative results and misdirected debugging.
69 
70### ✅ DO — Use GET with output suppression
71 
72```bash
73# Check status code only (GET, don't follow redirects)
74curl -s -o /dev/null -w "%{http_code}" "https://<func-name>.azurewebsites.net/api/<route>"
75 
76# Get status code and redirect URL
77curl -s -o /dev/null -w "Status: %{http_code}\nRedirect: %{redirect_url}" "https://<func-name>.azurewebsites.net/api/<route>"
78 
79# Verbose output showing response headers (GET)
80curl -sS -D - -o /dev/null "https://<func-name>.azurewebsites.net/api/<route>"
81```
82 
83### ❌ DON'T — Use HEAD requests
84 
85```bash
86# DO NOT use this — returns 404 even when the function works
87curl -I "https://<func-name>.azurewebsites.net/api/<route>"
88```
89 
90## Monitoring
91 
92Monitor your Functions deployment through Azure Portal or use azd to view deployment status.
93 
94### Common Issues
95 
961. **Deployment timeout**: Use `azd up` with appropriate timeout settings
972. **Missing dependencies**: Ensure package.json/requirements.txt is correct and committed
983. **Function not appearing**: Check azure.yaml service configuration
994. **Cold start issues**: Consider Premium plan configuration in Bicep templates
100 
101## CI/CD Integration
102 
103For automated deployments with azd, see [cicd/README.md](../cicd/README.md) for GitHub Actions and Azure DevOps integration.
104 
105## Data Loss Warning
106 
107> ⚠️ **CRITICAL: `azd down` Data Loss Warning**
108>
109> `azd down` **permanently deletes ALL resources** in the environment, including:
110> - **Function Apps** with all configuration and deployment slots
111> - **Storage accounts** with all blobs and files
112> - **Key Vault** with all secrets (use `--purge` to bypass soft-delete)
113> - **Databases** with all data (Cosmos DB, SQL, etc.)
114>
115> **Best practices:**
116> - Always use `azd provision --preview` before `azd up`
117> - Use separate environments for dev/staging/production
118> - Back up important data before running `azd down`
119 
120## Next Steps
121 
122After deployment:
1231. Verify functions are running
1242. Test endpoints
1253. Monitor Application Insights
1264. Set up alerts and monitoring
127