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-security/references/performance-scalability/connection-pooling-patterns.md

@@ -1,6 +1,6 @@
 # Connection Pooling Patterns
 
-**Last updated:** 2026-02
+**Last updated:** 2026-04 | Verified: MCP 2026-04
 **Status:** GA
 **Category:** Performance & Scalability
 
@@ -314,6 +314,56 @@ class ConnectionPoolLoadBalancer:
         raise Exception("All backends exhausted")
 ```
 
+
+## Azure API Management som Connection Pooling-lag (oppdatert 2026-04)
+
+APIM håndterer backend connection pooling mot Azure OpenAI, noe som avlaster klientsiden:
+
+### APIM Backend Pool-konfigurasjon
+
+```xml
+<!-- APIM: Backend pool med automatisk connection management -->
+<policies>
+    <inbound>
+        <base />
+        <!-- APIM gjenbruker backend-connections automatisk via intern pool -->
+        <!-- Klientene ser APIM som et enkelt endepunkt -->
+        <set-backend-service id="aoai-pool" backend-id="aoai-norway-backend" />
+        
+        <!-- Legg til correlation ID for tracing -->
+        <set-header name="x-correlation-id" exists-action="skip">
+            <value>@(context.RequestId)</value>
+        </set-header>
+    </inbound>
+    
+    <backend>
+        <retry condition="@(context.Response.StatusCode == 429 || context.Response.StatusCode >= 500)"
+               count="3" interval="0" first-fast-retry="true">
+            <!-- APIM håndterer retry mot backend-pool -->
+            <forward-request timeout="120" />
+        </retry>
+    </backend>
+    
+    <outbound>
+        <!-- Eksponer backend latens-metrikk til klient -->
+        <set-header name="x-backend-latency-ms" exists-action="override">
+            <value>@(context.Elapsed.TotalMilliseconds.ToString())</value>
+        </set-header>
+    </outbound>
+</policies>
+```
+
+### Backend-konfigurasjoner i APIM (4 topologier)
+
+Microsoft anbefaler disse mønstrene for APIM connection pooling mot Azure OpenAI:
+
+1. **Single backend**: Én APIM → én Azure OpenAI (enkelt, begrenset kvote)
+2. **Multi-backend single region**: APIM med weighted round-robin mellom Azure OpenAI-instanser
+3. **Multi-subscription**: Separate Azure OpenAI-instanser i ulike subscriptions for kvote-skalering
+4. **Multi-region**: APIM i flere regioner, each med regionale backends
+
+Klientene trenger aldri kjenne til antallet backends — APIM håndterer routing transparent.
+
 ## Norsk offentlig sektor
 
 Connection pooling har spesielle hensyn for norsk offentlig sektor: