[tmeschter]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

Updating awesome-copilot to point to the latest version of the Azure external plugin.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🔒 PR Risk Scan Results

Scanned 2 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🚦 Submission status: 👀 Ready for review

Risk tier: merge-risk:high — Privileged execution, automation, or review-policy change
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access, including a maintainer with admin or maintain permission.

Why this tier

• plugins/external.json is a high-risk path (automation, scripts, MCP config, hooks, or review policy)

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Plugin and extension validation	✅ Passed	Passed · logs
Plugin structure	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	✅ Passed	Passed · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs
Canvas/plugin smoke test	✅ Passed	Passed · logs

Review

• Approvals: 0/1
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• Still needed: 1 more approval(s); an approval from a maintainer with admin or maintain permission
• The core-maintainers pool is not staffed yet; an approver with admin or maintain permission is required instead.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for c45c16a · gate run · This comment is maintained automatically — see submission gate docs.}

[github-actions]

🛑 External plugin PR checks failed (submitter fixes required)

• Changed entries detected: 1
• Workflow state label: requires-submitter-fixes
• Full logs: Download quality gate artifact
• Status legend: ✅ pass · ⚠️ warning · 🛑 fail

Per-plugin quality summary

Plugin	spec compliance	vally lint	install smoke test	version match	ref/sha consistency	canvas structure	overall	source tree
azure	🛑 fail	✅ pass	✅ pass	✅ pass	⚪ not_run	⚪ not_run	🛑 fail	39b8cb013c5d0886e8819e7147f1eec1eebc0cd6

Gate output details

azure - spec compliance (🛑 fail)

Agent Plugins v1.0.0 manifest errors:
- manifest location is ".plugin/plugin.json"; expected "plugin.json" at plugin root
- $schema should be "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json"
- top-level field "skills" is not part of Agent Plugins v1.0.0
- top-level field "mcpServers" is not part of Agent Plugins v1.0.0
- top-level field "hooks" is not part of Agent Plugins v1.0.0
- schema validation: manifest must have required property '$schema'
- schema validation: manifest must NOT have additional properties
- schema validation: manifest must NOT have additional properties
- schema validation: manifest must NOT have additional properties

azure - vally lint (✅ pass)

✅ airunway-aks-setup (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.
✅ appinsights-instrumentation (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.
✅ azure-ai (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.
✅ azure-aigateway (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.
✅ azure-app-onboard-prereq (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.
✅ azure-app-onboard (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.
✅ azure-cloud-migrate (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are s
...output truncated...

azure - install smoke test (✅ pass)

Install smoke test succeeded. Verified /tmp/external-plugin-quality-TfJZWb/copilot-home/.copilot/installed-plugins/external-plugin-intake/azure/.plugin/plugin.json.

azure - version match (pass)

- 39b8cb013c5d0886e8819e7147f1eec1eebc0cd6: matched version "1.2.108" at ".github/plugins/azure-skills/.plugin/plugin.json".

azure - ref/sha consistency (not_run)

Ref/SHA consistency gate skipped because one of source.ref or source.sha was not provided.

azure - canvas structure (not_run)

Canvas structure gate skipped because plugin is not tagged with "canvas".

- azure: spec=fail, vally-lint=pass, install-smoke=pass, version-match=pass, ref-sha-consistency=not_run, canvas-structure=not_run, overall=fail

[Copilot]

🔵 Needs a closer look

Independent inspection of the pinned upstream commit was blocked by Microsoft organization SAML enforcement, so the quality gates or a maintainer must verify the SHA and manifest version 1.2.108 before merging.

No open issues 🎉

What changed in this PR

Updates the Azure external plugin reference to version 1.2.108 and synchronizes its pinned source commit across the catalog and generated marketplace metadata.

Changes:

• Updated the Azure plugin from 1.2.97 to 1.2.108.
• Updated the pinned source SHA to 39b8cb013c5d0886e8819e7147f1eec1eebc0cd6.
• Synchronized .github/plugin/marketplace.json with plugins/external.json.

This pull request is ready to be approved.

File	Description
plugins/​external.json	Updates the Azure external plugin version and immutable source commit.
.github/​plugin/​marketplace.json	Synchronizes the generated marketplace metadata with the updated plugin entry.

_{Review effort: Lite (auto)}

[aaronpowell]

I'll merge as is but can we action using the Agent Plugin spec for the next release.

[tmeschter]

I'll merge as is but can we action using the Agent Plugin spec for the next release.

@aaronpowell Yeah, I'm working on it. We make heavy use of hooks but there is very little documentation on how those are supported in Agent Plugin scenarios, so verification is taking some time.