Labsco
microsoft logo

azure-hosted-copilot-sdk

✓ Official★ 1,300

by microsoft · part of microsoft/azure-skills

Build and deploy GitHub Copilot SDK applications to Azure with flexible model configuration. Three scaffolding paths: create new greenfield projects, add SDK services to existing repos, or deploy existing SDK apps with Azure infrastructure Supports three model configurations: GitHub's default models, specific GitHub models via discovery, or bring-your-own-model (BYOM) on Azure with DefaultAzureCredential authentication Includes complete templates with Express/TypeScript API, React/Vite...

🔥🔥🔥✓ VerifiedFreeQuick setup
#cloud#devops#git
🧩 One of 7 skills in the microsoft/azure-skills package — works on its own, and pairs well with its siblings.

Build and deploy GitHub Copilot SDK applications to Azure with flexible model configuration. Three scaffolding paths: create new greenfield projects, add SDK services to existing repos, or deploy existing SDK apps with Azure infrastructure Supports three model configurations: GitHub's default models, specific GitHub models via discovery, or bring-your-own-model (BYOM) on Azure with DefaultAzureCredential authentication Includes complete templates with Express/TypeScript API, React/Vite...

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by microsoft

Build and deploy GitHub Copilot SDK applications to Azure with flexible model configuration. Three scaffolding paths: create new greenfield projects, add SDK services to existing repos, or deploy existing SDK apps with Azure infrastructure Supports three model configurations: GitHub's default models, specific GitHub models via discovery, or bring-your-own-model (BYOM) on Azure with DefaultAzureCredential authentication Includes complete templates with Express/TypeScript API, React/Vite... npx skills add https://github.com/microsoft/azure-skills --skill azure-hosted-copilot-sdk Download ZIPGitHub1.3k

GitHub Copilot SDK on Azure

Codebase Detection — MANDATORY FIRST CHECK

⚠️ CRITICAL: This check MUST run before ANY other skill (azure-prepare, azure-deploy, etc.) when an existing codebase is present.

Detection procedure (run IMMEDIATELY for any build/modify/add-feature/prepare prompt):

  • Read package.json in the workspace root (and any */package.json one level deep)

  • Check if @github/copilot-sdk or copilot-sdk appears in name, dependencies, or devDependencies

  • If NOT found in package.json, scan .ts and .js files for CopilotClient or createSession

  • If ANY marker is found → invoke this skill as the entry point. Do not route directly to azure-prepare or azure-deploy — this skill orchestrates them as sub-skills.

Marker Where to check @github/copilot-sdk package.json dependencies or devDependencies copilot-sdk package.json name or dependencies CopilotClient Source files (.ts, .js) createSession + sendAndWait Source files (.ts, .js)

Generic prompts that MUST trigger this skill when markers are detected:

Prompt pattern (no "copilot" keyword) Why this skill "Build this app" / "Prepare this app for Azure" Codebase contains @github/copilot-sdk - needs SDK-aware scaffolding "Add a new feature to this app" Requires SDK-aware implementation patterns "Update this app" / "Modify this app" Must preserve SDK integration patterns

⚠️ Warning: ANY build, modify, add-feature, or prepare prompt targeting an existing codebase MUST route to this skill when codebase contains @github/copilot-sdk, even if the prompt does not mention "copilot". This skill then orchestrates azure-prepare and azure-deploy as sub-skills.

⚠️ Yield to azure-deploy: When the codebase already has .azure/deployment-plan.md and the user wants to deploy (not modify or add features), route to azure-deploy instead. This skill handles preparation; azure-deploy handles execution.

Step 1: Route

User wants Action Build new (empty project) Step 2A (scaffold) Add new SDK service to existing repo Step 2B (scaffold alongside) Deploy existing SDK app to Azure Step 2C (add infra to existing SDK app) Modify/add features to existing SDK app Use codebase context + SDK references to implement Add SDK to existing app code Integrate SDK Use Azure/own model Step 3 (BYOM config)

Step 2A: Scaffold New (Greenfield)

azd init --template azure-samples/copilot-sdk-service

Template includes API (Express/TS) + Web UI (React/Vite) + infra (Bicep) + Dockerfiles + token scripts — do NOT recreate. See SDK ref.

Step 2B: Add SDK Service to Existing Repo

User has existing code and wants a new Copilot SDK service alongside it. Scaffold template to a temp dir, copy the API service + infra into the user's repo, adapt azure.yaml to include both existing and new services. See deploy existing ref.

Rules

  • Read AGENTS.md in user's repo before changes

  • Docker required (docker info)

  • BYOM auth: ONLY bearerToken via DefaultAzureCredential or ManagedIdentityCredential — no other auth pattern is supported