Microsoft Azure Webjobs Extensions Authentication Events Dotnet
microsoft/skills
Microsoft Entra Authentication Events SDK for .NET. An agent skill from microsoft/skills.
Diagnose and fix incomplete local development setup. An agent skill from microsoft-foundry/foundry-agent-webapp.
Install Validating Local Setup
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp validating-local-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/validating-local-setup .claude/skills/validating-local-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "validating-local-setup" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/validating-local-setup into .claude/skills/validating-local-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validating-local-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/validating-local-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp validating-local-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/validating-local-setup .agents/skills/validating-local-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "validating-local-setup" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/validating-local-setup into .agents/skills/validating-local-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validating-local-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp validating-local-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/validating-local-setup .cursor/skills/validating-local-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "validating-local-setup" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/validating-local-setup into .cursor/skills/validating-local-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validating-local-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft-foundry/foundry-agent-webapp.git --path .github/skills/validating-local-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp validating-local-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/validating-local-setup .gemini/skills/validating-local-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "validating-local-setup" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/validating-local-setup into .gemini/skills/validating-local-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validating-local-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft-foundry/foundry-agent-webapp validating-local-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/validating-local-setup .github/skills/validating-local-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "validating-local-setup" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/validating-local-setup into .github/skills/validating-local-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validating-local-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp validating-local-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/validating-local-setup .opencode/skills/validating-local-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "validating-local-setup" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/validating-local-setup into .opencode/skills/validating-local-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validating-local-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
validating-local-setup- GitHub stars
- 127
- Token cost
- ~1.2k tokens
- SKILL.md length
- 500 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose and fix incomplete local development setup. An agent skill from microsoft-foundry/foundry-agent-webapp.
- Works in 5 steps: Check current state → If no .azure/ directory (never ran azd) → If .azure/ exists but env files missing… → …
- Dev servers fail to start
- SKILL.md covers Portal vs azd up — What Each…, Quick Diagnostic, What azd up Creates and Required Environment Variables, plus 3 more sections
- Calls pwsh, dotnet and npm
What it does
Validating Local Setup is an agent skill from microsoft-foundry/foundry-agent-webapp. Diagnose and fix incomplete local development setup. Use when dev servers fail to start, env vars are missing, authentication errors occur, or before running any dev commands for the first time.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Authentication. It works with Microsoft Azure and Microsoft Entra ID. The repository describes itself as: GitHub Copilot enabled repo for building and deploying a web application with Entra ID authentication and integrated with Azure AI Foundry Agents. The licence is MIT.
When your agent uses it
- Dev servers fail to start
- Env vars are missing
- Authentication errors occur
- Before running any dev commands for the first time
Example prompts
- “/validating-local-setup”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Check current state
- If no .azure/ directory (never ran azd)
- If .azure/ exists but env files missing (partial setup)
- If env files exist but vars are wrong (stale config)
- Restart dev servers after any fix — env vars are read at startup.
What it can do on your machine
Read from SKILL.md and the folder at commit f6cb362. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pwshdotnetnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Validating Local Setup loads about 1.2k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 500 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:18
al** | Agent endpoint + agent ID | Root `.env` (or manual `azd env set`) | - NoteMentions a .env fileSKILL.md:19
ration, RBAC, infrastructure | `frontend/.env.local` + `backend/WebApp.Api/.env` | - NoteMentions a .env fileSKILL.md:31
This checks for `frontend/.env.local` and `backend/WebApp.Api/.env` with the core authentication variables. For a full l - NoteMentions a .env fileSKILL.md:39
SPA authentication (MSAL.js) | `frontend/.env.local` | - NoteMentions a .env fileSKILL.md:40
T token validation | `backend/WebApp.Api/.env` | - NoteMentions a .env fileSKILL.md:41
ontainer Apps, ACR, RBAC | `.azure/<env>/.env` | - NoteMentions a .env fileSKILL.md:48
### Frontend (`frontend/.env.local`) - NoteMentions a .env fileSKILL.md:56
### Backend (`backend/WebApp.Api/.env`) - NoteMentions a .env fileSKILL.md:73
es the Entra app and generates `frontend/.env.local`. - NoteMentions a .env fileSKILL.md:84
tion failing — check `backend/WebApp.Api/.env`.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from microsoft-foundry/foundry-agent-webapp at commit f6cb362, republished under its MIT licence (© microsoft-foundry). 500 words, ~1,209 tokens.
Download SKILL.mdSave it as
.claude/skills/validating-local-setup/SKILL.md (or your agent's skills folder).- name
- validating-local-setup
- description
- Diagnose and fix incomplete local development setup. Use when dev servers fail to start, env vars are missing, authentication errors occur, or before running any dev commands for the first time.
Local Setup Validation
Portal vs azd up — What Each Provides
The AI Foundry portal's "View sample app code" gives you AI resource variables (AI_AGENT_ENDPOINT, AI_AGENT_ID), which identify your agent. However, this app also needs an Entra ID app registration for user authentication — which only azd up creates. Both sets of config are required.
| Source | What It Provides | Config It Generates |
|---|---|---|
| AI Foundry portal | Agent endpoint + agent ID | Root .env (or manual azd env set) |
azd up | Entra app registration, RBAC, infrastructure | frontend/.env.local + backend/WebApp.Api/.env |
If you came from the portal, paste those values and run azd up — it detects them and incorporates them automatically.
Quick Diagnostic
Run the validation script to check all configuration:
pwsh -File deployment/scripts/validate-config.ps1This checks for frontend/.env.local and backend/WebApp.Api/.env with the core authentication variables. For a full list of required variables, see the tables below.
What azd up Creates
This app requires azd up before local development works. Here's what it provisions:
| What | Why | Generated File |
|---|---|---|
| Entra ID app registration | SPA authentication (MSAL.js) | frontend/.env.local |
| Backend auth config | JWT token validation | backend/WebApp.Api/.env |
| Azure infrastructure | Container Apps, ACR, RBAC | .azure/<env>/.env |
| Redirect URIs | Login callback URLs | Entra app registration |
Even if AI Foundry resources already exist (e.g., from the portal "View sample app code" flow), azd up is still required to create the Entra app registration.
Required Environment Variables
Frontend (frontend/.env.local)
| Variable | Source | Required |
|---|---|---|
VITE_ENTRA_SPA_CLIENT_ID | Entra app registration (created by azd up) | Yes |
VITE_ENTRA_TENANT_ID | Azure AD tenant | Yes |
VITE_ENTRA_BACKEND_CLIENT_ID | Backend app registration (OBO mode only) | No |
Backend (backend/WebApp.Api/.env)
| Variable | Source | Required |
|---|---|---|
AzureAd__TenantId | Azure AD tenant | Yes |
AzureAd__ClientId | Entra app registration | Yes |
AzureAd__Audience | api://{ClientId} | Yes |
AI_AGENT_ENDPOINT | AI Foundry project endpoint | Yes |
AI_AGENT_ID | Agent name in Foundry | Yes |
Common Error Patterns
"undefined" in login URL
login.microsoftonline.com/undefined/oauth2/v2.0/authorize?client_id=undefinedCause: VITE_ENTRA_SPA_CLIENT_ID and VITE_ENTRA_TENANT_ID not set.
Fix: Run azd up — this creates the Entra app and generates frontend/.env.local.
AADSTS900023: Specified tenant identifier is neither a valid DNS name
Cause: Same as above — tenant ID is undefined or empty.
Fix: Run azd up.
Show full SKILL.md (199 more words)Show less
Frontend shows "Setup Required" error page
Cause: The Vite env check plugin detected missing environment variables.
Fix: Run azd up, then restart the dev server.
401 Unauthorized on /api/* endpoints
Cause: Backend JWT validation failing — check backend/WebApp.Api/.env.
Fix: Ensure AzureAd__ClientId matches the Entra app registration. Run azd provision to regenerate.
ManagedIdentityCredential error in local dev
Cause: Backend trying to use managed identity locally.
Fix: Set ASPNETCORE_ENVIRONMENT=Development — local dev uses ChainedTokenCredential(AzureCliCredential, AzureDeveloperCliCredential) instead.
Step-by-Step Fix for Incomplete Setup
Check current state:
powershell pwsh -File deployment/scripts/validate-config.ps1If no
.azure/directory (never ran azd):powershell azd upIf
.azure/exists but env files missing (partial setup):powershell azd provision # Re-creates Entra app + generates .env filesIf env files exist but vars are wrong (stale config):
powershell azd provision # Regenerates everythingRestart dev servers after any fix — env vars are read at startup.
For Agents: Before Running Dev Commands
Before executing dotnet watch run, npm run dev, or start-local-dev.ps1:
- Check if
frontend/.env.localexists - Check if
backend/WebApp.Api/.envexists - If either is missing, tell the user to run
azd upfirst - Do NOT try to create these files manually — they contain auto-generated Entra app registration IDs
© microsoft-foundry, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/validating-local-setup of microsoft-foundry/foundry-agent-webapp.
Open the folder on GitHubat commit f6cb362
Compare with similar skills
Validating Local Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Validating Local Setup this skillmicrosoft-foundry/foundry-agent-webapp | 127 | — | ~1.2k | Automated safety check: Notes | MIT | |
| Microsoft Azure Webjobs Extensions Authentication Events Dotnetmicrosoft/skills | 3.1k | 5 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Entra App Registrationmicrosoft/GitHub-Copilot-for-Azure | 255 | 2 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Iam Auditbriiirussell/cybersecurity-skills | 412 | — | ~3.1k | Automated safety check: Notes | MIT | |
| Auditing Azure Active Directory Configurationmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Azure Identity Pymicrosoft/skills | 3.1k | — | ~4.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Entra App Registration
microsoft/GitHub-Copilot-for-Azure
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration.
Iam Audit
briiirussell/cybersecurity-skills
Audit, design, and migrate Identity and Access Management — cloud provider IAM (AWS, GCP, Azure), identity providers (Okta, Entra ID / Azure AD, Auth0, Google Workspace), application authorization…
Auditing Azure Active Directory Configuration
mukul975/Anthropic-Cybersecurity-Skills
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest…
- Official
Azure Identity Py
microsoft/skills
Azure Identity SDK for Python authentication with Microsoft Entra ID.
Apex Entra App Registration
jonathan-vella/apex
WORKFLOW SKILL — Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration.
More from microsoft-foundry/foundry-agent-webapp
All 19 skills in this repoCommitting Code
microsoft-foundry/foundry-agent-webapp
Provides commit message format and workflow for this repository.
Implementing Chat Streaming
microsoft-foundry/foundry-agent-webapp
Provides SSE streaming patterns for the chat API and frontend.
Planning Features
microsoft-foundry/foundry-agent-webapp
Provides structured plan template for feature implementation.
Researching Azure AI SDK
microsoft-foundry/foundry-agent-webapp
Provides research patterns for Foundry Agent Service SDK. An agent skill from microsoft-foundry/foundry-agent-webapp.
Deploying To Azure
microsoft-foundry/foundry-agent-webapp
Provides deployment commands and troubleshooting for Azure Container Apps.
Syncing MCP Servers
microsoft-foundry/foundry-agent-webapp
Synchronize MCP server configuration between VS Code (.vscode/mcp.json) and Copilot CLI (~/.copilot/mcp-config.json).
Related
Works with
Categories
Questions about Validating Local Setup
What does Validating Local Setup do?
Diagnose and fix incomplete local development setup. An agent skill from microsoft-foundry/foundry-agent-webapp. Validating Local Setup is an agent skill from microsoft-foundry/foundry-agent-webapp. Diagnose and fix incomplete local development setup.
When should I use Validating Local Setup?
Validating Local Setup fits situations like: dev servers fail to start; env vars are missing; authentication errors occur; before running any dev commands for the first time.
How do I install Validating Local Setup in Claude Code?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a claude-code`. Or copy the skill folder (.github/skills/validating-local-setup in microsoft-foundry/foundry-agent-webapp) into .claude/skills/validating-local-setup in your project. Claude Code loads it when a task matches its description.
How do I install Validating Local Setup in Codex?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a codex`. Or copy the skill folder (.github/skills/validating-local-setup in microsoft-foundry/foundry-agent-webapp) into .agents/skills/validating-local-setup in your project. Codex loads it when a task matches its description.
Can I use Validating Local Setup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft-foundry/foundry-agent-webapp --skill validating-local-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validating-local-setup, .gemini/skills/validating-local-setup, .github/skills/validating-local-setup and .opencode/skills/validating-local-setup in your project.
What does Validating Local Setup need to run?
Going by SKILL.md and its folder, Validating Local Setup needs the command-line tools its instructions call (pwsh, dotnet and npm).
Does Validating Local Setup access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Validating Local Setup safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Validating Local Setup use?
Validating Local Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Validating Local Setup use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Validating Local Setup?
Skills that share tags, products or a category with Validating Local Setup: Microsoft Azure Webjobs Extensions Authentication Events Dotnet (microsoft/skills, 3.1k stars), Entra App Registration (microsoft/GitHub-Copilot-for-Azure, 255 stars), Iam Audit (briiirussell/cybersecurity-skills, 412 stars) and Auditing Azure Active Directory Configuration (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Validating Local Setup?
microsoft-foundry (a GitHub organization) maintains it in microsoft-foundry/foundry-agent-webapp, which has 127 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on April 21, 2026.
Source: microsoft-foundry/foundry-agent-webapp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.