skilld
All skills
microsoft avatar

/azure-prepare

@7995851 official
by microsoftmicrosoft/github-copilot-for-azure253 stars
206

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/microsoft/github-copilot-for-azure/azure-prepare

This session only. Nothing lands on disk.

referencesservicesapp-servicetemplatesrecipescosmosREADME.md

≈923 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Cosmos DB Recipe — REFERENCE ONLY

Adds Azure Cosmos DB (NoSQL) integration to an App Service base template.

Overview

This recipe composes with a Web API or Web App base template to add Cosmos DB data access. It provides the IaC delta (Cosmos account, database, container, RBAC) and per-language source code using the Cosmos DB SDK.

Integration Type

Aspect Value
Database Azure Cosmos DB for NoSQL
Auth Managed identity (DefaultAzureCredential)
SDK Microsoft.Azure.Cosmos (.NET), @azure/cosmos (Node.js), azure-cosmos (Python)
Hosting App Service (from base template)
Local Auth Disabled (disableLocalAuth: true) — RBAC-only

Composition Steps

Apply these steps AFTER azd init -t <base-template>:

# Step Details
1 Add IaC module Add Cosmos DB Bicep module to infra/app/
2 Wire into main Add module reference in main.bicep
3 Add app settings Add Cosmos endpoint + database + container settings
4 Add source code Add Cosmos client setup from source/{lang}.md
5 Add packages Add Cosmos SDK + Azure Identity packages

App Settings

Setting Value Purpose
COSMOS_ENDPOINT https://{account}.documents.azure.com:443/ Cosmos account endpoint
COSMOS_DATABASE_NAME app-db Target database
COSMOS_CONTAINER_NAME items Target container

Bicep App Settings Block

appSettings: [
  { name: 'COSMOS_ENDPOINT', value: cosmos.outputs.endpoint }
  { name: 'COSMOS_DATABASE_NAME', value: cosmos.outputs.databaseName }
  { name: 'COSMOS_CONTAINER_NAME', value: cosmos.outputs.containerName }
]

Note: No connection string or key is needed. The SDK uses DefaultAzureCredential which automatically resolves to the app's managed identity in Azure.

RBAC Roles Required

Role GUID Scope Purpose
Cosmos DB Account Reader fbdf93bf-df7d-467e-a4d2-9458aa1360c8 Cosmos account Read account metadata
Cosmos DB Built-in Data Contributor 00000000-0000-0000-0000-000000000002 Cosmos account (SQL role) Read/write data

Important: Cosmos DB uses its own SQL RBAC system (sqlRoleAssignments) for data plane operations, not standard Azure RBAC.

Networking (when VNET_ENABLED=true)

Component Details
Private endpoint Cosmos account → App Service VNet subnet
Private DNS zone privatelink.documents.azure.com

Resources Created

Resource Type Purpose
Cosmos DB Account Microsoft.DocumentDB/databaseAccounts Serverless NoSQL database
SQL Database databaseAccounts/sqlDatabases Application database
Container sqlDatabases/containers Data container with partition key
Role Assignment Microsoft.Authorization/roleAssignments Control plane access
SQL Role Assignment databaseAccounts/sqlRoleAssignments Data plane access

Source Code Examples

Language Source File
C# (.NET) source/dotnet.md
Python source/python.md
Node.js source/nodejs.md

References

Source: SKILL.md on GitHub

Third-party checks

1 alert8d4 checks · Risk SAFE
  • Gen Agent Trust Hub8d

    The azure-prepare skill provides a comprehensive environment for preparing Azure applications for deployment. It focuses on generating infrastructure-as-code and deployment configuration while strictly enforcing security best practices like managed identity usage and secret management via Key Vault. No malicious patterns or security risks were identified.

  • Socket8d

    5 alerts: gptAnomaly, gptSecurity

  • Snyk8d

    Risk: LOW · No issues

  • Runlayer6mo

    68/196 files flagged

Provenance

Signed by skilld at 7995851. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 weeks ago

Capability

metadata
{
  "author": "Microsoft",
  "version": "0.0.0-placeholder"
}

Topics

  • Infrastructure
  • azure
  • bicep
  • terraform
  • deployment
  • docker
  • functions
  • app-service

README badge

README badge for microsoft/github-copilot-for-azure/azure-prepare

What it does

Prepares Azure applications for deployment by generating infrastructure templates (Bicep or Terraform), azure.yaml configuration, and Dockerfiles. Covers new app creation, modernization, and hosting on App Service, Container Apps, or Functions—but excludes Python App Service deployments, copilot SDK apps, and cross-cloud migrations which have dedicated skills.

Generated from the current SKILL.md.

Frequently asked

Does this skill handle Python App Service deployments?
No. Use the python-appservice-deploy skill instead for Python code-only App Service deploys.
Can I use this skill for cross-cloud migration?
No. This skill is for Azure-native preparation. Use azure-cloud-migrate for migrations from AWS, GCP, or other clouds.
Does this skill support Copilot SDK apps?
No. Use azure-hosted-copilot-sdk for apps with @github/copilot-sdk or CopilotClient.
What infrastructure templates does this skill support?
Azure Developer CLI (azd), Bicep, Terraform, and Azure CLI. The skill creates infrastructure code, Dockerfiles, and configuration files—actual deployment execution is handled by the azure-deploy skill.
Does this skill delete existing project files?
No. When adding features to existing projects, it modifies files rather than deletes them. It never removes the project or workspace directory itself.

Generated from the current SKILL.md. These answers refresh after source changes.