feat(ms-ai-architect): R7.3 KOMPLETT — payload-37/38/39/41/42/43/45/47/48/49 dømt+ingestet (216 claims, 61 flagg; ledger 133→143; R7.3 49/49, 1008 claims, 269 flagg) [skip-docs]
This commit is contained in:
parent
e625645739
commit
1b29e9673a
1 changed files with 843 additions and 1 deletions
|
|
@ -4,7 +4,7 @@
|
|||
"derived_from": "scripts/kb-update/data/full-pass-worklist.json (243 due, all never-verified)",
|
||||
"cadence": "R7–R10 (5 økter × ~49, 8–10 samtidige)",
|
||||
"batch": "R7.1",
|
||||
"count": 133,
|
||||
"count": 143,
|
||||
"generated": "2026-07-18"
|
||||
},
|
||||
"files": [
|
||||
|
|
@ -6156,6 +6156,232 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/streaming-rag-responses.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 17,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/streaming-rag-responses.md#13",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/api-management/forward-request-policy",
|
||||
"evidence_quote": "timeout | The amount of time in seconds to wait for the HTTP response headers to be returned by the backend service before a timeout error is raised. ... | No | 300",
|
||||
"reason": "API Management sin standard backend-timeout er 300 sekunder, ikke 30 — den bærende tallverdien i claimet motsies, og siden advarer i tillegg om at verdier over 240 s kanskje ikke honoreres.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/streaming-rag-responses.md",
|
||||
"line": 274,
|
||||
"claim": "Azure API Management har en standard route timeout på 30 s, som må økes til 300 s+ for SSE-endepunkter.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/streaming-rag-responses.md#14",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/power-automate/limits-and-config",
|
||||
"evidence_quote": "",
|
||||
"reason": "Ingen Learn-side sier at Power Automate mangler native SSE-streaming; limits-siden oppgir kun timeout-grenser (120 s synkront), så påstanden kan verken bekreftes eller motbevises.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/streaming-rag-responses.md",
|
||||
"line": 295,
|
||||
"claim": "Power Automate støtter ikke native SSE-streaming.",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/streaming-rag-responses.md#15",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/microsoft-copilot-studio/mcp-add-existing-server-to-agent",
|
||||
"evidence_quote": "Currently, Copilot Studio supports the Streamable transport type. Given that SSE transport is deprecated, Copilot Studio no longer supports SSE for MCP after August 2025.",
|
||||
"reason": "Den kanoniske siden som teller opp støttede transporter for custom connector-baserte serverkoblinger lister kun Streamable og sier eksplisitt at SSE ikke lenger støttes; ingen Learn-side dokumenterer SSE-streaming for Copilot Studio custom connectors i preview.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/streaming-rag-responses.md",
|
||||
"line": 299,
|
||||
"claim": "Copilot Studio støtter streaming via SSE for custom connectors (preview).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/streaming-rag-responses.md#17",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/semantic-kernel/support/",
|
||||
"evidence_quote": "",
|
||||
"reason": "Kun første del er dekket (Responses-siden krever Azure-abonnement og Foundry-/Azure OpenAI-ressurs); Learn kaller Semantic Kernel open source uten å oppgi MIT, og prisdetaljene for Application Gateway per gateway-time og API Management Consumption-tier ligger på JS-rendrede pricing-sider som ikke kan hentes.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/streaming-rag-responses.md",
|
||||
"line": 369,
|
||||
"claim": "Lisenskrav: Azure OpenAI krever Azure subscription + OpenAI resource | Semantic Kernel er open source (MIT) uten lisenskostnad | Application Gateway faktureres som Azure-kostnad per gateway-time | API Management har per call/måned-tier (Consumption for lavt volum).",
|
||||
"disposition": "unsourced"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 22,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#1",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/vector-search-index-size",
|
||||
"evidence_quote": "Vector optimization techniques are generally available. Use capabilities like narrow data types, scalar and binary quantization, and elimination of redundant storage to reduce your vector quota and storage quota consumption.",
|
||||
"reason": "Hybrid search som GA holder, men den andre lastbærende delen svikter: Learn oppgir scalar quantization som generelt tilgjengelig (GA), ikke preview.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 4,
|
||||
"claim": "Hybrid search i Azure AI Search er GA, mens scalar quantization er i Preview.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#2",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/vector-search-how-to-create-index",
|
||||
"evidence_quote": "vectorSearch.algorithms is either hnsw or exhaustiveKnn. These are the Approximate Nearest Neighbors (ANN) algorithms used to organize vector content during indexing.",
|
||||
"reason": "Den kanoniske opplistingen av vektoralgoritmer nevner kun hnsw og exhaustiveKnn; «Flat indexing (linear scan)» finnes ikke som algoritme i Azure AI Search.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 37,
|
||||
"claim": "Azure AI Search tilbyr vektoralgoritmene Hierarchical NSW (HNSW, approximate nearest neighbor) | Exhaustive KNN (exact nearest neighbor) | Flat indexing (linear scan).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#5",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/hybrid-search-ranking",
|
||||
"evidence_quote": "If you add vector weighting, the initial scores are subject to a weighting multiplier that increases or decreases the score. The default is 1.0, which means no weighting and the initial score is used as-is in RRF scoring.",
|
||||
"reason": "Vekting i hybrid search skjer med RRF og parameteren weight (standard 1.0) — noen alpha-parameter finnes ikke i den kanoniske dokumentasjonen, og top har standardverdi 50, ikke 10 («$top ... This defaults to 50» i Search Documents REST).",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 71,
|
||||
"claim": "Vekting av hybrid scores i Azure AI Search styres av parametrene alpha (balanse mellom vector 1.0 og BM25 0.0, standard 0.5, range 0.0–1.0) | k (antall vektorer fra vector search, standard 50, range 1–1000) | top (totale resultater etter merge, standard 10, range 1–1000).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#8",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/search-limits-quotas-capacity",
|
||||
"evidence_quote": "| Search queries (POST /indexes/{index}/docs/search) | Varies by SU count and query complexity | 50 queries/sec (aggregate read throttle per index) |",
|
||||
"reason": "Den kanoniske throttling-tabellen oppgir ingen grense på 3000 requests per sekund per replika — søkespørringer varierer med antall search units og spørringskompleksitet.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 168,
|
||||
"claim": "Azure AI Search har en rate limit på 3000 requests per sekund per replika.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#9",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/vector-search-how-to-create-index",
|
||||
"evidence_quote": "",
|
||||
"reason": "Learn oppgir at text-embedding-3-large støtter 1 til 3072 dimensjoner (native output 3 072), men ingen side sier at modellen brukes med 1536 dimensjoner i en Azure AI Search-index for standard RAG — verdien er tillatt, men verken bekreftet eller motsagt.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 178,
|
||||
"claim": "Embedding-modellen text-embedding-3-large brukes med 1536 dimensjoner i en Azure AI Search-index for standard RAG.",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#10",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/vector-search-how-to-quantization",
|
||||
"evidence_quote": "Scalar quantization compresses float values into narrower data types. AI Search currently supports int8, which is 8 bits, reducing vector index size fourfold.",
|
||||
"reason": "Scalar quantization reduserer datatypen (float32 til int8), ikke antall dimensjoner: 1536 float32 (6 144 byte) blir 1536 int8 (én firedel), ikke 384 int8 / 384 byte — dimensjonsreduksjon er en separat MRL-funksjon (truncationDimension).",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 235,
|
||||
"claim": "Scalar quantization i Azure AI Search komprimerer vektorer fra 1536 float32 (6 KB) til 384 int8 (384 bytes).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#11",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/vector-search-index-size",
|
||||
"evidence_quote": "Vector optimization techniques are generally available. Use capabilities like narrow data types, scalar and binary quantization, and elimination of redundant storage to reduce your vector quota and storage quota consumption.",
|
||||
"reason": "Scalar quantization er GA (og står ikke i Learn sin liste over preview-funksjoner i Azure AI Search), så statuspåstanden «preview» er motsagt.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 237,
|
||||
"claim": "Scalar quantization er en preview-funksjon i Azure AI Search (2026).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#12",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-azure-ai-search",
|
||||
"evidence_quote": "Select Add knowledge from either the Overview or Knowledge pages, or the Properties of a generative answers node. From the Add knowledge dialog, select Featured. Select Azure AI Search.",
|
||||
"reason": "Den dokumenterte navigasjonen er Add knowledge → Featured → Azure AI Search (alternativt Data sources → Azure AI Search), ikke «Security & Data → Knowledge sources → Add Azure AI Search»; den lastbærende stien er feil.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 318,
|
||||
"claim": "Copilot Studio konfigurerer Azure AI Search som kunnskapskilde for Generative answers via Security & Data → Knowledge sources → Add Azure AI Search, uten kontroll over HNSW-parametere (managed service).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#13",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/connectors/azureaisearch/",
|
||||
"evidence_quote": "| Agentic Search (Preview) | Delete a document | Delete multiple documents | Get index statistics | Get search indexes | Index a document | Index multiple documents | Merge a document | Search vectors | Search vectors with natural language | Semantic Hybrid Search |",
|
||||
"reason": "Den kanoniske opplistingen av handlinger i Azure AI Search-connectoren inneholder ingen handling som heter «Search documents (semantic)» (nærmeste er «Semantic Hybrid Search»), og connectoren stiller ingen krav om et felt ved navn contentVector.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 324,
|
||||
"claim": "AI Builder i Power Automate støtter semantic search via Azure AI Search-connectoren med handlingen «Search documents (semantic)», som krever en index med contentVector-felt.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#16",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R4",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/search-limits-quotas-capacity",
|
||||
"evidence_quote": "| After May 17, 2024 ^2^ | 15 | 160 | 512 | 1,024 | 2,048 | 4,096 | N/A |",
|
||||
"reason": "Lagringstallene 2/25/100/200 GB matcher kun den daterte legacy-raden «Before April 3, 2024»; gjeldende grenser er 15/160/512/1024 GB, og replika-tallene er også feil (Basic 3, S1–S3 12, ikke 1/3/6/12).",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 368,
|
||||
"claim": "Azure AI Search tilbys i tierne Basic (2 GB storage, 3 queries/sek, 1 replica) | S1 (25 GB, 15 queries/sek, 3 replicas) | S2 (100 GB, 60 queries/sek, 6 replicas) | S3 (200 GB, 60 queries/sek, 12 replicas).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#17",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/semantic-how-to-enable-disable",
|
||||
"evidence_quote": "| Free (default) | Provides a monthly free request allowance. After the free allowance is consumed, semantic ranker requests return a billing error. | Available on all pricing tiers. |",
|
||||
"reason": "Gratisplanen for semantic ranker er tilgjengelig på alle pristiers (standardplanen krever Basic eller høyere), ikke bare S1 og oppover, og ingen Learn-side oppgir et gratistak på 50 000 spørringer per måned.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 384,
|
||||
"claim": "Semantic Ranker er inkludert i S1 og høyere tiers, med et gratis usage cap på 50 000 queries per måned.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#18",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq",
|
||||
"evidence_quote": "Licensed by tenant, Microsoft Copilot Studio entitles a tenant to 25,000 messages per month.",
|
||||
"reason": "Lisensen gir 25 000 meldinger per tenant per måned, ikke 20 000.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 385,
|
||||
"claim": "Integrasjon med Copilot Studio krever Copilot Studio-lisens med 20 000 meldinger per måned.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-engineering/rag-architecture/vector-indexing-techniques.md#19",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R7",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/search/vector-search-how-to-create-index",
|
||||
"evidence_quote": "vectorSearch.algorithms.m is the bi-directional link count. Default is 4. The range is 4 to 10.",
|
||||
"reason": "HNSW-parameteren for koblinger heter m, ikke maxConnections — navnet er selve påstanden (lastbærende API-identifikator), så R7 sin leniens for illustrerende tall gjelder ikke, selv om efSearch og \"exhaustive\": true stemmer.",
|
||||
"file": "skills/ms-ai-engineering/references/rag-architecture/vector-indexing-techniques.md",
|
||||
"line": 433,
|
||||
"claim": "I hybrid search-indekser er HNSW standard ANN-algoritme med efSearch og maxConnections som tunbare parametere, mens eKNN (exhaustive K-Nearest Neighbors) gir fullstendig søk og aktiveres med \"exhaustive\": true i spørringen.",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/alerting-strategies-escalation.md",
|
||||
"batch": "R7.1",
|
||||
|
|
@ -6191,6 +6417,89 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/anomaly-detection-ai-systems.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 21,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/anomaly-detection-ai-systems.md#8",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-smart-detections-migration",
|
||||
"evidence_quote": "You can trigger the smart detection migration to alerts for a specific Application Insights resource by using ARM templates.",
|
||||
"reason": "De tre metodene stemmer (portal, Azure CLI, ARM-maler), men den bærende presiseringen «ARM templates for batch-migrering» er motsagt: ARM-malene er scoped til én bestemt ressurs, mens batch («Migrate all Application Insights resources in this subscription» / subscription-scope i CLI-body) er portal- og CLI-veien.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/anomaly-detection-ai-systems.md",
|
||||
"line": 78,
|
||||
"claim": "Migrering av smart detection til alerts kan gjøres på tre måter: Azure Portal (manuell migrering) | Azure CLI med REST API | ARM templates for batch-migrering.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/anomaly-detection-ai-systems.md#16",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/defender-for-cloud/alerts-ai-workloads",
|
||||
"evidence_quote": "Detected credential theft attempts on an Azure AI model deployment ... A Jailbreak attempt on an Azure AI model deployment was blocked by Azure AI Content Safety Prompt Shields ... Corrupted AI application\\model\\data directed a phishing attempt at a user ... Suspected wallet attack - volume anomaly ... Access anomaly in AI resource",
|
||||
"reason": "Den kanoniske alert-oversikten for AI-workloads enumererer langt flere enn tre kategorier og inneholder ingen «Model Inference Anomalies» eller «Data Exfiltration Patterns»; oversiktssiden lister truslene som «data leakage, data poisoning, jailbreak, credential theft, and more», så tre-kategori-taksonomien er ikke Microsofts.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/anomaly-detection-ai-systems.md",
|
||||
"line": 341,
|
||||
"claim": "Microsoft Defender for AI dekker tre AI-spesifikke deteksjonskategorier: Jailbreak Attempt Detection | Model Inference Anomalies | Data Exfiltration Patterns.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/anomaly-detection-ai-systems.md#17",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/templates/microsoft.security/pricings",
|
||||
"evidence_quote": "AIPromptEvidence - Exposes the prompts passed between the user and the AI model as alert evidence ... Available for AI plan. ... pricingTier | Indicates whether the Defender plan is enabled on the selected scope ... 'Free''Standard' (required)",
|
||||
"reason": "Kommandoen az security pricing create og tier Standard stemmer, men planen heter «AI» i API-et (jf. «Available for AI plan», på linje med CloudPosture/Containers/VirtualMachines) — ingen Learn-side navngir en «AIServices»-plan, og plannavnet er nettopp strengen leseren kopierer inn i CLI-kallet.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/anomaly-detection-ai-systems.md",
|
||||
"line": 363,
|
||||
"claim": "Defender for AI aktiveres med az security pricing create, plannavn AIServices og tier Standard.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/anomaly-detection-ai-systems.md#19",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/ai-services/anomaly-detector/overview",
|
||||
"evidence_quote": "We recommend migrating to Microsoft Fabric, which integrates the open-source microsoft/anomaly-detector, or to the open-source anomaly-detector project directly.",
|
||||
"reason": "Den kanoniske siden som ville enumerert alternativene anbefaler Microsoft Fabric eller open source anomaly-detector; ingen av de fire oppgitte alternativene (Azure ML model monitoring, Azure Monitor KQL, Stream Analytics, egne ML-modeller) står der.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/anomaly-detection-ai-systems.md",
|
||||
"line": 374,
|
||||
"claim": "Alternativer etter retirement av Azure AI Anomaly Detector: Azure ML model monitoring | Azure Monitor KQL-baserte funksjoner | Azure Stream Analytics | custom modeller i Azure ML.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/anomaly-detection-ai-systems.md#20",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/fabric/real-time-intelligence/anomaly-detection",
|
||||
"evidence_quote": "A Python plugin enabled on that same Eventhouse ... Select the Python 3.11.7 DL plugin and select Done ... Tests multiple anomaly detection algorithms ... A list of recommended algorithms, ranked by their effectiveness for your data.",
|
||||
"reason": "Eventhouse-Python-plugin-delen stemmer, men den kanoniske RTI-siden (og modell-spesifikasjonssiden, som lister TSB-AD-/MS-utviklede modeller) nevner ikke SimpleDetectAnomalies fra synapse.ml.services — den SynapseML-klassen hører til Spark-notebook-oppskriften i Fabric Data Science mot den utgående Anomaly Detector-tjenesten, ikke Eventhouse-mekanismen.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/anomaly-detection-ai-systems.md",
|
||||
"line": 385,
|
||||
"claim": "Microsoft Fabric Real-Time Intelligence støtter anomaly detection via Python-plugin i Eventhouse med SimpleDetectAnomalies fra synapse.ml.services.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/anomaly-detection-ai-systems.md#21",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R3",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/app/application-insights-faq",
|
||||
"evidence_quote": "Application Insights is billed through the Log Analytics workspace into which its log data ingested. The default Pay-as-you-go Log Analytics pricing tier includes 5 GB per month of free data allowance per billing account.",
|
||||
"reason": "5 GB gratis per måned stemmer, men rammen er feil: fribeløpet ligger i Pay-as-you-go-tieren i Log Analytics, ikke i en «Basic-tier» (Basic Logs er en tabellplan, ikke en tier som gir 5 GB gratis).",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/anomaly-detection-ai-systems.md",
|
||||
"line": 505,
|
||||
"claim": "Application Insights er inkludert i Basic-tier, gratis opp til 5 GB per måned.",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/compliance-monitoring-ai-governance.md",
|
||||
"batch": "R7.3",
|
||||
|
|
@ -6274,6 +6583,195 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/cost-monitoring-cost-attribution.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 20,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/cost-monitoring-cost-attribution.md#3",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/foundry/openai/how-to/fine-tuning-deploy",
|
||||
"evidence_quote": "After you deploy a customized model, if at any time the deployment remains inactive for more than 15 days, the deployment is deleted. ... The deletion of an inactive deployment doesn't delete or affect the underlying customized model.",
|
||||
"reason": "15-dagers automatisk sletting gjelder utelukkende distribusjoner av tilpassede (finjusterte) modeller — påstanden utvider regelen til Azure OpenAI-deployments generelt, og den bærende avgrensningen er dermed feil.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/cost-monitoring-cost-attribution.md",
|
||||
"line": 56,
|
||||
"claim": "Azure OpenAI-deployments som har vært inaktive i 15 dager slettes automatisk, mens den underliggende modellen bevares.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/cost-monitoring-cost-attribution.md#15",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/power-bi/connect-data/refresh-data",
|
||||
"evidence_quote": "you can configure up to eight daily time slots if your semantic model is on shared capacity, or 48 time slots on Power BI Premium",
|
||||
"reason": "Planlagt/automatisk oppdatering krever ikke Premium — delt kapasitet gir opptil åtte daglige oppdateringer (Premium hever kun taket til 48), og Cost Management-dokumentasjonen stiller ingen Premium-betingelse for eksportert kostnadsdata eller deling.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/cost-monitoring-cost-attribution.md",
|
||||
"line": 305,
|
||||
"claim": "Power BI Premium kreves for å aktivere automatisk oppdatering (automatic refresh) og deling med stakeholders av eksportert kostnadsdata.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/cost-monitoring-cost-attribution.md#16",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R7",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/foundry/openai/monitor-openai-reference",
|
||||
"evidence_quote": "Generated Completion Tokens Number of tokens generated (output) from an OpenAI model. Applies to PTU, PTU-managed and Pay-as-you-go deployments. | GeneratedTokens",
|
||||
"reason": "Den kanoniske metrikk-katalogen for Microsoft.CognitiveServices/accounts inneholder ingen metrikk TokensGenerated; utgangstokens heter GeneratedTokens (og OutputTokens under Models - Usage), så det bærende strengnavnet er feil.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/cost-monitoring-cost-attribution.md",
|
||||
"line": 320,
|
||||
"claim": "Azure OpenAI-deployments eksponerer metrikken TokensGenerated, som kan hentes med Get-AzMetric.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/cost-monitoring-cost-attribution.md#17",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/foundry/concepts/manage-costs",
|
||||
"evidence_quote": "",
|
||||
"reason": "Verken den siterte siden eller eksportdokumentasjonen oppgir regioner for lagring av kostnadsdata — de sier kun at data eksporteres til en lagringskonto du velger, så Norway East/Norway West kan verken bekreftes eller motbevises.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/cost-monitoring-cost-attribution.md",
|
||||
"line": 338,
|
||||
"claim": "Cost data kan lagres i de norske Azure-regionene Norway East og Norway West.",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/cost-monitoring-cost-attribution.md#18",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/foundry/openai/concepts/provisioned-throughput-billing",
|
||||
"evidence_quote": "Provisioned deployments (Regional, Data Zone, and Global) are charged at an hourly rate ($/PTU/hr) based on the number of PTUs deployed. ... you're billed hourly based on the number of Provisioned Throughput Units (PTUs) you deploy, rather than the number of tokens consumed.",
|
||||
"reason": "PTU faktureres per time på antall distribuerte PTU-er (med valgfri reservasjon som rabattmekanisme), ikke som fast månedlig kostnad målt i TPM/RPM — den månedlige Commitment-modellen er stengt for nye kunder, så den bærende prismodell-beskrivelsen er utdatert.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/cost-monitoring-cost-attribution.md",
|
||||
"line": 392,
|
||||
"claim": "Azure OpenAI tilbyr to prismodeller: PTU (Provisioned Throughput Units — fast månedlig kostnad med garantert throughput målt i TPM/RPM) | Pay-as-you-go (betaling kun for faktisk forbruk).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/cost-monitoring-cost-attribution.md#20",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/api-management/plan-manage-costs",
|
||||
"evidence_quote": "For example, a unit of the Basic tier has an estimated maximum throughput of approximately 1,000 requests per second. ... For example, two units of the Standard tier provide an estimated throughput of approximately 2,000 requests per second.",
|
||||
"reason": "Basic 1 000 req/s stemmer, men siden angir ca. 1 000 req/s per Standard-enhet (to enheter gir ca. 2 000), ikke 2 500; Consumption skaleres automatisk uten publisert req/s-tall, og Premium-tallet finnes ikke på Learn — én bærende verdi er dermed motsagt.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/cost-monitoring-cost-attribution.md",
|
||||
"line": 415,
|
||||
"claim": "Maksimal throughput per Azure API Management-tier: Consumption 1000 req/sek | Basic 1000 req/sek | Standard 2500 req/sek | Premium 4000 req/sek.",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/custom-dashboards-ai-operations.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 17,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/custom-dashboards-ai-operations.md#2",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/foundry-classic/how-to/monitor-applications",
|
||||
"evidence_quote": "These views bring key metrics - token consumption, latency, exceptions, response quality - into a single pane that provides transparency to teams.",
|
||||
"reason": "Foundrys workbook sporer token consumption/latency/exceptions/response quality, mens claimens «total conversations», «tool usage» og «topic analytics» er Copilot Studio Dashboard-metrikker — flere bærende deler er tilskrevet feil produkt.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/custom-dashboards-ai-operations.md",
|
||||
"line": 46,
|
||||
"claim": "Microsoft Foundrys out-of-box workbook sporer: Generative AI metrics (total conversations | latency | exceptions) | Tool usage (hvilke extensions og tools brukes mest) | Topic analytics (hvilke conversation topics dominerer) | Operational health (success rates | error patterns | response times).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/custom-dashboards-ai-operations.md#12",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/power-bi/connect-data/desktop-data-sources",
|
||||
"evidence_quote": "The Azure category provides the following data connections: Azure SQL Database, Azure Synapse Analytics SQL, Azure Analysis Services database, Azure Database for PostgreSQL, Azure Blob Storage, Azure Table Storage, Azure Cosmos DB v1, Azure Data Explorer (Kusto), Azure Data Lake Storage Gen2, Azure HDInsight (HDFS), Azure HDInsight Spark, HDInsight Interactive Query, Microsoft Cost Management, Azure Resource Graph, Azure HDInsight on AKS Trino (Beta), Azure Cosmos DB v2, Azure Databricks, Azure Synapse Analytics workspace (Beta)",
|
||||
"reason": "Den kanoniske konnektorlisten for Get Data → Azure i Power BI Desktop inneholder ingen «Azure Monitor Logs»-konnektor; den siterte siden dokumenterer i stedet eksport som M-query eller nytt Dataset.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/custom-dashboards-ai-operations.md",
|
||||
"line": 194,
|
||||
"claim": "Power BI Desktop har en Azure Monitor Logs-konnektor tilgjengelig via Get Data → Azure → Azure Monitor Logs.",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/data-residency-audit-monitoring.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 25,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/data-residency-audit-monitoring.md#2",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R4",
|
||||
"evidence_url": "https://learn.microsoft.com/purview/audit-solutions-overview",
|
||||
"evidence_quote": "The default retention period for Audit (Standard) changed from 90 days to 180 days. Audit (Standard) logs generated before October 17, 2023, are retained for 90 days. Audit (Standard) logs generated on or after October 17, 2023, follow the new default retention of 180 days.",
|
||||
"reason": "Claimet treffer kun den historiske raden (før 17. oktober 2023); gjeldende default for Audit (Standard) er 180 dager, ikke 90 — den lastbærende delen er utdatert selv om Premium-delen om retention policies stemmer.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/data-residency-audit-monitoring.md",
|
||||
"line": 38,
|
||||
"claim": "Microsoft Purview Audit Standard har 90 dagers retention som default, mens Premium gir konfigurerbare retention policies.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/data-residency-audit-monitoring.md#5",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/purview/audit-solutions-overview",
|
||||
"evidence_quote": "The following table compares the key capabilities available in Audit (Standard) and Audit (Premium). ... Up to 1-year audit log retention | 10-year audit log retention | Audit log retention policies | Intelligent insights",
|
||||
"reason": "Den kanoniske sammenligningstabellen som ville enumerert forskjellene mellom nivåene inneholder ingen compliance-sertifiseringer i det hele tatt — verken ISO 27001/SOC for Standard eller FedRAMP/«GDPR-optimalisert» som Premium-tillegg; sertifiseringer gjelder tjenesten, ikke SKU-nivået.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/data-residency-audit-monitoring.md",
|
||||
"line": 41,
|
||||
"claim": "Microsoft Purview Audit Standard dekker ISO 27001 | SOC 1/2/3, mens Premium i tillegg dekker FedRAMP | GDPR-optimalisert.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/data-residency-audit-monitoring.md#15",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-purview-service-description",
|
||||
"evidence_quote": "Which licenses provide the rights for a user to benefit from the service? Microsoft 365 E5/A5/G5/E3/A3/G3, Microsoft 365 Business Premium, SharePoint Online Plan 2, OneDrive for Business (Plan 2), Exchange Online Plan 2; Office 365 E5/A5/G5/E3/A3/G3; Microsoft Purview Suite/EDU/GOV/FLW",
|
||||
"reason": "Lisenskravet i claimet er for høyt: den kanoniske lisenstabellen gir DLP-rettigheter også med E3/A3/G3 (og Business Premium), og DLP-aktiviteter logges i unified audit log som er Audit (Standard) — det finnes ingen E5/G5-terskel slik claimet påstår.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/data-residency-audit-monitoring.md",
|
||||
"line": 196,
|
||||
"claim": "Microsoft Purview DLP med audit krever E5/G5-lisensiering eller Purview standalone.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/data-residency-audit-monitoring.md#18",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/purview/audit-copilot",
|
||||
"evidence_quote": "Pay-as-you-go billing doesn't apply to Microsoft applications. All Microsoft applications, including Microsoft Copilots like Microsoft Security Copilot, Copilot in Microsoft Fabric, and custom applications built using Microsoft Copilot Studio and Microsoft Foundry are included in Audit Standard.",
|
||||
"reason": "Nivået er feil: Copilot Studio-interaksjoner logges under Audit (Standard), ikke Premium, og «alle» holder ikke — Purview-siden for Copilot Studio krever pay-as-you-go for agenter publisert til ikke-Microsoft-kanaler.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/data-residency-audit-monitoring.md",
|
||||
"line": 274,
|
||||
"claim": "Purview Audit Premium logger alle agent-interaksjoner i Copilot Studio.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/data-residency-audit-monitoring.md#22",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R3",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/azure-monitor/logs/logs-table-overview",
|
||||
"evidence_quote": "Interactive retention | The period during which data is available for queries, alerts, and other Azure Monitor features. Interactive retention ranges from 4 to 730 days for Analytics tables, and is fixed at 30 days for Basic and Auxiliary tables. Long-term retention | A low-cost extension that keeps data in your workspace",
|
||||
"reason": "Rammeverket er erstattet: gjeldende modell har to retention-stadier (Interactive 4–730 dager for Analytics, fast 30 dager for Basic/Auxiliary, og Long-term retention opptil 12 år) — ikke «Interactive 0-31 dager | Basic 31 dager til 2 år | Archive 2+ år», og Basic er et table plan, ikke et retention-nivå.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/data-residency-audit-monitoring.md",
|
||||
"line": 414,
|
||||
"claim": "Azure Monitor Log Analytics har retention-nivåene Interactive 0-31 dager (default) | Basic 31 dager til 2 år | Archive 2+ år.",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/distributed-tracing-ai-pipelines.md",
|
||||
"batch": "R7.3",
|
||||
|
|
@ -6333,6 +6831,77 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/endpoint-health-and-capacity-planning.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 25,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/endpoint-health-and-capacity-planning.md#5",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/foundry/openai/how-to/quota",
|
||||
"evidence_quote": "Quota is allocated in terms of units of capacity, which have corresponding amounts of RPM & TPM: | Older chat models | 1 Unit | 6 RPM | 1,000 TPM |",
|
||||
"reason": "Tier-oppregningen (Free Tier / Tier 0 og Tier 1–6) er nøyaktig grunnet i quotas-limits (Seven tiers ... Free Tier and Tiers 1 through 6), men den løftebærende negasjonen «ikke via 1 Unit Capacity» motsies: gjeldende quota-side allokerer fortsatt kvote i units of capacity og advarer om feilallokering ved programmatisk deployment.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/endpoint-health-and-capacity-planning.md",
|
||||
"line": 55,
|
||||
"claim": "Kvote for Azure OpenAI tildeles via Quota Tiers — Free Tier (Tier 0) | Tier 1 | Tier 2 | Tier 3 | Tier 4 | Tier 5 | Tier 6 — ikke via «1 Unit Capacity».",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/endpoint-health-and-capacity-planning.md#6",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/foundry/openai/how-to/quota",
|
||||
"evidence_quote": "| Model | Capacity | Requests Per Minute (RPM) | Tokens Per Minute (TPM) | ... | Older chat models | 1 Unit | 6 RPM | 1,000 TPM | ... | o1 & o1-preview | 1 Unit | 1 RPM | 6,000 TPM | ... | o3 | 1 Unit | 1 RPM | 1,000 TPM | ... | o3-mini | 1 Unit | 1 RPM | 10,000 TPM |",
|
||||
"reason": "Alle fire forholdstallene står i kilden som «1 Unit» Capacity-rater, ikke som Tier 1/GlobalStandard-verdier; i Tier 1-tabellen på quotas-limits finnes verken eldre chat-modeller, o1-preview eller o1-mini under GlobalStandard, og ingen GlobalStandard-rad der har forholdet 6 RPM per 1 000 TPM — den stadfestede scope-angivelsen er dermed feil.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/endpoint-health-and-capacity-planning.md",
|
||||
"line": 59,
|
||||
"claim": "For Tier 1 og GlobalStandard er RPM/TPM-forholdet modellspesifikt: eldre chat-modeller 6 RPM / 1,000 TPM | o1 og o1-preview 1 RPM / 6,000 TPM | o3 1 RPM / 1,000 TPM | o3-mini og o1-mini 1 RPM / 10,000 TPM.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/endpoint-health-and-capacity-planning.md#14",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/provisioned-throughput",
|
||||
"evidence_quote": "Provisioned deployments support two billing modes: hourly billing for flexible, short-term usage, and Azure Reservations for sustained production workloads at a discounted rate. ... All provisioned deployment types are billed at an hourly rate ($/PTU/hr) based on the number of PTUs deployed ... In exchange for a 1-month or 1-year commitment, you receive a discounted effective $/PTU/hr rate.",
|
||||
"reason": "Varighetene 1 måned/1 år er riktige, men de gjelder frivillige Azure Reservations; PTU faktureres som standard per time uten commitment, så den løftebærende delen «krever commitment» motsies av kilden.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/endpoint-health-and-capacity-planning.md",
|
||||
"line": 199,
|
||||
"claim": "PTU (Provisioned Throughput) krever commitment på 1 måned eller 1 år.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/endpoint-health-and-capacity-planning.md#18",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/deployment-types",
|
||||
"evidence_quote": "Data residency for all deployment types: Data stored at rest remains in the designated Azure geography. However, inferencing data is processed as follows: Global types: May be processed in any Azure region; DataZone types: The service processes data only within the Microsoft-specified data zone (US, EU, or Asia Pacific (APAC)); Standard/Regional types: Processed in the deployment region",
|
||||
"reason": "Påstanden om at databehandling for Azure OpenAI skjer i EU er ubetinget, mens kilden gjør prosesseringssted avhengig av deployment-type — for Global-typer kan data behandles i hvilken som helst Azure-region, altså utenfor EU.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/endpoint-health-and-capacity-planning.md",
|
||||
"line": 454,
|
||||
"claim": "Databehandling for Azure OpenAI skjer i EU, selv om kontrollplanet er globalt.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/endpoint-health-and-capacity-planning.md#19",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/quick-create-workspace",
|
||||
"evidence_quote": "You need Microsoft.OperationalInsights/workspaces/write permissions to the resource group where you want to create the Log Analytics workspace, as provided by the Log Analytics Contributor built-in role, for example.",
|
||||
"reason": "Kilden krever ikke Owner eller Contributor for å opprette Log Analytics workspace — den smalere rollen Log Analytics Contributor er tilstrekkelig (Microsoft dokumenterer eksplisitt at dette er narrower than a full Contributor role), så den løftebærende rollepåstanden er feil.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/endpoint-health-and-capacity-planning.md",
|
||||
"line": 477,
|
||||
"claim": "Azure Monitor er inkludert i Azure-abonnementet uten separat lisens, og oppsett av Log Analytics workspace krever Owner- eller Contributor-rolle.",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/log-analytics-kql-ai-queries.md",
|
||||
"batch": "R7.3",
|
||||
|
|
@ -6368,6 +6937,279 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/model-performance-drift-detection.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 23,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/model-performance-drift-detection.md#1",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/machine-learning/concept-model-monitoring?view=azureml-api-2",
|
||||
"evidence_quote": "Model performance: Classification (preview) | Tracks the objective performance of a model's output in production by comparing it to collected ground truth data. | Accuracy, Precision, and Recall",
|
||||
"reason": "Kilden merker både Model performance: Classification og Model performance: Regression som (preview) (og Feature attribution drift som (preview)), så den løftebærende GA-delen av påstanden er motsagt selv om data drift, prediction drift og data quality ikke er preview-merket.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/model-performance-drift-detection.md",
|
||||
"line": 4,
|
||||
"claim": "Model performance monitoring og drift detection i Azure Machine Learning er GA (generelt tilgjengelig).",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/model-performance-drift-detection.md#20",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/foundry/concepts/observability",
|
||||
"evidence_quote": "",
|
||||
"reason": "Den siterte observability-siden sier ingenting om regionvalg for Azure ML, og fallback-søk fant ingen learn.microsoft.com-side som opplister regiontilgjengelighet for Azure ML produksjonsdata eller monitoring jobs (den kanoniske listen ligger på azure.microsoft.com), så påstanden kan verken bekreftes eller motbevises.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/model-performance-drift-detection.md",
|
||||
"line": 281,
|
||||
"claim": "Azure-regioner innenfor EU/EØS som kan velges for produksjonsdata og monitoring jobs inkluderer Norway East | Sweden Central | France Central.",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/model-performance-drift-detection.md#21",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/foundry/concepts/observability",
|
||||
"evidence_quote": "",
|
||||
"reason": "Verken den siterte siden eller fallback-søk gir en learn.microsoft.com-side som oppgir lisensierings- eller kjøpsformer for Azure Machine Learning; dette er prisinformasjon som ligger utenfor Learn.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/model-performance-drift-detection.md",
|
||||
"line": 323,
|
||||
"claim": "Azure Machine Learning lisensieres via Enterprise Agreement eller Pay-As-You-Go.",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/model-performance-drift-detection.md#22",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/ai-foundry/concepts/evaluation-regions-limits-virtual-network",
|
||||
"evidence_quote": "These regions support the following safety evaluators: Hate and unfairness, Sexual, Violent, Self-harm, Indirect attack, Code vulnerabilities, and Ungrounded attributes. | Americas | Europe | Asia Pacific | | East US 2 | France Central | Australia East | | North Central US | Sweden Central | | | | Switzerland West | |",
|
||||
"reason": "Den kanoniske regionlisten for risk and safety evaluators inneholder East US 2, North Central US, France Central, Sweden Central, Switzerland West og Australia East - UK South står ikke i listen, så den påståtte regionen mangler i den enumererende kilden.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/model-performance-drift-detection.md",
|
||||
"line": 325,
|
||||
"claim": "Microsoft Foundry safety evaluations er hostet i East US 2 | France Central | UK South | Sweden Central.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/model-performance-drift-detection.md#23",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R4",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/machine-learning/how-to-monitor-datasets?view=azureml-api-1",
|
||||
"evidence_quote": "Data drift (preview) was retired on September 1, 2025. Migrate to Model Monitor for your data drift tasks.",
|
||||
"reason": "Legacy-stemplingen og migreringen til Model Monitor stemmer, men gjeldende status er at funksjonen allerede ble pensjonert 1. september 2025 - ikke at den er under utfasing - så statusdelen av påstanden er superseded.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/model-performance-drift-detection.md",
|
||||
"line": 393,
|
||||
"claim": "Den eldre dataset-baserte data drift monitoring i Azure ML (azureml-api-1) er legacy og under utfasing, med migrering til Model Monitor.",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 22,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/observability-for-copilot-extensions.md#1",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/microsoft-cloud/dev/copilot/isv/observability-for-ai",
|
||||
"evidence_quote": "",
|
||||
"reason": "Påstanden gjelder referansefilens egen statusmerking (GA per 2026-05); ingen learn.microsoft.com-side uttaler seg om statusen til dette KB-dokumentet, og den siterte ISV-veiledningen bærer verken GA- eller preview-merking.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"line": 4,
|
||||
"claim": "Referansen for observability for Copilot-extensions er merket med status GA (per 2026-05).",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/observability-for-copilot-extensions.md#3",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/microsoft-cloud/dev/copilot/isv/observability-for-ai",
|
||||
"evidence_quote": "",
|
||||
"reason": "Den siterte ISV-observabilitetssiden inneholder ingen fem-lags telemetri-inndeling med verktøytilordning (den strukturerer stoffet i tre livssyklusfaser og metrikk-kategorier), og søk finner ingen annen Learn-side som angir denne taksonomien; enkeltkoblingene er dokumentert hver for seg, men selve fem-lags-framingen står ingen steder.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"line": 39,
|
||||
"claim": "Telemetri for Copilot-extensions deles i fem lag med tilhørende verktøy: Copilot Studio Agent → Application Insights | Plugin/Connector Runtime → Application Insights SDK | LLM Interaction → Azure OpenAI metrics | User Engagement → Custom events | Security/Compliance → Microsoft Sentinel, Purview.",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/observability-for-copilot-extensions.md#4",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-bot-framework-composer-capture-telemetry",
|
||||
"evidence_quote": "Enable logging: If turned on, the system logs details of incoming and outgoing messages and events. Log conversation details: Includes user ID, user name, and message text (for Message activities). Log sensitive Activity properties: If turned on, the logs include the values of certain properties that could be considered sensitive on incoming and outgoing messages and events. Node execution events: Log an event each time a node within a topic is executed.",
|
||||
"reason": "Settings → Advanced → Connection string stemmer, men den kanoniske siden lister fire valgfrie innstillinger (Enable logging, Log conversation details, Log sensitive Activity properties, Node execution events) — verken «Log activities» eller «Log custom telemetry events» finnes, så to av tre påståtte innstillingsnavn er fraværende.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"line": 50,
|
||||
"claim": "Application Insights konfigureres i Copilot Studio under Settings → Advanced med en Connection string, og har tre valgfrie innstillinger: Log activities | Log sensitive Activity properties | Log custom telemetry events.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/observability-for-copilot-extensions.md#5",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R2",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-bot-framework-composer-capture-telemetry",
|
||||
"evidence_quote": "Log sensitive Activity properties: If turned on, the logs include the values of certain properties that could be considered sensitive on incoming and outgoing messages and events.",
|
||||
"reason": "Den kanoniske siden enumererer ingen egenskaper for «Log sensitive Activity properties», og tilordner tvert imot user ID, user name og message text til den separate innstillingen «Log conversation details» — påstandens liste userid/name/text/speak står ikke der.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"line": 52,
|
||||
"claim": "Innstillingen «Log sensitive Activity properties» i Copilot Studio logger egenskapene userid | name | text | speak.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/observability-for-copilot-extensions.md#13",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R7",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-logging-copilot-studio",
|
||||
"evidence_quote": "| Agents | BotCreate | The creation of a new agent in Copilot Studio | ... | Agents | BotUpdateOperation-BotPublish | Publishing of an agent in Copilot Studio | | Agents | BotUpdateOperation-BotShare | Sharing of an agent to other users in Copilot Studio |",
|
||||
"reason": "Den kanoniske Purview-enumerasjonen navngir hendelsene BotUpdateOperation-BotPublish og BotUpdateOperation-BotShare, ikke BotPublish/BotShare; event-label er en lastebærende streng en leser filtrerer på, så to av tre navn er feil selv om BotCreate og M365-lisenskravet stemmer.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"line": 224,
|
||||
"claim": "Purview-revisjonslogger dekker Copilot Studio-hendelsene BotCreate | BotPublish | BotShare, og revisjonslogging må aktiveres for Microsoft 365-lisensinnehavere.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/observability-for-copilot-extensions.md#16",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/azure-monitor/app/application-insights-faq",
|
||||
"evidence_quote": "Raw data retention can be set to 30, 60, 90, 120, 180, 270, 365, 550, or 730 days. Retention beyond 90 days can incur extra charges. ... Data is stored in the region you choose when creating the resource.",
|
||||
"reason": "Learn dokumenterer at dataplassering bestemmes av regionen du velger ved opprettelse av ressursen, mens Settings → Data retention styrer oppbevaringstid — påstanden tilordner data residency til feil mekanisme.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"line": 253,
|
||||
"claim": "Data Residency aktiveres i Application Insights under Settings → Data retention.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/observability-for-copilot-extensions.md#19",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R3",
|
||||
"evidence_url": "https://learn.microsoft.com/microsoft-copilot-studio/requirements-sessions-management",
|
||||
"evidence_quote": "This section is for billed sessions in the legacy Power Virtual Agents license, which was available for purchase starting on December 1, 2023. This legacy license is no longer available for purchase starting on January 1, 2024.",
|
||||
"reason": "Lisensrammen påstanden bygger på er erstattet: Power Virtual Agents-lisensen er merket legacy og ikke kjøpbar etter 1. januar 2024, og dagens modell er Copilot Studio-lisens/Copilot Credits-kapasitet (analyse er dessuten tilgjengelig via Teams-planen i M365-lisenser).",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"line": 304,
|
||||
"claim": "Innebygd Copilot Studio-analyse krever Power Virtual Agents-lisens eller Copilot Studio-kapasitet.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/observability-for-copilot-extensions.md#21",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/azure/sentinel/sentinel-overview",
|
||||
"evidence_quote": "Microsoft Sentinel SIEM is available in the Microsoft Defender portal - for customers with or without Defender XDR or an E5 license - offering a unified security operations experience.",
|
||||
"reason": "Learn sier eksplisitt at Sentinel er tilgjengelig uten E5-lisens (og faktureres på forbruk, ikke som «standalone»-lisens), mens Copilot Studio-veiledningen bare krever «an assigned Microsoft 365 license» — det lastebærende E5-kravet er motsagt.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/observability-for-copilot-extensions.md",
|
||||
"line": 306,
|
||||
"claim": "Microsoft Sentinel for revisjonslogger krever Microsoft 365 E5 eller Sentinel standalone.",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/real-time-streaming-monitoring.md",
|
||||
"batch": "R7.3",
|
||||
"judged_at": "2026-07-25",
|
||||
"per_file_verdict": "flagged",
|
||||
"claim_count": 24,
|
||||
"verified": null,
|
||||
"verified_by": null,
|
||||
"flags": [
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/real-time-streaming-monitoring.md#14",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-ingestion-time",
|
||||
"evidence_quote": "The average latency to ingest log data is less than 10 seconds.",
|
||||
"reason": "Azure Monitor oppgir gjennomsnittlig ingestion-latency til under 10 sekunder og prosesstid under 10 sekunder, ikke en iboende latency på 1-5 minutter.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/real-time-streaming-monitoring.md",
|
||||
"line": 92,
|
||||
"claim": "Application Insights og Log Analytics har en iboende ingestion-latency på 1-5 minutter.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/real-time-streaming-monitoring.md#15",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/fabric/real-time-intelligence/dashboard-live-refresh",
|
||||
"evidence_quote": "",
|
||||
"reason": "Refresh-innstillingene dokumenterer Refresh rate limit som minste tidsintervall mellom oppdateringer, men verken denne siden eller create-dashboard-siden oppgir noen 10-sekunders minimumsverdi.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/real-time-streaming-monitoring.md",
|
||||
"line": 110,
|
||||
"claim": "Minimum auto-refresh-intervall for Fabric Real-Time Dashboard er 10 sekunder.",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/real-time-streaming-monitoring.md#19",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/fabric/admin/region-availability",
|
||||
"evidence_quote": "Europe | Norway West | ✅ | ❌ | Power BI only region",
|
||||
"reason": "Norway East har alle Fabric-workloads, men Norway West er en Power BI only-region uten Fabric-workloads, så Fabric-kapasitet med eventhouse kan ikke velges der; én bærende del av påstanden er feil (R8).",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/real-time-streaming-monitoring.md",
|
||||
"line": 340,
|
||||
"claim": "Fabric-kapasitet med eventhouse kan velges i Norway East/West for datasuverenitet.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/real-time-streaming-monitoring.md#20",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/app/connection-strings",
|
||||
"evidence_quote": "Customized endpoints (sovereign or hybrid cloud environments): Endpoint settings allow sending data to a specific Azure Government region.",
|
||||
"reason": "Endepunktet live.applicationinsights.azure.com hører riktig nok til public cloud, men samme side lister applicationinsights.us som gyldig suffiks og live som prefiks for Live Metrics, altså er Live Metrics tilgjengelig i Azure Government; andre bærende del er feil (R8).",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/real-time-streaming-monitoring.md",
|
||||
"line": 345,
|
||||
"claim": "Live Metrics-endepunktet live.applicationinsights.azure.com hostes i Azure public cloud, og Live Metrics er ikke tilgjengelig i Azure Government.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/real-time-streaming-monitoring.md#21",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R8",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview",
|
||||
"evidence_quote": "Managed identities can be used at no extra cost.",
|
||||
"reason": "Forutsetningene for Entra-autentisering i Application Insights er managed identity eller service principal pluss Monitoring Metrics Publisher-rollen, uten noe lisenskrav, og managed identities koster ingenting ekstra; SKU-delen om Entra ID P1/P2 er derfor feil selv om september 2025-kravet stemmer (R8).",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/real-time-streaming-monitoring.md",
|
||||
"line": 381,
|
||||
"claim": "Entra ID-autentisering for Live Metrics er inkludert i Entra ID P1/P2 og er påkrevd fra september 2025.",
|
||||
"disposition": "outdated"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/real-time-streaming-monitoring.md#22",
|
||||
"judge_verdict": "source_silent",
|
||||
"rule": "",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/fabric/real-time-intelligence/real-time-dashboards-overview",
|
||||
"evidence_quote": "",
|
||||
"reason": "Verken dashboard-oversikten, lisenssiden eller RTI-forbrukssidene sier at Real-Time Dashboard er inkludert i kapasiteten uten ekstra kostnad; forbruk måles i CU per operasjon, så påstanden kan verken bekreftes eller motbevises.",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/real-time-streaming-monitoring.md",
|
||||
"line": 391,
|
||||
"claim": "Real-Time Dashboard er inkludert i Fabric-kapasiteten uten ekstra kostnad.",
|
||||
"disposition": "unsourced"
|
||||
},
|
||||
{
|
||||
"id": "ms-ai-governance/monitoring-observability/real-time-streaming-monitoring.md#23",
|
||||
"judge_verdict": "not_grounded",
|
||||
"rule": "R3",
|
||||
"evidence_url": "https://learn.microsoft.com/en-us/fabric/real-time-intelligence/data-activator/activator-capacity-usage",
|
||||
"evidence_quote": "Similar to other workloads in Fabric, Activator billing is based on the consumption of resources. Fabric uses Capacity Units (CU) to measure and bill for resource usage.",
|
||||
"reason": "Activator faktureres som CU-forbruk på Fabric-kapasiteten med publiserte satser (rule uptime per hour 0.02222, event ingestion, event computations, storage), ikke som egen SKU per reflex med uannonsert preview-prising; både rammeverket og TBA-statusen er erstattet (R3).",
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/real-time-streaming-monitoring.md",
|
||||
"line": 394,
|
||||
"claim": "Data Activator faktureres som egen SKU per reflex/trigger, med preview-prising ikke annonsert (TBA).",
|
||||
"disposition": "outdated"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"file": "skills/ms-ai-governance/references/monitoring-observability/security-and-audit-logging-ai.md",
|
||||
"batch": "R7.1",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue