.png){kind=small}
Using Built-in Extensions: @azure, @github, and Friends
Calling Azure, GitHub, and third-party Extensions from chat.
What You Will Learn
- Use @azure for Azure resources.
- Use @github for issues/PRs/actions.
- Use other built-in Extensions.
- Combine with @workspace.
- Recognize limits.
Why This Matters
Built-in Extensions (@azure, @github, etc.) are pre-installed and immediately useful. Knowing how to invoke them unlocks live-data workflows without custom development.
Concept Explained
Built-in Extensions are pre-installed @-participants for common services: Azure, GitHub, MongoDB, Datadog, etc. Invoke by typing @ + name in Chat.
How It Works
Type @ + Extension name in Chat. The Extension fetches data from its service. Copilot uses the data as context to answer your question.
Step-by-Step Tutorial
1. Identify service
What live data do you need? Azure deployments? GitHub issues? Sentry errors?2. Type @ + name
@azure, @github, @sentry, etc.3. Ask your question
'@azure show failing deployments in last hour'4. Verify
Cross-check the data with the actual service UI.5. Iterate
If wrong, refine the question or check service connectivity.Real-World Example
A developer used @github to ask 'show me open PRs waiting on review > 24 hours'. Got a list with PR numbers. Asked Copilot to summarize each PR's blockers. Saved 30 minutes of GitHub UI navigation per day.
Example Prompts / Commands / Code
@azure Show me failing deployments in the last hour.
@azure List all web apps in my subscription.
@azure What's the status of my-app-prod?
@azure Show me the error log for my-app-prod from 10 minutes ago.
@github Show me open PRs in repo team/service waiting on review > 24 hours.
@github List issues assigned to me with label 'bug' and priority 'high'.
@github Summarize the latest 5 commits in main.
@github Show me failing Actions workflows in the last 24 hours.
Common Mistakes
- Asking vague questions — Extensions return raw data without context.
- Not verifying data — Extensions may have stale caches.
- Using Extensions when a quick check on the service UI would suffice.
- Forgetting Extensions cost API calls to the underlying service.
Best Practices
- Be specific in your question.
- Verify data against the actual service UI.
- Use Extensions when checking the UI would take >2 minutes.
- Combine with @workspace for context-rich questions.
- Be mindful of API call costs on the underlying service.
Troubleshooting
| Problem | How to Fix |
|---|---|
| Extension returns nothing | Check service connectivity and your permissions. |
| Data is stale | Re-run. Some Extensions cache; check the service UI for live data. |
Practical Exercise
Your Turn
Use @github to ask about your open PRs. Then use it to list failing Actions. Verify the data against the GitHub UI.
Professional Challenge
Identify a daily task where you check a service UI. Use the relevant Extension instead. Measure time saved over a week.
Key Takeaways
- Built-in Extensions: @azure, @github, @sentry, etc.
- Invoke with @ + name in Chat.
- Be specific in questions.
- Verify data against service UI.
- Combine with @workspace for rich context.
Frequently Asked Questions
Do all Extensions work on all plans?
Are there rate limits?
Further Reading
Official References
SEO Metadata
SEO title: Using Built-in Extensions: @azure, @github, and Friends
Meta description: Calling Azure, GitHub, and third-party Extensions from chat.
Primary keyword: using built-in extensions
Secondary keywords: using built-in extensions: @azure, @github, and friends
Search intent: Informational
URL slug: /using-built-in-extensions-azure-github
Categories: AI Tools, GitHub Copilot
Tags: GitHub Copilot, Intermediate, Extensions, Azure, GitHub, IMCSEIAN, Tutorial, IMCSEIAN
Featured image concept: IMCSEIAN lesson card for Using Built-in Extensions: @azure, @github, and Friends
Comments
Comments
Post a Comment