Skip to content

Roadmap

The Azure Functions Python Cookbook is a mission-driven project aimed at providing the most comprehensive, production-ready, and well-tested collection of patterns for Azure Functions development with Python. This roadmap outlines the direction of the project and its current status as we move toward a complete and rich resource for the community.

Current Status

The project has successfully reached its initial milestone with the release of v0.1.0 on 2026-03-08. We have established the repository structure, defined the core development standards, and created placeholders for our first set of recipes. The foundation is now in place for building out high-quality content.

Phase 1: Foundation (COMPLETE)

The primary goal of this phase was to build the infrastructure required to support a long-term, high-quality documentation project.

  • Repository structure and organization established using modern Python standards.
  • Continuous Integration (CI/CD) and GitHub workflows for automated testing, linting, and security.
  • Documentation site architecture using MkDocs Material theme for a modern, searchable experience.
  • Recipe template and formal contract definition to ensure all recipes are consistent and complete.
  • Initial set of 5 recipe placeholders defined to guide immediate content creation efforts.
  • Internationalization support with translated READMEs for Korean, Japanese, and Chinese audiences.
  • Development tooling integration (Ruff, Black, Mypy, Pytest, Bandit, Hatch).
  • Automated badge synchronization across all translated README files.
  • Pre-commit hooks for code quality, formatting, and type checking.

Phase 2: Recipe Content (IN PROGRESS)

This phase focuses on transforming the placeholders into fully-fleshed, production-ready recipes that users can depend on.

  • Write comprehensive content for the first 5 core recipes (HTTP Basic, OpenAPI, Webhook, Queue, Timer).
  • Develop fully runnable example projects for each recipe that can be deployed directly to Azure.
  • Include deep-dive production notes covering performance, scaling, and cost optimization.
  • Create architectural diagrams and flowcharts for each pattern to aid visual understanding.
  • Ensure all example code passes 100% of the repository's security and quality checks.
  • Gather initial community feedback on the recipe format and content depth.
  • Add detailed setup instructions for each example project.
  • Provide guidance on integrating these recipes into existing Azure Functions apps.

Phase 3: Discovery (PLANNED)

Once the core content is established, we will focus on making that content easier to find, navigate, and use in complex projects.

  • Implement a robust recipe search and tagging system (e.g., search by trigger, service, or pattern).
  • Develop a richer gallery or landing experience to showcase featured and trending recipes.
  • Create cross-referencing with official Azure scaffold templates and other community resources.
  • Add advanced recipes covering integrations with services like Cosmos DB, Event Hubs, and Service Bus.
  • Implement a "copy to clipboard" feature for code snippets to streamline developer workflows.
  • Integrate with community tools for recipe browsing and sharing.
  • Support deep linking to specific sections of recipes for easier sharing.

Phase 4: Integration (FUTURE)

The final phase aims to integrate the cookbook more deeply into the developer's toolchain and provide even higher levels of automation.

  • Explore deeper scaffold integration where users can generate a project directly from a recipe.
  • Build automated example validation that ensures all samples stay up-to-date with the latest SDK releases.
  • Provide recipe metadata in a machine-readable format for consumption by other developer tools.
  • Explore the possibility of a lightweight CLI for browsing and scaffolding recipes from the terminal.
  • Support community-driven recipe submissions through a formal contribution and review process.
  • Automate the testing of infrastructure-as-code templates associated with recipes.
  • Provide one-click deployment options for all example projects.

Non-Goals

To maintain focus and ensure high quality, we have explicitly defined what this project is not:

  • Not a CLI: In the first release, we are prioritizing content quality over building a new command-line interface.
  • No Deep Automation Initially: We prefer clear, manual steps that teach users how things work before we automate them.
  • Quality Over Quantity: We will not add a large number of low-quality or undocumented samples just to increase the count.
  • Not a Replacement for Official Docs: This cookbook complements the official Microsoft documentation by providing opinionated, production-ready patterns.
  • No Legacy Support: We exclusively focus on the Python v2 programming model and Python 3.10+.
  • No Large Numbers of Low-Quality Samples: We focus on high-impact, well-documented patterns rather than an exhaustive list of every possible variation.

How We Prioritize

We prioritize recipes and features based on the following criteria: 1. Community demand and common pain points reported by developers. 2. Stability and longevity of the underlying Azure services and Python SDKs. 3. Potential for improving the overall security and performance of Azure Functions. 4. Completeness of the existing collection to ensure we cover the most important use cases.

The roadmap is a living document and will be updated as the project evolves and we receive more feedback from the community. We are committed to making this the best resource for Python developers on Azure.