Skip to content

Commit 1d1ca3d

Browse files
usepowershellusepowershell
committed
instructions in progress
1 parent a84970b commit 1d1ca3d

File tree

3 files changed

+118
-91
lines changed

3 files changed

+118
-91
lines changed

‎README.MD‎

Lines changed: 15 additions & 78 deletions
Original file line numberDiff line numberDiff line change
@@ -1,51 +1,3 @@
1-
# Welcome AI Tour 26 Creators!
2-
3-
Thanks for creating content for AI Tour 26.
4-
5-
One of our opportunities from FY25 was make a more consistent experience for attendees. Following this template, and keeping users in these repos, will help us achieve this opportunity for this year's AI Tour.
6-
7-
Steps:
8-
9-
## Docs using MKDocs
10-
If you are interested in using mkdocs, this repo is configured for it.
11-
1. update the `mkdocs.yml` file to reference your session. Look particularly for the `site_name`, `site_author`, and `repo_name` tags.
12-
1. Subfolders in the docs folder will show up as tabs in the navigation bar.
13-
14-
If you want to disable mkdocs:
15-
1. Delete the mkdocs.yml file.
16-
1. Delete the references to it in [docs/README.md](./docs/README.md)
17-
1. Delete the docs/assets folder and its contents.
18-
19-
## Other folders
20-
Note the data, docs, src, lab, session-delivery-resources folders.
21-
1. Remove folders that you dont need.
22-
1. Please keep and use the folders that you do need. e.g. put your data in the data folder, and put your docs in the docs folder.
23-
24-
## Update Readme
25-
1. Fill out the content below in this file, below the banner graphic.
26-
27-
## Update Repo Info
28-
29-
1. Note the data, docs, src, lab, session-delivery-resources folders.
30-
31-
1. Remove folders that you dont need, but please keep and use the folders that you do need. e.g. put your data in the data folder, and put your docs in the docs folder.
32-
33-
1. Fill out the content below in this file, below the banner graphic.
34-
35-
1. Update the Repo Info for this repo
36-
1. Click the gear icon⚙️ in the upper right.
37-
1. Set a good description of this repo.
38-
1. Add the technologies that you're using in this session. E.g. the same items that are in the Technologies Used section below.
39-
40-
1. Please embed links to Learn with your campaign codes!
41-
42-
## Questions?
43-
Send them to Mike Kinsman, Erik Weis, and cc Anthony Bartolo.
44-
45-
## Last step
46-
Delete this line and everything above it!
47-
48-
491
<p align="center">
502
<img src="img/Banner-MS-AI-Tour-26.png" alt="decorative banner" width="1200"/>
513
</p>
@@ -60,7 +12,6 @@ If you will be delivering this session, check the [session-delivery-sources](./s
6012

6113
Learn how Copilot in Azure boosts app resilience by reviewing logs and streamlining ops. Get hands-on with real scenarios, and see how GitHub Copilot can enhance your build and deployment workflows.
6214

63-
6415
### 🧠 Learning Outcomes
6516

6617
By the end of this session, learners will be able to:
@@ -70,7 +21,6 @@ By the end of this session, learners will be able to:
7021
- Guide **GitHub Copilot** to enhance CI/CD security and reduces manual configuration effort
7122
- Build effective prompts for **AI assistance** to accelerate both operational troubleshooting and infrastructure
7223

73-
7424
### 💻 Technologies Used
7525

7626
1. Copilot in Azure
@@ -79,50 +29,37 @@ By the end of this session, learners will be able to:
7929
1. Azure Developer CLI
8030

8131
### 🔗 Session Resources
82-
| Resources | Links | Description |
83-
|:-------------------|:----------------------------------|:-------------------|
32+
33+
| Resources | Links | Description |
34+
| :------------------------------------ | :-------------------------- | :----------------------------- |
8435
| Additional Resources for this session | https://learn.microsoft.com | Links specific to this session |
8536

8637
### 📚 Continued Learning Resources
87-
| Resources | Links | Description |
88-
|:-------------------|:----------------------------------|:-------------------|
89-
| AI Tour 2026 Resource Center | https://aka.ms/AITour26-Resource-center | Links to all repos for AI Tour 26 Sessions |
90-
| Azure AI Foundry Community Discord | [![Microsoft Azure AI Foundry Discord](https://dcbadge.limes.pink/api/server/ByRwuEEgH4)](https://discord.com/invite/ByRwuEEgH4)| Connect with the Azure AI Foundry Community! |
91-
| Learn at AI Tour | https://aka.ms/LearnAtAITour | Continue learning on Microsoft Learn |
38+
39+
| Resources | Links | Description |
40+
| :--------------------------------- | :------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------- |
41+
| AI Tour 2026 Resource Center | https://aka.ms/AITour26-Resource-center | Links to all repos for AI Tour 26 Sessions |
42+
| Azure AI Foundry Community Discord | [![Microsoft Azure AI Foundry Discord](https://dcbadge.limes.pink/api/server/ByRwuEEgH4)](https://discord.com/invite/ByRwuEEgH4) | Connect with the Azure AI Foundry Community! |
43+
| Learn at AI Tour | https://aka.ms/LearnAtAITour | Continue learning on Microsoft Learn |
9244

9345
### 🌐 Multi-Language Support
9446

95-
*languages will go here when its time to localize*
47+
_languages will go here when its time to localize_
9648

9749
## Content Owners
9850

99-
<!-- TODO: Add yourself as a content owner
100-
1. Change the src in the image tag to {your github url}.png
101-
2. Change INSERT NAME HERE to your name
102-
3. Change the github url in the final href to your url. -->
103-
104-
10551
<table>
10652
<tr>
107-
<td align="center"><a href="http://github.com/mikekinsman">
108-
<img src="https://github.com/mikekinsman.png" width="100px;" alt="INSERT NAME HERE"
109-
"/><br />
110-
<sub><b> INSERT NAME HERE
111-
</b></sub></a><br />
112-
<a href="https://github.com/mikekinsman" title="talk">📢</a>
113-
</td>
114-
<td align="center"><a href="http://github.com/mikekinsman">
115-
<img src="https://github.com/mikekinsman.png" width="100px;" alt="INSERT NAME HERE
53+
<td align="center"><a href="http://github.com/smurawski">
54+
<img src="https://github.com/smurawski.png" width="100px;" alt="Steven Murawski"
11655
"/><br />
117-
<sub><b>INSERT NAME HERE
56+
<sub><b> Steven Murawski
11857
</b></sub></a><br />
119-
<a href="https://github.com/mikekinsman" title="talk">📢</a>
58+
<a href="https://github.com/smurawski" title="talk">📢</a>
12059
</td>
12160
</tr></table>
12261

123-
##
124-
125-
## Responsible AI
62+
## Responsible AI
12663

12764
Microsoft is committed to helping our customers use our AI products responsibly, sharing our learnings, and building trust-based partnerships through tools like Transparency Notes and Impact Assessments. Many of these resources can be found at [https://aka.ms/RAI](https://aka.ms/RAI).
12865
Microsoft’s approach to responsible AI is grounded in our AI principles of fairness, reliability and safety, privacy and security, inclusiveness, transparency, and accountability.

‎docs/prompt_checklist.md‎

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
# ✅ Prompt Design Checklist for GitHub Copilot & Copilot in Azure
2+
3+
## 1. Define Clear Intent
4+
- [ ] What do you want the AI to do? (e.g., generate code, analyze logs, suggest improvements)
5+
- [ ] Use action verbs: *generate*, *review*, *optimize*, *deploy*, *analyze*, *fix*
6+
- [ ] Avoid vague requests like “help me with this” — be specific.
7+
8+
**Examples:**
9+
- GitHub Copilot: `Generate a secure CI/CD pipeline for a Node.js app using GitHub Actions.`
10+
- Azure Copilot: `Analyze AKS cluster logs for failed pod restarts in the last 24 hours.`
11+
12+
---
13+
14+
## 2. Include Context
15+
- [ ] Mention the environment (e.g., AKS, Azure Functions, GitHub Actions)
16+
- [ ] Specify the file or resource (e.g., Dockerfile, pipeline.yml, log file)
17+
- [ ] Provide relevant metadata (e.g., service name, region, timeframe)
18+
19+
**Example:**
20+
`Review the Dockerfile for the payment-service microservice and suggest security improvements.`
21+
22+
---
23+
24+
## 3. Use Natural Language, But Be Precise
25+
- [ ] Write prompts as you would explain to a colleague.
26+
- [ ] Avoid jargon unless necessary.
27+
- [ ] Use complete sentences when possible.
28+
29+
**Example:**
30+
`Create a Bicep template to deploy a web app with autoscaling and logging enabled.`
31+
32+
---
33+
34+
## 4. Break Down Complex Tasks
35+
- [ ] Split multi-step tasks into separate prompts.
36+
- [ ] Use numbered steps or bullet points if needed.
37+
38+
**Example:**
39+
1. `Identify security vulnerabilities in the pipeline.yml.`
40+
2. `Add steps to scan dependencies using GitHub Advanced Security.`
41+
42+
---
43+
44+
## 5. Request Examples or Explanations
45+
- [ ] Ask Copilot to show examples or explain its suggestions.
46+
47+
**Example:**
48+
`Show an example of a retry policy for Azure Functions in Bicep.`
49+
50+
---
51+
52+
## 6. Iterate and Refine
53+
- [ ] Review AI output and revise the prompt if needed.
54+
- [ ] Use feedback to improve prompt clarity.
55+
56+
**Example:**
57+
Initial: `Improve the build process.`
58+
Refined: `Add caching to the npm install step in the GitHub Actions workflow to speed up builds.`
59+
60+
---
61+
62+
## 7. Use Prompts for Operational Insights
63+
- [ ] Log analysis: `Summarize error patterns from the last 3 days.`
64+
- [ ] Infrastructure as Code: `Generate a Bicep template for a resilient AKS cluster.`
65+
- [ ] Security: `Recommend NSG rules for a public-facing web app.`
66+
67+
---
68+
69+
## 8. Prompt for Collaboration
70+
- [ ] Generate documentation, dashboards, or summaries for team sharing.
71+
72+
**Example:**
73+
`Create a markdown summary of the deployment changes for the last release.`
74+
75+
---
76+
77+
## 9. Avoid Confidential or Sensitive Prompts
78+
- [ ] Do not include secrets, credentials, or internal user data.
79+
- [ ] Use placeholders or mock data.
80+
81+
**Example:**
82+
Use `Fix the login bug for a sample user` instead of real user info.
83+
84+
---
85+
86+
## 10. Use Prompt Templates for Reusability
87+
88+
```markdown
89+
### Prompt Template: Log Analysis
90+
"Analyze logs from [resource name] in [region] for [error type] between [start time] and [end time]. Summarize root causes and suggest remediation."

‎session-delivery-resources/readme.md‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -8,30 +8,30 @@ Prior to delivering the workshop please:
88
2. Watch the video presentation
99
3. Ask questions of the content leads! We're here to help!
1010

11-
1211
## 📁 File Summary
1312

14-
| Resources | Links | Description |
15-
|-------------------|----------------------------------|-------------------|
16-
| Workshop Slide Deck | [Presentation](https://aka.ms/) | Presentation slides for this workshop with presenter notes and embedded demo video |
17-
| Session Delivery Deck | [Deck](https://aka.ms/) | The session delivery slides |
18-
| More Files | [Some More Files](https://aka.ms/) | More File Descriptions |
19-
13+
| Resources | Links | Description |
14+
| --------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------- |
15+
| Workshop Slide Deck | [Presentation](https://aka.ms/) | Presentation slides for this workshop with presenter notes and embedded demo video |
16+
| Session Delivery Deck | [Deck](https://aka.ms/) | The session delivery slides |
17+
| Prompt Checklist | [Prompt Checklist](../docs/prompt_checklist.md) | Tips for effective prompting |
2018

2119
## 🚀Get Started
2220

23-
The workshop is divided into multiple sections including 16 slides, 1 demo and 2 hands on labs.
21+
The workshop is divided into multiple sections including a short slide presentation and 3 hands on labs, with four bonus labs if there's time or for future exploration.
2422

2523
### 🕐Timing
2624

27-
| Time | Description
28-
--------------|-------------
29-
0:00 - 5:00 | Intro and overview
30-
5:00 - 70:00 | Session Steps
31-
70:00 - 75:00 | Wrap up and Q&A
25+
| Time | Description |
26+
| ------------- | ------------------ |
27+
| 0:00 - 10:00 | Intro and overview |
28+
| 10:00 - 70:00 | Session Steps |
29+
| 70:00 - 75:00 | Wrap up and Q&A |
3230

3331
### 🏋️Preparation
32+
3433
Preparation Notes go here
3534

3635
### 🖥️Demos
36+
3737
Description of demos goes here

0 commit comments

Comments
 (0)