docs(architect): weekly KB update — 52 files refreshed (2026-04)
Key content changes: - MLOps: MLflow 3 scorers expanded (RetrievalRelevance, Fluency, multi-turn judges) - MLflow 3 A/B eval: mirror_traffic GA confirmed, new scorer catalog - CI/CD: OIDC auth replaces deprecated --sdk-auth (Azure ML GitHub Actions) - Agent framework A2A: updated SDK patterns (A2ACardResolver, BearerAuth) - AG-UI backend tool rendering: accurate TOOL_CALL_* event shapes - Computer Use agents: US region requirement, credentials patterns - Purview governance: bulk term edit, expire/delete workflows - CAF AI Secure: 3-phase structure confirmed current - Copilot Studio: Claude Sonnet 4.5/4.6 GA, new orchestration controls - M365 manifest: v1.26 GA (April 2026), copilotAgents node - Power Platform: agent flow capacity enforcement corrected - Azure Monitor: Simple Log Alerts GA, AMBA for policy-based alerting - Security Copilot: SCU capacity model (400 SCU/1000 users) - EU Data Boundary: all EU + EFTA countries confirmed - gateway-multi-backend: added 4th topology, subscription-level quota note Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen
parent
ff6a50d14f
commit
34c6db36fa
40 changed files with 398 additions and 239 deletions
|
|
@ -389,7 +389,7 @@ Connection pooling har spesielle hensyn for norsk offentlig sektor:
|
|||
- [Guidelines for using HttpClient](https://learn.microsoft.com/dotnet/fundamentals/networking/http/httpclient-guidelines) — HttpClient best practices
|
||||
- [Pool HTTP connections with HttpClientFactory](https://learn.microsoft.com/aspnet/core/performance/performance-best-practices) — ASP.NET performance
|
||||
- [Manage connections in Azure Functions](https://learn.microsoft.com/azure/azure-functions/manage-connections) — Serverless connection management
|
||||
- [Use a gateway in front of multiple Azure OpenAI deployments](https://learn.microsoft.com/azure/architecture/ai-ml/guide/azure-openai-gateway-multi-backend) — Multi-backend gateway patterns
|
||||
- [Use a gateway in front of multiple Azure OpenAI deployments or instances](https://learn.microsoft.com/azure/architecture/ai-ml/guide/azure-openai-gateway-multi-backend) — Multi-backend gateway patterns (Azure OpenAI i Foundry Models) — Verified (MCP 2026-04)
|
||||
|
||||
## For Cosmo
|
||||
|
||||
|
|
|
|||
|
|
@ -405,8 +405,10 @@ Microsoft dokumenterer multi-backend gateway som den anbefalte arkitekturmønste
|
|||
|
||||
### Anbefalte topologier for rate limit-distribusjon
|
||||
|
||||
> **Viktig:** Standard-kvote er subscription-nivå, ikke Azure OpenAI-instansnivå. Load balancing mellom standard-instanser i samme subscription gir IKKE høyere gjennomstrømning — bruk separate subscriptions eller global/data zone deployments for reell kvoteutvidelse. — Verified (MCP 2026-04)
|
||||
|
||||
| Topologi | Kvote-kapasitet | Kompleksitet | Anbefalt for |
|
||||
|----------|----------------|--------------|--------------|
|
||||
|----------|----------------|--------------|------------|
|
||||
| Single instance | Baseline TPM | Lav | Utvikling, lav trafikk |
|
||||
| Multi-backend, single region | 2-5x baseline | Medium | Produksjon, standard |
|
||||
| Multi-subscription | 5-20x baseline | Høy | Høy trafikk enterprise |
|
||||
|
|
@ -475,7 +477,7 @@ Microsoft dokumenterer multi-backend gateway som den anbefalte arkitekturmønste
|
|||
- [Manage Azure OpenAI quota](https://learn.microsoft.com/azure/ai-foundry/openai/how-to/quota) — Kvotehåndtering
|
||||
- [Azure OpenAI quotas and limits](https://learn.microsoft.com/azure/ai-foundry/openai/quotas-limits) — Grenser per modell
|
||||
- [Azure OpenAI SDK retry handling](https://learn.microsoft.com/azure/ai-foundry/openai/supported-languages) — SDK retry-konfigurasjon
|
||||
- [Use a gateway in front of Azure OpenAI](https://learn.microsoft.com/azure/architecture/ai-ml/guide/azure-openai-gateway-multi-backend) — Multi-region gateway
|
||||
- [Use a gateway in front of multiple Azure OpenAI deployments or instances](https://learn.microsoft.com/azure/architecture/ai-ml/guide/azure-openai-gateway-multi-backend) — Multi-region gateway (Azure OpenAI i Foundry Models) — Verified (MCP 2026-04)
|
||||
|
||||
## For Cosmo
|
||||
|
||||
|
|
|
|||
|
|
@ -28,6 +28,8 @@ Latensforskjellen mellom regioner kan være betydelig: en forespørsel fra Oslo
|
|||
|
||||
### Deployment-typer og regionvalg
|
||||
|
||||
> **Anbefaling (Verified MCP 2026-04):** Hvis du ikke trenger å begrense databehandling til én bestemt region, bruk **Global** eller **Data Zone**-deployments for å utnytte Azures globale infrastruktur til dynamisk ruting til datasentre med ledig kapasitet — fremfor å bygge kompleks multi-region gateway-logikk.
|
||||
|
||||
| Deployment Type | Data Location | Routing | Bruksområde |
|
||||
|----------------|---------------|---------|-------------|
|
||||
| Global Standard | Any Azure region | Automatisk til ledig kapasitet | Høyest tilgjengelighet, lavest kostnad |
|
||||
|
|
@ -394,7 +396,7 @@ Microsoft dokumenterer nå fire formelle topologier for Azure OpenAI gateway:
|
|||
|
||||
## Referanser
|
||||
|
||||
- [Use a gateway for multi-backend Azure OpenAI](https://learn.microsoft.com/azure/architecture/ai-ml/guide/azure-openai-gateway-multi-backend) — Multi-region patterns
|
||||
- [Use a gateway in front of multiple Azure OpenAI deployments or instances](https://learn.microsoft.com/azure/architecture/ai-ml/guide/azure-openai-gateway-multi-backend) — Multi-region patterns (Azure OpenAI i Foundry Models) — Verified (MCP 2026-04)
|
||||
- [Azure Front Door](https://learn.microsoft.com/azure/frontdoor/front-door-overview) — Global load balancing
|
||||
- [APIM multi-region deployment](https://learn.microsoft.com/azure/api-management/api-management-howto-deploy-multi-region) — Regional gateway
|
||||
- [Azure OpenAI deployment types](https://learn.microsoft.com/azure/ai-foundry/openai/how-to/deployment-types) — Global vs Regional
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue