Introduction to Cloud and Azure
Azure Resource Management
Azure Data Lake Storage (ADLS)
Azure PostgreSQL Databases
Azure Container Apps
Deploying and Storing Results
Practice
Assignment
Gotchas & Pitfalls
Week 6 Lesson Plan (Teachers)
Gotchas & Pitfalls
Content coming soon...
Suggested Topics
- Forgetting firewall rules: Azure Postgres blocks all connections by default
- Using admin credentials in application code instead of least-privilege users
- Choosing the wrong region: latency and cost differences between Azure regions
- Leaving resources running: forgotten Container Apps and databases generate ongoing costs
- Connection string errors: mixing up SSL modes, ports, or database names
- ADLS naming mistakes: spaces, special characters, or inconsistent date partition formats
- ACR authentication from Container Apps: forgetting to grant the Container App's managed identity
AcrPull permissions, resulting in "image pull failed" errors
- Container App revision not updating: deploying a new image but the old revision still serves traffic; need to create a new revision or force update
- Container startup failures due to missing environment variables: container exits immediately with no obvious error
- Postgres SSL requirement: Azure Postgres enforces SSL by default; connection strings without
sslmode=require will fail
- The mental shift from local
.env file to Container Apps environment variable injection
- Forgetting to grant Key Vault access policy or RBAC role to the Managed Identity: the container starts but fails to read secrets
- Log Analytics query delay: logs can take 2-5 minutes to appear, which confuses students expecting real-time output
- Managed Identity not available locally: your local dev environment still needs connection strings or
az login token; Managed Identity only works when deployed to Azure
The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0

*https://hackyourfuture.net/*
Found a mistake or have a suggestion? Let us know in the feedback form.