azure-hosted-copilot-sdk

Scaffold, configure, and deploy GitHub Copilot SDK applications to Azure Container Apps.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/stephschofield/beth --skill azure-hosted-copilot-sdk-stephschofield
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-hosted-copilot-sdk
Source: https://github.com/stephschofield/beth/tree/main/.github/skills/azure-hosted-copilot-sdk
Command: npx skills add https://github.com/stephschofield/beth --skill azure-hosted-copilot-sdk-stephschofield

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building and deploying a GitHub Copilot SDK application on Azure involves many moving parts: scaffolding the service, wiring Bicep infrastructure, configuring model providers, and handling authentication. This Skill guides the entire workflow from greenfield scaffolding to production deployment, including Azure BYOM (bring your own model) configuration. ## Core Features & Use Cases - Project Scaffolding: Initialize new Copilot SDK services with azd init --template azure-samples/copilot-sdk-service, or add the SDK service alongside an existing repository without overwriting files. - Model Configuration: Choose between GitHub default models, specific GitHub models via listModels(), or Azure BYOM with DefaultAzureCredential and managed identity, including supported model families and API version requirements. - Deployment Pipeline: Copy Bicep infra, adapt azure.yaml, wire the GitHub token flow through Key Vault, and deploy to Azure Container Apps. - Use Case: You have an existing Express app and want to add a Copilot-powered chat endpoint hosted on Azure with your own Azure OpenAI o4-mini deployment. The Skill walks you through SDK integration, BYOM provider config, infra setup, and azd deployment. ## Quick Start Ask the agent to scaffold a new Copilot SDK service and deploy it to Azure with an Azure OpenAI model.

Frequently Asked Questions about azure-hosted-copilot-sdk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a GitHub Copilot SDK app to Azure?▼

Scaffold the azure-samples/copilot-sdk-service template with azd init, then run the azure-prepare, azure-validate, and azure-deploy steps in order. For existing apps, scaffold to a temp directory and copy the infra folder, azure.yaml, and token script into your project.

How do I use my own Azure OpenAI model with the Copilot SDK?▼

Pass a provider config to createSession with your Azure endpoint, a bearer token from DefaultAzureCredential, wireApi set to completions, and apiVersion nested under azure. Only o-series and gpt-5 family models support the SDK's encrypted content.

Which models support Copilot SDK BYOM on Azure?▼

BYOM supports o-series models (o3, o3-mini, o4-mini) and the gpt-5 family (gpt-5, gpt-5-mini, gpt-5.1 variants, codex models). Models like gpt-4o and gpt-4.1 fail with encrypted content errors or silent timeouts.

Should I use DefaultAzureCredential in production on Azure?▼

No. DefaultAzureCredential is intended for local development where it picks up CLI credentials. In production use ManagedIdentityCredential, which is deterministic, avoids fallback-chain latency, and requires no stored secrets.

Why does my Copilot SDK deployment fail with a 400 or 404 error?▼

A 400 with tool calls usually means wireApi is set to responses instead of completions. A 404 CAPIError typically means apiVersion was placed at the top level instead of nested under the azure key in the provider config.

Can I add the Copilot SDK to an existing Node.js or Python app?▼

Yes. Install @github/copilot-sdk (or the Python equivalent), add a route that creates a CopilotClient session, and register it with your existing server. Do not create a separate server or duplicate startup logic.