Platform¶

The Platform section helps you make design-time decisions for Azure Functions: runtime architecture, hosting plan, scaling model, network boundaries, reliability controls, and security posture.

Use this section before implementation to choose the right operating model for your workload.

What this section covers¶

flowchart TD
    A[Hosting]
    A --> B[Scaling]
    B --> C[Triggers and Bindings]
    C --> D[Networking]
    D --> E[Security]

• Architecture — host/worker runtime model, deployment unit, and resource relationships.
• Hosting — Consumption, Flex Consumption, Premium, and Dedicated plan behavior.
• Triggers and bindings — eventing patterns and integration contracts.
• Scaling — how scale decisions differ by trigger type and hosting plan.
• Networking — VNet integration, private endpoints, and hybrid connectivity.
• Reliability — retries, poison message handling, and high-availability choices.
• Security — auth models, managed identity, and network isolation.

Start with the design sequence¶

1. Pick a hosting plan from Hosting.
2. Validate scale behavior in Scaling.
3. Design private/public paths in Networking.
4. Add failure handling from Reliability.
5. Lock down access using Security.

Platform principles¶

• Platform = design decisions (not deployment runbooks).
• Language-agnostic guidance for Python, Node.js, .NET, and Java.
• Microsoft Learn aligned values, limits, and capabilities.
• Plan-aware architecture: capabilities are not identical across plans.

See Also¶

• Start Here: Hosting Options
• Operations: Deployment
• Operations: Monitoring
• Troubleshooting: Index