技能 azure-functions
☁️

azure-functions

安全

Master Azure Functions Development

Building serverless solutions on Azure often means grappling with cold starts and orchestration complexity. This skill delivers proven patterns for the isolated worker model, Durable Functions, and performance tuning.

支持: Claude Codex Code(CC)
📊 71 充足
1

下载技能 ZIP

2

在 Claude 中上传

前往 设置 → 功能 → 技能 → 上传技能

3

开启并开始使用

测试它

正在使用“azure-functions”。 Request guidance on Azure Functions connection management

预期结果:

Recommended approach: Use IHttpClientFactory for HTTP connections. This provides connection pooling, DNS refresh, and prevents socket exhaustion. Never instantiate HttpClient directly in function code.

正在使用“azure-functions”。 Ask about Durable Functions pattern for fan-out processing

预期结果:

Use the Fan-out/Fan-in pattern: The orchestrator calls multiple activity functions in parallel using Task.WhenAll, then aggregates results. Ideal for batch processing, data aggregation, or parallel API calls.

正在使用“azure-functions”。 Need help with Python Azure Functions v2 model

预期结果:

The v2 model uses decorators like @app.function_name and @app.route. Key benefits: IntelliSense support, simplified binding syntax, and unified programming model. Import azure.functions module and define routes with HTTP methods.

安全审计

安全
v1 • 2/24/2026

Static analyzer flagged two false positives for weak cryptographic algorithms at lines 3 and 46. Manual review confirms these are documentation strings with no actual cryptographic code. The SKILL.md file contains only descriptive content about Azure Functions patterns - no executable code, network calls, file operations, or external commands. Safe for publication.

1
已扫描文件
47
分析行数
0
发现项
1
审计总数
未发现安全问题
审计者: claude

质量评分

38
架构
100
可维护性
87
内容
32
社区
100
安全
91
规范符合性

你能构建什么

Build Event-Driven Serverless APIs

Create scalable HTTP-triggered functions with proper connection pooling and async patterns for production workloads.

Implement Complex Workflow Orchestration

Design durable function chains for multi-step business processes with built-in retry and state management.

Migrate Legacy Services to Serverless

Transform existing in-process functions to isolated worker model with improved performance and dependency isolation.

试试这些提示

Setup Isolated Worker for .NET
Create a new Azure Functions project using the isolated worker model for .NET 8. Include an HTTP trigger endpoint that processes JSON payloads and returns validated responses. Add proper dependency injection setup and configuration binding.
Design Durable Functions Orchestration
Build a Durable Functions orchestration that processes orders through multiple stages: validation, payment processing, inventory check, and shipping notification. Include error handling with retry policies and human approval gates for high-value orders.
Optimize Cold Start Performance
Analyze my Azure Functions configuration for cold start issues. The function runs Python with a large ML model. Recommend specific settings for premium plan, instance warming, and package optimization to achieve sub-second response times.
Migrate In-Process to Isolated Worker
Convert this existing in-process Azure Function to the isolated worker model. Update the function signature, binding attributes, and dependency injection pattern. Highlight any breaking changes I need to address.

最佳实践

  • Always use the isolated worker model for new .NET projects to benefit from process isolation and side-by-side versioning
  • Implement async/await patterns throughout to prevent thread pool starvation and improve throughput
  • Reuse clients and connections via dependency injection or static instances to avoid connection exhaustion

避免

  • Blocking async calls with .Result or .Wait() which causes deadlocks and thread pool exhaustion
  • Creating new HttpClient instances per request instead of using IHttpClientFactory for connection pooling
  • Using the legacy in-process model for new projects when isolated worker provides better isolation and compatibility

常见问题

What is the difference between in-process and isolated worker models?
In-process runs inside the Azure Functions host process, while isolated worker runs in a separate process. Isolated worker supports side-by-side .NET versions, better dependency isolation, and is the recommended model for new projects.
How do I reduce cold start times for my Azure Functions?
Use Premium plan or dedicated App Service plan, implement warmup triggers, minimize package dependencies, enable ReadyToRun compilation for .NET, and consider using smaller deployment packages with external dependencies.
When should I use Durable Functions versus regular functions?
Use Durable Functions when you need stateful orchestration, complex workflows with multiple steps, fan-out/fan-in patterns, or long-running processes with human interaction. Use regular functions for simple stateless operations.
What are the timeout limits for Azure Functions?
Consumption plan has a maximum timeout of 5-10 minutes depending on configuration. Premium and dedicated plans support up to 30 minutes. For longer processes, use Durable Functions with built-in checkpointing.
How do I handle secrets and configuration in Azure Functions?
Use Azure Key Vault references in Application Settings, Managed Identity for authentication, and avoid hardcoding secrets. Access configuration via environment variables or IConfiguration in .NET isolated worker.
Can I use Azure Functions with containers?
Yes, Azure Functions supports containerized deployment on Azure Container Instances, Azure Kubernetes Service, or Azure Container Apps. This provides more control over the runtime environment and dependencies.

开发者详情

文件结构

📄 SKILL.md