AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

customize

Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--customize at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 4

references/customize-guides.md

Customize Guides — Selection Guides & Advanced Topics

Reference for: models/deploy-model/customize/SKILL.md

Table of Contents: Selection Guides · Advanced Topics

Selection Guides

How to Choose SKU

| SKU | Best For | Cost | Availability | |-----|----------|------|--------------| | GlobalStandard | Production, high availability | Medium | Multi-region | | Standard | Development, testing | Low | Single region | | ProvisionedManaged | High-volume, predictable workloads | Fixed (PTU) | Reserved capacity | | DataZoneStandard | Data residency requirements | Medium | Specific zones |

Decision Tree:

Do you need guaranteed throughput?
├─ Yes → ProvisionedManaged (PTU)
└─ No → Do you need high availability?
        ├─ Yes → GlobalStandard
        └─ No → Standard

How to Choose Capacity

For TPM-based SKUs (GlobalStandard, Standard):

| Workload | Recommended Capacity | |----------|---------------------| | Development/Testing | 1K - 5K TPM | | Small Production | 5K - 20K TPM | | Medium Production | 20K - 100K TPM | | Large Production | 100K+ TPM |

For PTU-based SKUs (ProvisionedManaged):

Use the PTU calculator based on:

  • Input tokens per minute
  • Output tokens per minute
  • Requests per minute

Capacity Planning Tips:

  • Start with recommended capacity
  • Monitor usage and adjust
  • Enable dynamic quota for flexibility
  • Consider spillover for peak loads

How to Choose RAI Policy

| Policy | Filtering Level | Use Case | |--------|----------------|----------| | Microsoft.DefaultV2 | Balanced | Most applications | | Microsoft.Prompt-Shield | Enhanced | Security-sensitive apps | | Custom | Configurable | Specific requirements |

Recommendation: Start with Microsoft.DefaultV2 and adjust based on application needs.


Advanced Topics

PTU (Provisioned Throughput Units) Deployments

What is PTU?

  • Reserved capacity with guaranteed throughput
  • Measured in PTU units, not TPM
  • Fixed cost regardless of usage
  • Best for high-volume, predictable workloads

PTU Calculator:

Estimated PTU = (Input TPM × 0.001) + (Output TPM × 0.002) + (Requests/min × 0.1)

Example:
- Input: 10,000 tokens/min
- Output: 5,000 tokens/min
- Requests: 100/min

PTU = (10,000 × 0.001) + (5,000 × 0.002) + (100 × 0.1)
    = 10 + 10 + 10
    = 30 PTU

PTU Deployment:

az cognitiveservices account deployment create \
  --name <account-name> \
  --resource-group <resource-group> \
  --deployment-name <deployment-name> \
  --model-name <model-name> \
  --model-version <version> \
  --model-format "OpenAI" \
  --sku-name "ProvisionedManaged" \
  --sku-capacity 100  # PTU units

Spillover Configuration

Spillover Workflow:

  1. Primary deployment receives requests
  2. When capacity reached, requests overflow to spillover target
  3. Spillover target must be same model or compatible
  4. Configure via deployment properties

Best Practices:

  • Use spillover for peak load handling
  • Spillover target should have sufficient capacity
  • Monitor both deployments
  • Test failover behavior

Priority Processing

What is Priority Processing?

  • Prioritizes your requests during high load
  • Available for ProvisionedManaged SKU
  • Additional charges apply
  • Ensures consistent performance

When to Use:

  • Mission-critical applications
  • SLA requirements
  • High-concurrency scenarios