AGENTIC MEMORY

Skills

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

← Back to Skills

azure-prepare

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

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.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-prepare 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 · 164

references/services/sql-database/README.md

Azure SQL Database

Managed relational database with ACID compliance and full SQL Server compatibility.

When to Use

  • Relational data with ACID requirements
  • Complex queries and joins
  • Existing SQL Server workloads
  • Reporting and analytics
  • Strong schema enforcement

Authentication

Default: Entra-only authentication (recommended)

  • Required for subscriptions with Entra-only policies
  • More secure than SQL authentication
  • Eliminates password management

Required Supporting Resources

| Resource | Purpose | |----------|---------| | Key Vault | Store connection strings | | Private Endpoint | Secure access (optional) |

SKU Selection

| Tier | Use Case | Features | |------|----------|----------| | Basic | Dev/test, light workloads | 5 DTUs, 2GB | | Standard | Production workloads | 10-3000 DTUs | | Premium | High-performance | In-memory OLTP | | Serverless | Variable workloads | Auto-pause, auto-scale | | Hyperscale | Large databases | 100TB+, instant backup |

Environment Variables

| Variable | Value | When to Set | |----------|-------|-------------| | AZURE_PRINCIPAL_ID | Current user's object ID | After azd init, before azd provision | | AZURE_PRINCIPAL_NAME | Current user's display name | After azd init, before azd provision | | SQL_SERVER | {server}.database.windows.net | Runtime (from Bicep outputs) | | SQL_DATABASE | Database name | Runtime (from Bicep outputs) | | SQL_CONNECTION_STRING | Full connection string (Key Vault) | Runtime (from Bicep outputs) |

Set principal variables:

PRINCIPAL_INFO=$(az ad signed-in-user show --query "{id:id, name:displayName}" -o json)
azd env set AZURE_PRINCIPAL_ID $(echo $PRINCIPAL_INFO | jq -r '.id')
azd env set AZURE_PRINCIPAL_NAME $(echo $PRINCIPAL_INFO | jq -r '.name')

References