정적 사이트입니다. 배포 대상은 docs/ 폴더이며 GitHub Pages(라이브: https://microsoft.github.io/azure-solution-hub/)로 서빙됩니다. docs/ 하위에 새 HTML 페이지를 추가할 때는 반드시 아래 두 스크립트를 <head>에 포함해야 합니다. 하나는 Microsoft Clarity, 다른 하나는 Google Analytics 4(GA4)입니다. 순서는 Clarity → GA4로 통일합니다. 현재 스니펫이 적용된 페이지: docs/index.html, docs/solution.html, docs/solutions/ontology/demo/index.html, docs/privacy/index.html. 페이지를 추가/삭제하거나 URL 구조가 바뀌면 아래 파일을 *함께 업데이트*합니다. 정식 URL은 라이브 호스트 https://microsoft.github.io/azure-solution-hub/를 기준으로 절대경로를 사용합니다. 솔루션 URL 형식은 solution.html?slug=<slug>이며, 솔루션 목록은 docs/solutions/solutions.md 매니페스트에서 관리됩니다. 새 솔루션을 추가하면 sitemap.xml과 llms.txt에도 해당 URL을 반영합니다. 실습…
This repository is part of Microsoft Build 2026. It contains session materials, demo code, and resources for session OD858: Personalize Your Windows PC with AI. When working in this repo,…
Before creating or modifying the state of any resource or object, always check for existing resources and their current state. This helps avoid unnecessary changes and ensures idempotency.
217mo agoReviewMountCreate a free account to mount
You are working on a project that uses Squad, an AI team framework. When picking up issues autonomously, follow these guidelines. IMPORTANT — run this check on EVERY session start,…
This repository is a Microsoft Ignite 2026 session template. Use the Ignite 2026 repository agent for setup. There are two workflows: Attendee guidance can remain in docs/ for intentional MkDocs or docs-site patterns when the root README links clearly to the entry point. Accept: BRK, WRK, LAB, ILL, LTG, THR, DEM, INV, PREL, PREB followed by digits.
이 리포지토리에서 작업할 때 반드시 참고해야 할 규칙과 워크플로우 모음입니다. 새 세션의 Copilot/코딩 에이전트는 사용자가 별도로 지시하지 않아도 이 문서를 그대로 따르세요. script.js는 templates.json을 먼저 읽고, 그 안의 categories[]를 따라가며…
- This repository publishes microsoft-opentelemetry, a Python OpenTelemetry distribution exposed through microsoft.opentelemetry. It configures tracing, metrics, logging, resource detection, exporters, and application and GenAI instrumentations. - The main setup API…
All agent context for this repository lives in AGENTS.md at the repository root. Read that file first. Do not add instructions here — update AGENTS.md instead.
The authoritative guidance for AI coding agents working in this repository — the lab's scenario canon (single source of truth) and its MCAP authoring conventions — lives in AGENTS.md. Read it before editing any page under docs/.
This repo (microsoft/end-to-end-observability) is a monorepo of independent Azure observability subprojects that share the SRE-Agent + Azure Monitor theme but have separate tooling, no shared root build, and their own READMEs. Always cd into the relevant subproject before running anything. The root README.md is a setup placeholder — ignore it for technical context. The most important convention: workbook JSON is generated, never hand-edited. - sre-agent-observability-workbooks/: edit builder/specs/*.py (one spec per workbook) or builder/shared/*, then rebuild. command_center.py is the reference spec.…
Read .github/github-instructions.md, AGENTS.md, and Software-Requirements-Document.md before changing this repository. The detailed rules in those files are binding. Non-negotiable Milestone 1 constraints: - The platform is always the receiving firm. - Run deterministic FINRA validation before any model call. - Account-type mismatch blocks with code 03. - Never fabricate an ACATS control number or unresolved [Qn] value. - Hosted invocations must write to legal-hold-protected WORM Blob or fail. - SQL, Fabric, Cosmos DB, and live ACATS submission are deferred. - Humans…
Use the official MCP Python SDK v2 documentation at <https://py.sdk.modelcontextprotocol.io/> and the protocol documentation at <https://modelcontextprotocol.io/> when changing the MCP server. Use the Azure Functions Python developer reference at <https://learn.microsoft.com/azure/azure-functions/functions-reference-python> when changing the Function App entry point or host configuration.
- This repository publishes @microsoft/opentelemetry-browser, a browser-focused OpenTelemetry distribution for traces and logs with Azure Monitor exporters, browser instrumentations, resource detection, session and user context, page-view telemetry, and lifecycle controls. - The distribution supports independent telemetry instances. Each instance owns its providers, processors, exporters, instrumentations, resources, identity, session, and lifecycle state. Page context, propagation, and page-operation correlation are realm-wide and coordinated across instances. Global routing providers select an instance and return tracers and loggers bound to it. - Public package…
pypi-lockdown is a CLI tool that bootstraps Python environments to use internal, authenticated PyPI feeds. It has two commands: Entry point: src/pypi_lockdown/__main__.py parses args and treats a bare URL as shorthand for configure URL. Versioning is dynamic via setuptools-scm from git tags.
scitt-verifier verifies SCITT transparent statements and evaluates the relying party's policy, offline by default. Artifact binding and resource adapters are optional; a deployed ledger is not the general subject of verification. Receipt proof support is currently CCF VDS only. It returns pipeline exit codes and is a security gate. The failure that matters is not a crash — it is a PASS printed for something nobody actually checked, because that answer is believed and acted on. Read CONTRIBUTING.md first; the…
This repository contains AI Agent Skills for assessing retiring Azure Communication Services (ACS) resources across Azure subscriptions. Scans Azure subscriptions for ACS resources that use retiring standalone SDKs and APIs, measures actual usage over 90 days, calculates migration urgency, and generates reports with migration guidance. **Impacted ACS services (planned announcement July 22, 2026 · retirement July 31, 2028): Retired after July 31, 2028:** - Email Service (standalone ACS SDK) — retires 2028-07-31 - SMS API (standalone ACS SDK) - Chat…
Read AGENTS.md, README.md, instructions/README.md, and instructions/copilot.md before helping with setup. - Scope is the Fabric-only LTG243 demo. - Use Node.js 24+ and the exact Fabio version pinned in .fabio-version (0.79.0). Upgrade with fabio upgrade --target-version 0.79.0 if needed. - Run the manifest check and validator before any deployment work. - Ask for the target workspace ID; do not infer or reuse one from logs. - Run create-data.sh or create-data.ps1 with --dry-run first. - Show the workspace and command before running…