docs(architect): weekly KB update — 106 files refreshed (2026-04)

Updates across all 5 skills: ms-ai-advisor, ms-ai-engineering,
ms-ai-governance, ms-ai-security, ms-ai-infrastructure.

Key changes:
- Language Services (Custom Text Classification, Text Analytics, QnA):
  retirement warning 2029-03-31, migration guides to Foundry/GPT-4o
- Agentic Retrieval: 50M free reasoning tokens/month (Public Preview)
- Computer Use: Claude Sonnet 4.5 (preview) + OpenAI CUA models
- Agent Registry: Risks column (M365 E7), user-shared/org-published types
- Declarative agents: schema v1.5 → v1.6, Store validation requirements
- MLflow 3: 13 built-in LLM judges, production monitoring, Genie Code
- AG-UI HITL: ApprovalRequiredAIFunction (C#) + @tool(approval_mode) (Python)
- Entra ID Ignite 2025: Agent ID Admin/Developer RBAC roles, Conditional Access
- Security Copilot: 400 SCU/month per 1000 M365 E5 licenses, auto-provisioned
- Fast Transcription API: phrase lists, 14-language multi-lingual transcription
- Azure Monitor Workbooks: Bicep support, RBAC specifics
- Power Platform Copilot: data residency (Norway/Europe → EU DB, Bing → USA)
- RAG security-rbac: 4-approach table (GA + 3 preview access control methods)
- IaC MLOps: Well-Architected OE:05 principles, Bicep/Terraform patterns
- Translator: image file batch translation Preview (JPEG/PNG/BMP/WebP)

All 106 files: Last updated 2026-04 | Verified: MCP 2026-04

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

skills/ms-ai-advisor/references/prompt-engineering/error-handling-and-fallback-prompting.md

@@ -1,6 +1,6 @@
 # Error Handling and Fallback Prompting Strategies
 
-**Last updated:** 2026-02
+**Last updated:** 2026-04 | Verified: MCP 2026-04
 **Status:** GA
 **Category:** Prompt Engineering & LLM Optimization
 
@@ -374,10 +374,20 @@ APIM kan enforces content safety checks automatisk:
 </policies>
 ```
 
+**Policy-attributter (Verified MCP 2026-04):**
+- `backend-id`: Azure AI Content Safety backend i APIM
+- `shield-prompt`: Sjekk for brukerangrep/adversarial prompts (true/false)
+- `enforce-on-completions`: Aktiver content safety på responser i tillegg til requests
+- `window-size`: Tegn per vindu for evaluering (maks 10 000 tegn, konfigurerbart for responser)
+- `output-type`: FourSeverityLevels (0,2,4,6) eller EightSeverityLevels (0-7)
+- Threshold 0 = mest restriktivt, 7 = minst restriktivt. Threshold 4 blokkerer nivå 4-7, tillater 0-3.
+- Støtter også `blocklists` for tilpassede ord/uttrykk
+
 **Fordeler:**
-- Sentralisert content safety enforcement
-- Automatisk blokkering av requester som matcher attack patterns
+- Sentralisert content safety enforcement på API-lag
+- Automatisk blokkering (HTTP 403) av requester som matcher attack patterns
 - Ingen endringer nødvendig i applikasjonskode
+- Fungerer for streaming responses (buffer-basert sliding window)
 
 ### Azure Monitor + Action Groups for Automated Healing
 
@@ -680,7 +690,7 @@ User Request
 2. [Architecture strategies for self-preservation](https://learn.microsoft.com/en-us/azure/well-architected/reliability/self-preservation) – Azure Well-Architected Framework reliability-mønstre
 3. [Azure OpenAI Priority-Based Load Balancer (GitHub)](https://github.com/Azure-Samples/openai-aca-lb) – Referanseimplementasjon av smart load balancing
 4. [Troubleshooting Azure OpenAI On Your Data](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/on-your-data-best-practices) – Best practices for debugging og error handling
-5. [llm-content-safety policy (APIM)](https://learn.microsoft.com/en-us/azure/api-management/llm-content-safety-policy) – Content safety enforcement i API Management
+5. [llm-content-safety policy (APIM)](https://learn.microsoft.com/en-us/azure/api-management/llm-content-safety-policy) (Re-verified MCP 2026-04) – Content safety enforcement i API Management. Policy-attributter: backend-id, shield-prompt, enforce-on-completions, window-size, output-type, threshold (0-7), blocklists.
 
 **Sekundærkilder:**
 6. [Azure OpenAI FAQ](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/faq) – Vanlige feilsituasjoner og workarounds
@@ -690,7 +700,7 @@ User Request
 **Verifisert:** Alle tekniske detaljer er hentet fra offisielle Microsoft-kilder (learn.microsoft.com, GitHub samples). Kodeeksempler er basert på offisielle SDK-dokumentasjon (januar 2026).
 
 **Confidence markers:**
-- **Høy confidence:** HTTP error codes, SDK retry defaults, `Retry-After` header, content safety policies
+- **Høy confidence:** HTTP error codes, SDK retry defaults, `Retry-After` header, content safety policies (re-verified MCP 2026-04)
 - **Medium confidence:** Kostnadsestimater (prisene kan variere), spesifikke PTU-priser for norske kunder
 - **Lav confidence:** N/A – alle anbefalinger er basert på etablerte mønstre