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-engineering/references/agent-orchestration/agent-to-agent-communication.md

@@ -1,6 +1,6 @@
 # Agent-to-Agent Communication Protocols
 
-**Last updated:** 2026-02
+**Last updated:** 2026-04 | Verified: MCP 2026-04
 **Status:** GA
 **Category:** Agent Orchestration & Automation
 
@@ -237,8 +237,14 @@ eventBus.Subscribe<AgentCompletedEvent>(async evt =>
 
 | Topologi | Beskrivelse | Use Case |
 |----------|-------------|----------|
-| **Broker Topology** | Agenter broadcaster events, andre agenter reagerer eller ignorerer | Dynamiske workflows, ingen sentral koordinering |
-| **Mediator Topology** | En mediator styrer event flow og state | Komplekse workflows med error handling og state management |
+| **Broker Topology** | Agenter broadcaster events, andre agenter reagerer eller ignorerer. Hoey dekobling, men mangler innebygd error handling og distributed transaction-stoette | Dynamiske workflows, ingen sentral koordinering |
+| **Mediator Topology** | En mediator styrer event flow og state, dispatcher commands til dedikerte kanaler. Bedre feilhaandtering og datakonsistens, men oekt kobling og potensielt bottleneck | Komplekse workflows med error handling og state management |
+
+**Event-driven utfordringer ved agent-kommunikasjon:**
+- **Eventual consistency:** Data paa tvers av agenter er ikke umiddelbart konsistent. Design for dette bevisst.
+- **Ordering:** Ved skalering kan events motttas i feil rekkefoelge. Bruk partisjonsnoekler og idempotent processing.
+- **Observability:** Inkluder correlation ID i alle events fra start — retrofit er vanskelig.
+- **Schema evolution:** Definer versjonsstrategi tidlig. Design consumers til aa haandtere ukjente event-versjoner.
 
 **Når brukes dette:**
 - Lang-levende workflows (timer/dager)
@@ -538,7 +544,7 @@ Trenger dere agent discovery?
 
 4. **Event-Driven Architecture (Azure)**
    - https://learn.microsoft.com/en-us/azure/architecture/guide/architecture-styles/event-driven
-   - Confidence: **Verified** (Azure Architecture Center, 2024)
+   - Confidence: **Verified** (Azure Architecture Center, oppdatert 2026-04: broker vs mediator topology, eventual consistency, ordering, observability, schema evolution)
 
 5. **Azure Service Bus Integration**
    - https://learn.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/integration-event-based-microservice-communications