-
Notifications
You must be signed in to change notification settings - Fork 881
[Hack Update] 066-AI fundamentals 0126 #1073
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
- Add generic .devcontainer/devcontainer.json at repo root - Updated Challenge-00-lab.md with working Dev Containers button - Root devcontainer uses universal image for broad compatibility - Allows users to start with generic container, then reopen specific folders in their specialized containers
- Updated URL to include ref=TestCodespaceButton parameter - Ensures testing uses the branch with the root devcontainer - Users can now test the full dev container workflow
…ve elements ✨ Key Enhancements: - 🎨 Changed Jekyll theme from midnight to modern cayman theme - 💅 Comprehensive custom CSS with modern styling and animations - 📊 Interactive elements: progress bars, alerts, status badges - 📁 Collapsible sections for better content organization - 📈 Mermaid diagram support for visual workflows - 🌙 Dark mode support and responsive design - 📱 Mobile-optimized experience - ♿ Improved accessibility features 🚀 Challenge-00 Improvements: - Added technology badges and progress indicators - Enhanced navigation with visual hierarchy - Interactive validation checklists - Collapsible help sections - Modern card-based layout 📝 Template Creation: - Created enhanced challenge template for consistency - Includes all new visual elements and best practices
- Created demonstration page showing all enhanced visual elements - Includes examples of alerts, badges, progress bars, cards, buttons - Shows Mermaid diagrams, collapsible sections, and enhanced tables - Provides reference for content creators using the new styling - Documents the complete visual enhancement system
✨ Theme Changes: - 🎨 Switched from dark Cayman to bright, clean Minima theme - 🌈 Redesigned entire color palette with bright, friendly colors - ☀️ Light background with colorful gradients throughout - 🎯 Maintained all interactive elements with brighter styling 🎨 Visual Improvements: - 💙 Bright blue primary colors instead of dark themes - 🌸 Colorful gradients in alerts, cards, and buttons - 🌅 Light backgrounds with subtle gradients - 🔆 Enhanced contrast for better readability - 🎨 Colorful progress bars with rainbow gradients - ✨ Bright, cheerful badge designs 🎯 Enhanced Elements: - 📊 Redesigned all components for brightness - 🎪 More colorful and engaging visual elements - 📱 Maintained mobile responsiveness - ♿ Kept accessibility features with better contrast
…re AD token provider, enhance error handling, and improve environment setup. Add Bicep module for Foundry project deployment with role assignments and diagnostic settings.
…s; clarify resource creation process and troubleshooting steps for students.
…e challenge documents for consistency and clarity.
…can be used prior to getting the PR approved in the main repo
…the introduction and use case sections.
…y deployment error details on failure.
…es for AI Services and Storage Account.
…cess to codespaces
…cess with devcontainer configuration
Removed reference to 'Hub' in project verification steps.
…despaces changes instead)
…atTheHack into ai-fundamentals-0126
Changed Codespace link
…es and environment setup. Add easy.txt for quick fixes.
…ecessary configurations.
…streamline HTML elements and remove unnecessary includes.
…d streamline content for clarity.
…nused configuration.
…resources and update API versions - Updated `deploy.sh` to derive deployment name from template filename and corrected environment variable for project endpoint. - Removed parameters and modules related to Application Insights and Container Registry from `main.bicep`. - Updated AI Services resource to use the latest API version and added project management properties. - Deleted unused modules for Application Insights, Container Registry, Foundry Project, and Hub. - Added new notebook for building a Research Assistant Agent using the Microsoft Agent Framework.
…-06-AgenticAI notebook
…t Foundry portal in CH-06-AgenticAI notebook
…A-RAG_for_structured_data notebook
…e clarity, and update success criteria
…-03 notebooks to improve clarity and maintainability.
| [template]="main.bicep" | ||
| [parameters]="main.bicepparam" | ||
| [resourceGroupName]="rg-ai-foundry-secure" | ||
| [resourceGroupName]="rg-microsoft-foundry-secure" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wondering if we should name the RG after the hack? "rg-wth-ai-fundamentals"? (Also, why does it say "secure" in the RG name?!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Now rg-openai-fundamentals for the default
| } | ||
| }, | ||
| "outputs": [], | ||
| "outputs": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be populated? I thought all the outputs should be blank? Perhaps this ended up committed after you were testing inline?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was fixed earlier
| { | ||
| "cell_type": "code", | ||
| "execution_count": null, | ||
| "execution_count": 15, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are all of these nulls changed to numbers like 15, 16, 17, etc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also fixed
| - [GitHub Codespaces](#setup-github-codespace) | ||
| - [Local Workstation](#setup-local-workstation) | ||
| - [Deploy Azure AI Foundry Resources](#deploy-azure-ai-foundry-resources) | ||
| - [Deploy Microsoft Foundry Resources](#deploy-azure-ai-foundry-resources) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - [Deploy Microsoft Foundry Resources](#deploy-azure-ai-foundry-resources) | |
| - [Deploy Microsoft Foundry Resources](#deploy-microsoft-foundry-resources) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the nav link needs to match the new header
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's delete this file since we're not using it anymore.
I can see copilot updated this file anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
|
||
| **NOTE:** Previously, each of the Content Safety services were hosted in their own portals. As of July 2024, they have been integrated into Azure AI Foundry. While searching for documentation of these services, you may find references to their original stand-alone portals. You should access these services via Azure AI Foundry for this hack. | ||
|
|
||
| ### Access Content Safety Service - TEMPORARY STEP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we confident that these "temporary steps" are no longer needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The deployment script does this now
This pull request updates documentation and environment configuration to consistently use "Microsoft Foundry" instead of "Azure AI Foundry" across all student and coach materials. It also introduces a new development container configuration for improved setup consistency. The most important changes are grouped below:
Dev Environment Setup
.devcontainer.jsonfile to define a standardized development container with pre-installed Azure CLI, Node.js, Python, and recommended VS Code extensions for a smoother onboarding experience.Documentation Updates: Foundry Naming and Instructions
Student Guide Enhancements
Resource Credential and Environment File Clarifications
.envfile, specifying where to find credentials in the Microsoft Foundry and Azure Portal, and updated language to avoid confusion regarding file renaming and resource verification. [1] [2] [3]Troubleshooting and Known Bugs
Let me know if you'd like a walkthrough of any specific section or further details on the new dev container setup!