open/ms-ai-architect
1
0
Fork 0
Code Issues Releases 4 Activity

docs(ms-ai-architect): KB-refresh tema-b — Foundry-navnesveip «Azure AI Foundry»→«Microsoft Foundry» (233 filer)

Browse source 
Verifisert mot offisiell MS-doc (juni 2026): «Microsoft Foundry» er det
gjeldende produkt-/portalnavnet; «Foundry (classic)» = gamle «Azure AI Foundry»
(/azure/foundry/ vs /azure/foundry-classic/). Premiss bekreftet før sveip.

Multi-regel, IKKE naiv s/Azure AI Foundry/Microsoft Foundry/ — MS dropper
«Azure AI» (legger IKKE til «Microsoft») for to produktvarianter:
- «Azure AI Foundry Agent[ Service|s]» → «Foundry Agent Service/Agents» (MS-form)
- «Azure AI Foundry Models» → «Foundry Models» (i «Azure OpenAI in Foundry Models»)
- «Azure AI Foundry SDK» → «Microsoft Foundry SDK» (operatør-valg)
- «Azure AI Foundry portal/project» + generisk → «Microsoft Foundry»
- Pre-eksisterende «Microsoft Foundry Models» (4) normalisert → «Foundry Models»

Bevart: «Azure OpenAI», «Azure AI Inference SDK», «Azure AI Search»,
«Azure AI Services», kode-IDer. Historisk ref «(tidligere Azure AI Foundry)»
i model-catalog-2026.md beskyttet via lookbehind. URL /azure/ai-foundry/→
/azure/foundry/ kun i owasp-llm-top10 (KB-ref); docs/-filer deferred.

Scope: skills (inkl. 3 SKILL.md) + commands + agents + README + CLAUDE.
Ekskludert: docs/ (interne), playground/+tests/ fixtures (testdata),
CHANGELOG.md (historisk logg), STATE.md (gitignored).

3 SKILL.md endret (advisor/engineering/security) → judge-cache teknisk
invalidert for disse, men scorer uendret: advisor 91, eng/gov/infra/sec 96
(alle ≥90). validate 239/0. 0 «Azure AI Foundry» igjen (utenom bevart ref).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-06-23 21:00:27 +02:00
commit 03d596e4ec
233 changed files with 810 additions and 810 deletions
Download patch file Download diff file Expand all files Collapse all files

6
skills/ms-ai-advisor/references/copilot-extensibility/enterprise-governance-copilot-deployment.md
View file

@ -54,7 +54,7 @@ Microsoft anbefaler en tredelt governance-modell basert på risiko og teknisk ko
|------|-------------|---------------|------------|
| **Zone 1: Citizen Development** | Personlige og team-produktivitetsagenter. Read-only, private. Lav risiko. | Agent Builder (M365 Copilot), SharePoint agents | Developer environments med environment routing. Sharing disabled. |
| **Zone 2: Partnered Development** | IT-godkjente makers bygger agents for teams/avdelinger. Moderat risiko. | Copilot Studio | IT-managed environments, review-prosesser, ALM pipelines, scoped roles. |
| **Zone 3: Professional Development** | Mission-critical, enterprise-grade agents. Høy risiko. | Copilot Studio, Azure AI Foundry Agent Service | Strengeste security controls, standard ALM, SLAs, audit trails. |
| **Zone 3: Professional Development** | Mission-critical, enterprise-grade agents. Høy risiko. | Copilot Studio, Foundry Agent Service | Strengeste security controls, standard ALM, SLAs, audit trails. |
**Secure-kontroller per zone:**
- Zone 1: Kun Microsoft 365 og Power Platform connectors. Agents kjører i user context.
@ -511,10 +511,10 @@ Set-CsTeamsCallingPolicy -Identity <policy name> -Copilot EnabledWithTranscript
- Copilot respekterer SharePoint permissions (kun inkluder content user har access til)
- Oversharing blueprint: Pilot → Deploy → Operate phases med SAM og Purview
### Azure AI Foundry
### Microsoft Foundry
**Integration point:**
- Zone 3 (Professional Development) kan bruke Azure AI Foundry Agent Service for mission-critical agents
- Zone 3 (Professional Development) kan bruke Foundry Agent Service for mission-critical agents
- Agents deployes som Azure-tjenester med full Azure governance (RBAC, networking, monitoring)
- Integration med Copilot Studio via custom connectors (agent-to-agent orchestration)