fix(ms-ai-architect): Foundry URL-navnerom-migrering (ai-foundry → foundry/foundry-classic, 141 filer)
Task #5 del 1/3 (URL-migrering). Verifiseringen motbeviste STATE.md-premisset om ren prefix-swap: rebrand er per-URL, ikke mekanisk. En blind sed ai-foundry→foundry ville lagd 56 nye 404-er (classic-stiene finnes ikke under nytt foundry/-prefiks — bekreftet empirisk). Metode: resolverte alle 237 unike KB-URLer mot live redirects (curl -L), bygde full-URL→full-URL-mapping fra faktisk url_effective. Bevarer locale-form, query (?view=) og #fragment per lenke. - 231 navnerom-erstatninger over 141 filer (408 forekomster): - 161 → azure/foundry/ (98 ren prefix-swap + 10 sti-reorg + reorg-tilfeller) - 69 → azure/foundry-classic/ (eldre hub-spor: assistants, hub-DR, on-your-data; faktisk redirect-mål per operatorvalg) - 1 → azure/foundry-local/ - 2 døde lenker (404) fikset til verifiserte mål: - agent-service → azure/foundry/agents/overview - concepts/evaluation-evaluators/ → azure/foundry/how-to/evaluate-generative-ai-app - 5 path-/display-referanser (uten https://, i backticks/lenketekst) rettet manuelt. - 6 slug-baserte ai-foundry-treff urørt (scope-grense): managed-grafana-dashboard, security-baseline, power-platform prompt-builder, architecture baseline-chat (sistnevnte slug-rebrand i annet navnerom — mulig fremtidig funn). - Parkert til task #5 del 2/3: Norway East GPT-5-datasuverenitet-fiks + modellkatalog-utvidelse (5.3/5.4/5.5, gpt-oss, sora-2). Verifisert: 0 gjenværende azure/ai-foundry/-navnerom i skills/. validate-plugin.sh 219 PASS. test-kb-integrity.sh 117/117 passed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01REiKFhP4w6xGXXqWKpPCJJ
This commit is contained in:
parent
84e3cfaa03
commit
dd1036ab8a
141 changed files with 399 additions and 399 deletions
|
|
@ -331,15 +331,15 @@ PTU er en kapasitetsbasert prismodell for Azure OpenAI, primært for produksjons
|
|||
*Sist sjekket: 2026-02*
|
||||
|
||||
2. **Provisioned Throughput Concepts**
|
||||
https://learn.microsoft.com/en-us/azure/ai-foundry/openai/concepts/provisioned-throughput
|
||||
https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/provisioned-throughput
|
||||
*Sist sjekket: 2026-02*
|
||||
|
||||
3. **Provisioned Throughput Onboarding (PTU Cost Management)**
|
||||
https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/provisioned-throughput-onboarding
|
||||
https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/provisioned-throughput-billing
|
||||
*Sist sjekket: 2026-02*
|
||||
|
||||
4. **Plan and Manage Costs for Azure OpenAI**
|
||||
https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/manage-costs
|
||||
https://learn.microsoft.com/en-us/azure/foundry/concepts/manage-costs
|
||||
*Sist sjekket: 2026-02*
|
||||
|
||||
5. **Govern AI Costs (Cloud Adoption Framework)**
|
||||
|
|
@ -374,7 +374,7 @@ PTU er en kapasitetsbasert prismodell for Azure OpenAI, primært for produksjons
|
|||
- microsoft_docs_search: "Azure AI Services reserved capacity commitment tier"
|
||||
- microsoft_docs_search: "Azure AI Services budget management cost estimation"
|
||||
- microsoft_docs_fetch: `/azure/ai-services/commitment-tier`
|
||||
- microsoft_docs_fetch: `/azure/ai-foundry/openai/how-to/manage-costs`
|
||||
- microsoft_docs_fetch: `/azure/foundry/concepts/manage-costs`
|
||||
- microsoft_docs_fetch: `/azure/cloud-adoption-framework/scenarios/ai/platform/governance`
|
||||
- microsoft_docs_search: "Azure OpenAI provisioned throughput PTU cost optimization"
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue