Cannot sign in
Check that you are using the assigned `koicatiu.onmicrosoft.com` account. Keep working in mock mode and ask your tutor to escalate.
Azure practice environment
Azure Lab Guide
A practical guide for using Azure and Microsoft Foundry during KOICA-TIU labs and hackathons. Use the assigned resources, keep the scope small, and protect credentials.
Lab Workflow
1
Sign in
Use the account provided by the operations team and complete MFA when required.
2
Open Foundry
Go to Microsoft Foundry and select your assigned team project.
3
Test a model call
Run a short prompt in the playground or a minimal Python example.
4
Build the prototype
Connect the model to a small UI, notebook, or API.
5
Prepare the demo
Save screenshots or a short recording in case live demo fails.
6
Clean up
Stop idle apps and confirm resource status with your tutor.
Account Setup
Use assigned account
Do not use a personal Microsoft account for the hackathon build. Use the account given by operations.
Complete MFA
Set up the required authentication method during first sign-in. Ask a tutor if the prompt blocks your progress.
Check team scope
Confirm that your team resource group, Foundry project, and app slot match your team number.
Keep credentials local
Put endpoint, key, and deployment names in `.env` only. Commit `.env.example`, not `.env`.
Foundry Quickstart
1
Open the assigned project
Select your team project and confirm that your tutor can see the same project name.
2
Find model deployment
Write down the deployment name in your local `.env`; do not put it in public screenshots if it reveals internal setup.
3
Run one small prompt
Use one short test question first. Avoid repeated long prompts while designing the UI.
4
Connect code
Use the sample template or a short Python client to call the model from your prototype.
5
Prepare fallback
Save one screenshot or short video after your first successful model response.
Usage Rules
These rules protect the shared project credit so both semesters and both hackathons can use Azure.
Use team resources only
Do not create resources outside your assigned project or app slot.
Keep prompts small
Test with short prompts first. Long repeated prompts consume quota quickly.
Never expose secrets
Do not paste API keys, endpoints, passwords, or tokens into GitHub, slides, screenshots, or chats.
Stop idle apps
After demos, stop or return App Service slots to the operations team.
Ask tutors early
Report quota, login, or deployment problems before the final demo block.
Troubleshooting During the Hackathon
MFA prompt blocks progress
Do not retry many times. Show the screen to your tutor so the operations team can reset or verify the method.
Foundry project missing
Confirm the team number. If the project does not appear, the tutor should check the admin dashboard assignment row.
Model call fails
Check endpoint, deployment name, API version, and `.env` loading. Never paste keys into chat or screenshots.
Quota warning
Stop repeated tests, switch to shorter prompts, and ask the tutor to review loops or background calls.
App deployment fails
Keep the local demo and backup screenshots ready while the tutor checks the assigned App Service slot.
Student Account FAQ
Which account should I use?
Use only the KOICA-TIU Azure account assigned by the operations team.
Can teammates share one password?
No. Each student account is individual. Do not share passwords or MFA methods.
Where do I store Azure values?
Store endpoint, deployment name, and keys in `.env`. Commit `.env.example` only.
What happens after the event?
The operations team may disable or clean up team resources after demos and cost review.
Quota Basics
Team budget
Event cap is controlled by the operations team. Each team receives a quota plan before the hackathon.
Model usage
Use low-volume tests during development and reserve longer prompts for the final demo.
App Service
One B1 slot per team by default. Extra apps require admin approval.
Data
Use small public or synthetic data. Do not upload private personal data.
Credit Safety
Protecting the Shared Credit
KOICA-TIU has one annual Azure credit that funds the June hackathon, the second semester AI-901 Foundry labs, and the second hackathon. Six student rules keep that budget healthy for the whole year.
Annual credit
18,000,000 KRW
Shared across both semesters and both hackathons.
June 2026 hackathon
2-3M KRW target
5 teams × 4 members. Per-team cap roughly 600K KRW.
Fall semester Foundry labs
4-5M KRW
Weekly mini-labs from September. Stop rules apply per cohort.
Fall semester hackathon
3-4M KRW
Recalibrated after the June retrospective.
Mock-first
Use mock mode or local stubs while building the UI. Only switch to live Azure calls when you have a working prototype.
Short prompts
Iterate with short test prompts (under 200 tokens) until the flow works. Save longer prompts for the final demo.
Small samples
Use 3-5 sample documents for RAG until the retrieval works. Scale up only after evaluation passes.
Stop idle apps
When you leave the room, stop the App Service slot. Idle B1 slots eat the shared credit even with no traffic.
No background loops
Never leave a polling loop, recursive agent, or auto-retry running. One missed loop can burn a team budget in minutes.
Watch team cap
Each team has a budget cap (~375K KRW for the June hackathon). Ask the tutor if you are unsure of the remaining quota.
If you see a quota warning, do not retry. Stop the call, screenshot the message, and ask your tutor. A single missed background loop has crashed an entire team's budget in past hackathons elsewhere.
Estimate Before You Build
Plug in how many tokens you expect to use for input and output. The simulator returns the KRW cost using the verified gpt-4o-mini planning price.
Cost Simulator
Input price
$0.000165/1K tokens
Output price
$0.00066/1K tokens
Estimated cost
—
—
Default rate 1400 KRW/USD. Adjust either input box to estimate per-call or per-event cost. Hackathon teams typically run 5K-50K tokens per build, 100K-400K tokens for a full day.
Before You Present
- Your project runs in the assigned team scope.
- Your demo does not show secrets.
- Your app has a backup screenshot or recording.
- Your tutor has checked your final demo path.