ms-ai-architect/skills/ms-ai-governance/references/responsible-ai/transparency-documentation-standards.md

Transparency and Documentation - Regulatory and Best Practice Standards

Last updated: 2026-06-19 Status: GA / Preview (Responsible AI scorecard) Category: Responsible AI & Governance Type: reference Source: https://learn.microsoft.com/azure/machine-learning/concept-responsible-ai

---

Innhold

• Introduksjon
• Kjernekomponenter
• Arkitekturmønstre
• Beslutningsveiledning
• Integrasjon med Microsoft-stakken
• Offentlig sektor (Norge)
• Kostnad og lisensiering
• For arkitekten (Cosmo)
• Kilder og verifisering

Introduksjon

Transparency and documentation er sentrale prinsipper i Microsofts Responsible AI Standard og krav i emerging regulations som EU AI Act. Dokumentasjon av AI-systemer omfatter både interne governance-verktøy og brukervendte disclosure-mekanismer. Microsoft tilbyr standardiserte rammeverk for å dokumentere AI-kapabiliteter, begrensninger og sikkerhetstiltak gjennom Transparency Notes, model cards, datasheets og Responsible AI scorecards.

Transparency handler ikke bare om teknisk eksportabilitet (model interpretability), men også om organisatorisk accountability — dokumentasjon av design-beslutninger, risk assessments, testing-prosedyrer og ongoing monitoring. Dette sikrer både compliance og stakeholder trust.

Nøkkelkonsepter:

• Transparency Notes: Microsofts standardformat for AI system-dokumentasjon
• Model Cards: Kortfattet beskrivelse av modellens capabilities, limitations og intended use
• Responsible AI Scorecard: PDF-rapport for multi-stakeholder alignment
• Documentation-first approach: Dokumentere before deployment, monitor during operation

---

Kjernekomponenter

1. Transparency Notes (Microsoft Standard)

Microsofts offisielle dokumentasjonsformat for AI-systemer, designet for å forklare hvordan teknologien fungerer og hva organisasjoner må vurdere.

Komponent	Innhold	Målgruppe
What is a Transparency Note?	Definisjon av systemets omfang — teknologi, brukere, påvirkede personer, miljø	Alle stakeholders
The basics of [system name]	Hvordan systemet fungerer, key terms, grunnleggende capabilities	Tekniske og ikke-tekniske
Capabilities	Hva systemet kan gjøre (konkrete use cases)	Product owners, utviklere
Limitations	Technical limitations, operational factors, edge cases	Risk officers, utviklere
System performance	Best practices for tuning, evaluation, measurement	ML professionals
Evaluating and integrating	Guidance for responsible deployment	Decision-makers
Learn more about responsible AI	Lenker til prinsipper, ressurser, training	Compliance teams

Eksempel fra Azure OpenAI Transparency Note:

• Beskriver model weights, ungrounded content, agentic systems som key terms
• Detaljerer GPT-4, DALL-E 3, Whisper capabilities separat
• Warnings om Computer Use preview security risks
• Best practices for content filters, prompt engineering, human review

Confidence: Verified (MCP: microsoft-learn)

---

2. Model Cards og Datasheets

Strukturerte metadatabeskrivelser av AI-modeller og datasets. Originating fra akademisk forskning (Mitchell et al. 2019), adoptert av industry som standard practice.

Model Card komponenter:

Seksjon	Detaljer
Model details	Navn, versjon, eier, lisens, training data source
Intended use	Primary use cases, out-of-scope use cases
Factors	Demographic eller contextual factors som påvirker performance
Metrics	Accuracy, fairness metrics, validation methodology
Evaluation data	Datasets brukt for testing, data splits
Training data	Data sources, preprocessing, filtering
Quantitative analyses	Performance across subgroups og scenarios
Ethical considerations	Kjente risker, biases, mitigation-strategier
Caveats and recommendations	Usage warnings, update-frekvens

Microsoft implementasjon:

• Microsoft Foundry: Model catalog med built-in model cards for pretrained models
• Hugging Face integration: Model cards synces automatisk
• Custom models: Template for å generere egne model cards

Datasheet komponenter:

• Motivation: Hvorfor ble datasettet samlet?
• Composition: Hva er i datasettet? (instances, labels, features)
• Collection process: Hvordan ble data anskaffet?
• Preprocessing: Cleaning, filtering, transformations
• Uses: Intended tasks, prohibited uses
• Distribution: Licensing, update-schedule
• Maintenance: Hvem opprettholder datasettet?

Confidence: Verified (MCP + Baseline)

---

3. Responsible AI Scorecard

PDF-rapport designet for å dele modell- og data-innsikter mellom tekniske og ikke-tekniske stakeholders, spesielt for auditability og compliance.

Primære brukstilfeller:

Rolle	Bruk av Scorecard
Data scientists	Ekstrahere insights fra Responsible AI dashboard for deployment approval
Product managers	Sette target performance/fairness metrics og verifisere at modellen møter dem
Risk officers	Dele modell- og data-innsikter for auditability, slik AI-regelverk krever
Auditors	Arkiverte scorecards i Azure ML Run History for retrospective review

Komponenter i Scorecard:

1. Summary / model overview: Modelloversikt og de target-verdiene du har satt
2. Fairness insights: Hvor godt modellen møter fairness-målverdiene du har satt for de sensitive gruppene du velger
3. Top important factors: Faktorene som påvirker modellens prediksjoner mest
4. Causal insights: Causal vs correlational relationships i features
5. Data analysis: Karakteristikker ved dataene dine
6. Model performance: Modellens viktigste metrikker og prediksjonskarakteristikker, målt mot target values du har satt
7. Cohorts: Best og dårligst presterende datakohorter og subgrupper, automatisk uttrukket av scorecard-en

Ikke scorecard-segmenter: Error analysis og Counterfactual analysis er komponenter i Responsible AI dashboard, ikke segmenter i scorecard-PDF-en. Scorecard-en eksporterer innsikter fra dashboard-et, men de to komponentene har ingen egne segmenter i PDF-rapporten.

Customization:

• Target values: Ytelsesmetrikkene du velger (inntil tre) med målverdier — f.eks. target accuracy og target error rate — pluss målverdi på fairness-metrikken du velger
• Cohort analysis: Modellytelsen på de underliggende kohortene for de features of interest du velger, og over-/underrepresentasjon i datasettet
• Scorecard summary: Tittel og en valgfri fritekstbeskrivelse av modellens funksjonalitet, dataene den er trent og evaluert på, og arkitekturtype

Status: Public preview (Azure ML) — leveres uten SLA, og Microsoft anbefaler den ikke for production workloads.

Confidence: Verified (MCP: microsoft-learn, 2026-08-09)

---

4. Governance Documentation Requirements

Microsoft Responsible AI Standard krever dokumentasjon på flere nivåer av AI lifecycle:

Pre-deployment:

Fase	Dokumentasjonskrav
Impact Assessment	Dokumentere goals, requirements, practices for each Responsible AI principle
Risk discovery	Red teaming reports, bias testing results, safety evaluations
Model selection	Justification for model choice, alignment med risk tolerance
Data vetting	Datasheet for training data, sensitivity classification
Third-party tools	Vetting-report for external APIs/SDKs, security/compliance review

Post-deployment:

Fase	Dokumentasjonskrav
Monitoring	Performance dashboards, drift detection thresholds, retraining triggers
Incident response	Escalation paths, shutdown authorities, user notification procedures
Audit trails	Decision logs, approval workflows, configuration changes
Transparency reports	Public disclosure av AI usage, incident statistics, improvements

Template tilgjengelig: Microsoft Responsible AI Standard v2 (juni 2022) inneholder checklists og templates for Impact Assessments.

Confidence: Verified (MCP: microsoft-learn)

---

Arkitekturmønstre

Mønster 1: Transparency-by-Design Pipeline

Integrer dokumentasjon som mandatory checkpoints i AI development lifecycle:

[Design] → Impact Assessment → [Development] → Model Card → [Testing]
   → Red Team Report → [Deployment] → Transparency Note → [Operations]
   → Monitoring Dashboard → [Incident] → Incident Report

Implementasjon i Azure:

• Azure DevOps: Gates for approval av model cards før deployment
• Azure ML: Auto-generate Responsible AI scorecard etter hver training run
• Microsoft Foundry: Built-in evaluation tools med export til PDF
• Microsoft Purview: Data lineage tracking for governance

Anti-pattern: Dokumentere etter deployment ("doc debt") — fører til incomplete/inaccurate documentation.

---

Mønster 2: Multi-Stakeholder Scorecard Review

Bruk Responsible AI Scorecard som kommunikasjonsverktøy mellom teams:

Workflow:

1. Data scientist genererer scorecard fra Azure ML dashboard
2. Product manager reviewer mot target metrics (accuracy, fairness)
3. Legal/Compliance sjekker mot regulatory requirements
4. Risk officer vurderer residual risk etter mitigations
5. Approval committee tar go/no-go decision basert på scorecard

Tooling:

• Azure ML Run History: Archive alle scorecards med versioning
• Power BI: Dashboard for å tracke metrics across models
• Teams/SharePoint: Collaborative review med comments

---

Mønster 3: Layered Disclosure

Tilby ulike nivåer av transparency basert på audience:

Audience	Disclosure format	Innhold
End users	In-app notifications, FAQs	"This feature uses AI", data collection disclosure, opt-out links
Developers	API documentation, model cards	Technical capabilities, limitations, sample code
Regulators	Transparency Notes, audit reports	Full system architecture, testing procedures, compliance mapping
General public	Transparency reports (annual)	Aggregate statistics, policy updates, incident summaries

Azure implementasjon:

• Azure OpenAI: Content Safety labels i API response
• Copilot Studio: Standard transparensmelding i chat interface: "Just so you are aware, I sometimes use AI to answer your questions."
• Azure Portal: Model catalog med filterable model cards

---

Mønster 4: Living Documentation

Dokumentasjon som evolves med systemet:

Prinsipp: Transparency Notes og model cards er ikke "set and forget" — de må oppdateres når modellen retraines, capabilities endres, eller nye risks oppdages.

Maintenance triggers:

Trigger	Oppdatering
Model retrain	Oppdater metrics, training data details i model card
New feature	Expand capabilities-seksjonen i Transparency Note
Incident	Legg til caveats/warnings, oppdater limitations
Regulatory change	Review compliance-seksjoner, update legal disclosures
User feedback	Clarify confusing sections, add FAQs

Versioning: Bruk semantic versioning (v1.0, v1.1, v2.0) og publish changelog.

Azure tooling:

• Azure DevOps: Version control for documentation
• Azure ML: Model versioning linked to scorecard versions

---

Beslutningsveiledning

Når kreves formell Transparency Note?

Obligatorisk:

Scenario	Rationale
Generative AI (LLMs, image generation)	Høy risiko for ungrounded content, bias, safety issues
High-risk AI systems (EU AI Act definition)	Legal requirement for transparency dokumentasjon
Customer-facing AI	User disclosure requirements, trust-building
AI med autonomous actions	Accountability for decisions made without human-in-loop

Anbefalt (ikke obligatorisk):

Scenario	Rationale
Internal productivity tools	Best practice for organizational accountability
Low-risk AI (non-generative)	Simplified transparency documentation akseptabelt

Ikke nødvendig:

• Rule-based systems uten ML
• Simple automation (RPA uten AI-komponent)

---

Velge dokumentasjonsformat

Decision tree:

Trenger du auditability for compliance?
  ├─ Ja → Responsible AI Scorecard (formal, PDF-based)
  └─ Nei → Er systemet customer-facing?
      ├─ Ja → Transparency Note (user-friendly, web-based)
      └─ Nei → Er det en pretrained model?
          ├─ Ja → Model Card (compact, metadata-focused)
          └─ Nei → Custom documentation (Markdown, Wiki)

Kombinasjoner:

• Enterprise AI product: Transparency Note + Responsible AI Scorecard + Model Card
• Internal tool: Model Card + lightweight governance doc
• Research prototype: Model Card only

---

Compliance mapping

EU AI Act requirements:

EU AI Act krav	Microsoft tool
Documentation av intended purpose	Transparency Note: "Capabilities" + "Evaluating and integrating"
Description of system architecture	Transparency Note: "The basics of [system]"
Risk assessment	Responsible AI Scorecard: fairness insights
Human oversight measures	Transparency Note: "System performance" (review interventions)
Accuracy metrics	Responsible AI Scorecard: model performance
Data governance	Datasheet + Azure Purview lineage tracking

Sector-specific (Norge):

• Finanstilsynet (finans): Scorecard for fairness metrics i kredittscoring
• Helsedirektoratet (helse): Transparency Note for diagnostiske AI-systemer
• Datatilsynet (GDPR): Privacy impact assessment (PIA) + Transparency Note

Confidence: Verified (Baseline + MCP-inferred)

---

Integrasjon med Microsoft-stakken

Azure Machine Learning

Built-in transparency tools:

Feature	Funksjon
Responsible AI dashboard	Suite av 7 tools (fairness, explainability, error analysis, etc.)
Responsible AI scorecard	PDF export av dashboard-insights
Model interpretability	Global/local feature explanations, counterfactual what-if
Fairness assessment	Disparate impact metrics across sensitive groups
Model catalog	Curated models med pre-built model cards

Workflow:

1. Train model i Azure ML
2. Generate Responsible AI dashboard i Studio
3. Analyze cohorts (gender, age, etc.)
4. Export Responsible AI scorecard
5. Archive scorecard i Run History
6. Share med stakeholders via link/download

Code example (Python SDK):

from azure.ai.ml import MLClient
from azure.ai.ml.entities import Model

# Register model med model card metadata
model = Model(
    name="credit-scoring-model",
    version="1.0",
    description="XGBoost model for credit scoring",
    tags={
        "intended_use": "consumer loans",
        "training_data": "anonymized-credit-bureau-2025",
        "fairness_evaluated": "True"
    }
)

ml_client.models.create_or_update(model)

# Generate Responsible AI dashboard
from responsibleai import RAIInsights

rai_insights = RAIInsights(
    model=model,
    test_data=test_df,
    target_column="loan_approved",
    task_type="classification",
    categorical_features=["gender", "ethnicity"]
)

rai_insights.explainer.add()
rai_insights.fairness.add(sensitive_features=["gender", "ethnicity"])
rai_insights.error_analysis.add()
rai_insights.compute()

# Export scorecard
rai_insights.save("rai_scorecard.pdf")

Confidence: Verified (MCP: microsoft-learn code samples)

---

Azure OpenAI Service

Transparency mechanisms:

Mechanism	Implementasjon
Transparency Notes	Per-model transparency notes (GPT-4, DALL-E 3, Whisper, o1, etc.)
System Card references	Links til OpenAI system cards (GPT-4, o1, Deep Research)
Content Safety labels	API response inkluderer content filter scores (hate, violence, sexual, self-harm)
Abuse monitoring	Automated detection av misuse (disclosed i data privacy policy)
Zero data retention	Customer prompts/completions ikke lagret (disclosed publicly)

User disclosure:

• Azure OpenAI API inkluderer model field i response → apps kan vise "Powered by GPT-4o"
• Content filter annotations → apps kan forklare hvorfor content ble blocked

Transparency Note URL: https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/transparency-note

---

Microsoft Foundry

Documentation features:

Feature	Funksjon
Model catalog	1500+ pretrained models med model cards
Evaluation tools	Safety metrics (hallucination, bias) pre-deployment
Transparency Notes	Integrated documentation for Foundry services
Tracing	Observability for agent actions (governance logs)
Compliance integrations	Export til Microsoft Purview for data governance

Agent transparency:

• Trace agent actions (tool calls, data access, decisions)
• Log reasoning steps for auditability
• Disclosure widgets: "This chatbot uses AI" embeddable component

---

Microsoft Copilot Studio

Built-in disclosures:

Component	Disclosure
Chat interface	Standard transparensmelding: "Just so you are aware, I sometimes use AI to answer your questions."
Generative answers	Attribution links til source documents
Data usage	Privacy statement link i bot settings

Maker-konfigurerte kontroller (ikke innebygde disclosures):

• Bekreftelse før dataendrende verktøy: makers kan kreve brukerbekreftelse før verktøy som endrer data kjøres. Kilden oppgir dette blant sikringene makeren konfigurerer for agenter med generativ orkestrering, og sier ikke at bekreftelse gis uten slik konfigurasjon.

Customization:

• Copilot Studio generative AI toolkit: Pre-built "AI disclosure" topic
• Adaptive cards: Template for transparency notices

Responsible AI FAQ:

• Oversikt (hub): https://learn.microsoft.com/en-us/microsoft-copilot-studio/responsible-ai-overview
• Generativ orkestrering — kilden for bekreftelses-sikringen over: https://learn.microsoft.com/en-us/microsoft-copilot-studio/faqs-generative-orchestration
• Generative answers — standardmeldingen står også her, med bredere ramme («best practice to communicate to users that the agent uses artificial intelligence»): https://learn.microsoft.com/en-us/microsoft-copilot-studio/faqs-generative-answers

---

Microsoft Purview

Data governance for AI:

Feature	AI transparency use case
Data lineage	Trace hvilke datasets ble brukt til training
Sensitivity labels	Classify PII/sensitive data i training sets
Audit logs	Track data access for compliance reporting
Data catalog	Metadata om datasets (ekvivalent til datasheet)

Integration med Azure ML:

• Auto-tag datasets med sensitivity labels
• Lineage graph: Dataset → Training job → Model → Deployment

---

Offentlig sektor (Norge)

Regulatory landscape

Norske krav:

Regulering	Transparency-krav
Personopplysningsloven (GDPR)	Informasjon om automated decision-making (art. 13-14), right to explanation (art. 22)
Offentleglova	Disclosure av AI-bruk i offentlige tjenester (med unntak for sikkerhet)
Digitaliseringsdirektoratets veileder	Anbefaling om "AI-merking" i brukergrensesnitt
EU AI Act (framtidig)	Transparency obligations for high-risk AI systems

Spesifikke tilpasninger:

For NAV (trygd/sosialtjenester):

• Obligatorisk: Transparency Note + Responsible AI Scorecard for automated decision systems
• Bruker-disclosure: "Vedtaket er basert på automatisk saksbehandling" i varsel
• Right to explanation: Provide counterfactual explanations ("du ville fått godkjent hvis...")

For Helsevesenet:

• Transparency Note må inkludere clinical validation results
• Model Card skal inneholde FDA/CE-marking-ekvivalent info (intended use, contraindications)
• Incident reporting: Adverse events må dokumenteres og rapporteres til Helsedirektoratet

For Kommunale tjenester (barnehageplass, skoleinntak):

• Lightweight transparency: Simplified transparency note for lavrisiko-systemer
• Public consultation: Draft transparency notes publiseres for comment-periode

---

Språkkrav

Norsk lovkrav:

• Bruker-facing disclosure: Må være på norsk (bokmål/nynorsk)
• Technical documentation: Kan være på engelsk hvis målgruppen er utviklere
• Regulatory submissions: Datatilsynet/Helsedirektoratet aksepterer engelsk technical docs, men executive summary må være norsk

Microsoft-støtte:

• Transparency Notes: Engelsk-only (men kan oversettes av kunde)
• Azure Portal: UI på norsk, men model cards er engelsk
• Responsible AI Scorecard: Støtter ikke norsk i preview (manual translation nødvendig)

---

Procurement requirements

Anbud for offentlige AI-systemer:

Typisk krav i kravspesifikasjon:

• "Leverandøren skal levere en Transparency Note som dokumenterer AI-systemets funksjon, begrensninger og sikkerhetstiltak."
• "Modellen skal ha en Model Card som beskriver training data, intended use og kjente biases."
• "Løsningen skal ha innebygd disclosure-mekanisme for sluttbrukere (norsk språk)."

Microsoft compliance:

• Azure OpenAI: ✅ Transparency Notes tilgjengelig
• Azure ML: ✅ Responsible AI Scorecard kan genereres
• Custom solutions: ⚠️ Kunde ansvarlig for å generere documentation

---

Kostnad og lisensiering

Azure Machine Learning

Responsible AI dashboard:

• Kostnad: Inkludert i Azure ML compute cost (ingen ekstra lisens)
• Pricing model: Pay-per-compute (Standard_DS3_v2: ~$0.27/hour)
• Estimat: Generate scorecard for medium model (~10k samples): $2-5 per run

Responsible AI Scorecard:

• Kostnad: Gratis (preview feature)
• Storage: PDF lagres i Azure ML storage (~1-5 MB per scorecard)
• Retention: Ingress til Run History: Gratis for 90 dager, deretter standard storage pricing (~$0.02/GB/month)

---

Azure OpenAI

Transparency Notes:

• Kostnad: Gratis (public documentation)
• Content Safety annotations: Inkludert i API pricing (ingen ekstra cost)

Custom Transparency Notes:

• Hvis kunde må generere egen Transparency Note for custom fine-tuned model: Konsulentarbeid (estimat: 20-40 timer = NOK 40 000-80 000 ved NOK 2000/time)

---

Tooling for documentation

Anbefalte verktøy:

Tool	Bruk	Kostnad
Markdown editors (VS Code, Typora)	Skrive Transparency Notes	Gratis
Model Card Toolkit (open source)	Generate model cards programmatically	Gratis
Azure ML SDK	Generate Responsible AI Scorecard	Inkludert i Azure ML
Microsoft Word/PowerPoint	Export scorecard til corporate template	Microsoft 365 lisens

---

Governance overhead

Time investment (estimat per AI system):

Aktivitet	Tid (første gang)	Tid (vedlikehold)
Transparency Note (initial draft)	20-40 timer	4-8 timer per major update
Model Card	4-8 timer	1-2 timer per retrain
Responsible AI Scorecard	2-4 timer (generate + review)	1 time per iteration
User disclosure design	8-16 timer (UX design)	Minimal (templates reusable)

Tip: Bruk templates fra Microsoft Responsible AI Standard for å redusere initial draft-tid med 50%.

---

For arkitekten (Cosmo)

Vurderingskriterier ved transparency-design

Spørsmål til kunden:

1. Hvem er målgruppen for transparency?

   • End users → Layered disclosure (in-app + FAQ)
   • Regulators → Formal Transparency Note + Scorecard
   • Developers → Model Card + API docs

2. Hva er compliance-konteksten?

   • EU AI Act → High-risk AI documentation requirements
   • GDPR → Right to explanation, automated decision disclosure
   • Sector-specific (helse, finans) → Additional certifications

3. Hva er risk-nivået?

   • Generative AI → Mandatory Transparency Note
   • High-stakes decisions (loan, diagnosis) → Responsible AI Scorecard
   • Low-risk automation → Lightweight model card

4. Finnes det eksisterende governance-prosesser?

   • Ja → Integrate transparency i existing approval workflows
   • Nei → Establish transparency-by-design pipeline

5. Hva er audience's technical literacy?

   • Non-technical → Use Responsible AI Scorecard med narrative sections
   • Technical → Model Card med detailed metrics
   • Mixed → Multi-format (scorecard for execs, model card for devs)

---

Recommendations by scenario

Scenario 1: Offentlig sektor chatbot (low-stakes)

Transparency approach:

• ✅ Lightweight Transparency Note (1-2 sider)
• ✅ In-app disclosure: "Denne tjenesten bruker AI — svar kan være unøyaktige"
• ✅ FAQ: "Hvordan fungerer chatboten?" med link til Transparency Note
• ❌ Ikke nødvendig: Formal Responsible AI Scorecard (ingen high-risk decision)

Tooling: Azure OpenAI Transparency Note + Copilot Studio disclosure widget

---

Scenario 2: Kommunal AI for barnehageplass-tildeling (medium-risk)

Transparency approach:

• ✅ Full Transparency Note (inkl. limitations, fairness testing results)
• ✅ Responsible AI Scorecard (for political approval process)
• ✅ Public transparency report: Aggregate statistics (søkere, inntak, appeals)
• ✅ User disclosure: "Vedtaket er basert på automatisk rangering — du kan klage"

Tooling: Azure ML Responsible AI dashboard + custom web-based transparency report

---

Scenario 3: Helsevesen diagnostisk AI (high-risk)

Transparency approach:

• ✅ Comprehensive Transparency Note (aligned med CE-marking documentation)
• ✅ Responsible AI Scorecard med clinical validation metrics
• ✅ Model Card med performance per patient subgroup (age, comorbidities)
• ✅ Clinician training materials (interpretability guidance)
• ✅ Patient disclosure: "AI assisterer legen — endelig beslutning tas av lege"

Compliance: GDPR, Helseforskningsloven, Medical Device Regulation (MDR)

Tooling: Azure ML + custom clinical validation dashboard

---

Red flags (når transparency er insufficient)

Warningssignaler:

• ❌ "Vi dokumenterer etter deployment" → Doc debt risk
• ❌ "Model Card er nok for high-risk system" → Compliance gap
• ❌ "Vi bruker generic template uten customization" → Ineffective disclosure
• ❌ "Transparency Note er ikke oppdatert siden launch" → Living documentation failure
• ❌ "End users vet ikke at de interagerer med AI" → User disclosure missing

Intervention:

• Implement transparency checkpoints i deployment pipeline
• Conduct compliance gap analysis (EU AI Act, GDPR)
• Establish documentation versioning og update triggers

---

Arkitekturvalg for transparency tooling

Decision matrix:

Behov	Løsning	Rationale
Formal compliance (audit-ready)	Azure ML Responsible AI Scorecard	PDF archive, versioning, metrics
User-facing disclosure	Custom web page + Azure OpenAI annotations	Layered disclosure, UX control
Developer documentation	Model Card i Azure ML catalog	Standardized metadata, search
Public reporting	Power BI dashboard + annual transparency report	Aggregate stats, trend visualization
Incident transparency	Azure Monitor + custom incident log	Real-time alerts, postmortem docs

---

Conversation starters

Når kunde sier: "Vi trenger compliance med EU AI Act"

Cosmo: "EU AI Act krever transparency documentation for high-risk systemer. La oss starte med:

1. Klassifisere systemet (Annex III risk categories)
2. Velge documentation format — anbefaler Transparency Note + Responsible AI Scorecard
3. Map compliance requirements til Microsoft tools
4. Establish living documentation workflow (updates ved retrain/incidents)

Har dere identifisert hvilken Annex III-kategori systemet faller under?"

---

Når kunde sier: "Brukerne må forstå hvorfor AI tok en beslutning"

Cosmo: "Dette handler om både interpretability og disclosure. To approaches:

1. Technical interpretability: Azure ML model explanations (feature importance, counterfactuals) — for power users/appeals
2. User-facing explanations: Simplified narratives i UI ("avslått fordi inntekt < terskel") — for alle brukere

Hva er målgruppen? Trenger de technical details eller intuitive forklaringer?"

---

Når kunde sier: "Transparency er for dyrt"

Cosmo: "Transparency har upfront cost, men preventerer costlier incidents senere. Breakdown:

• Compliance cost: Bøter for EU AI Act non-compliance: opptil €35 mill / 7 % av global omsetning (Art. 5-forbud; øvrige brudd €15 mill / 3 %)
• Incident cost: Reputational damage ved non-disclosed AI failure: Unmålbar
• Tooling cost: Azure ML Responsible AI dashboard: ~NOK 20-50 per scorecard

Return on investment: Transparency er billigere enn cleanup. Skal vi prioritere minimum viable transparency (model card + lightweight disclosure) for å starte?"

---

Kilder og verifisering

Verified sources (MCP: microsoft-learn):

1. Transparency note for Azure OpenAI https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/transparency-note (Status: Verified 2026-02 — Latest updates: o3/o4-mini, Deep Research system cards)

2. Transparency note for Azure AI Search https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/search/transparency-note (Status: Verified 2026-02 — Recommendations for A/B testing, bias detection)

3. Transparency note for Document Intelligence https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/document-intelligence/transparency-note (Status: Verified 2026-02 — Limitations for prebuilt/custom models)

4. Responsible AI scorecard documentation https://learn.microsoft.com/en-us/azure/machine-learning/concept-responsible-ai-scorecard (Status: Verified 2026-02 — Public preview, multi-stakeholder alignment use case)

5. Responsible AI dashboard documentation https://learn.microsoft.com/en-us/azure/machine-learning/concept-responsible-ai-dashboard (Status: Verified 2026-02 — 7 components: fairness, explainability, error analysis, etc.)

6. What is Responsible AI? https://learn.microsoft.com/en-us/azure/machine-learning/concept-responsible-ai (Status: Verified 2026-02 — Six principles: fairness, reliability, privacy, inclusiveness, transparency, accountability)

7. Microsoft Responsible AI Standard v2 https://blogs.microsoft.com/wp-content/uploads/prod/sites/5/2022/06/Microsoft-Responsible-AI-Standard-v2-General-Requirements-3.pdf (Status: Baseline — Impact Assessment framework, June 2022)

8. ISO/IEC 42001:2023 overview (Verified MCP 2026-06-19) https://learn.microsoft.com/en-us/compliance/regulatory/offering-iso-42001 Microsoft-sertifisering dekker nå: GitHub Copilot, M365 Copilot, Copilot Health, Copilot Studio, Dragon Copilot, Dragon Copilot (Radiologist), Microsoft Foundry og Security Copilot (utvidet fra kun M365 Copilot). (Status: Verified 2026-06-19 — AI management system standard)

9. Govern AI (Cloud Adoption Framework) https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/ai/govern (Status: Verified 2026-02 — AI governance policy examples, documentation requirements)

10. Establishing responsible AI policies (Cloud Adoption Framework) https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ai-agents/responsible-ai-across-organization (Status: Verified 2026-02 — Cross-functional governance, auditing, transparency mechanisms)

11. Generate Responsible AI insights in the studio UI https://learn.microsoft.com/en-us/azure/machine-learning/how-to-responsible-ai-insights-ui (Status: Verified 2026-08-09 — Scorecard-konfigurasjon: målverdier, cohort analysis i Data analysis-seksjonen, fritekstbeskrivelse i scorecard summary)

12. Use Responsible AI scorecard (preview) in Azure Machine Learning https://learn.microsoft.com/en-us/azure/machine-learning/how-to-responsible-ai-scorecard (Status: Verified 2026-08-09 — De sju scorecard-segmentene; preview uten SLA, ikke anbefalt for production workloads)

Baseline sources (model knowledge + MCP-inferred):

13. Model Cards for Model Reporting (Mitchell et al., 2019) https://arxiv.org/abs/1810.03993 (Academic origin of model card concept)

14. Datasheets for Datasets (Gebru et al., 2018) https://arxiv.org/abs/1803.09010 (Academic origin of datasheet concept)

15. EU AI Act https://artificialintelligenceact.eu/ (Status: Adopted 2024 — Transparency obligations for high-risk AI)

16. NIST AI Risk Management Framework https://www.nist.gov/itl/ai-risk-management-framework (US standard for AI governance)

17. Developing Responsible Generative AI Applications (Windows) https://learn.microsoft.com/en-us/windows/ai/rai (Status: Verified 2026-02 — Model Cards reference, red teaming, governance processes)

Unique sources: 17 URLs Confidence: 17 kilder — 12 oppført under «Verified sources», 5 under «Baseline sources»

---

For Cosmo: Denne kunnskapsbasen dekker både teknisk implementasjon (Azure ML dashboard, Azure OpenAI annotations) og organisatorisk praksis (governance workflows, compliance mapping). Bruk decision trees og scenario-spesifikke recommendations for å guide kunder gjennom transparency-design. Vekt living documentation-prinsippet — transparency er ikke en one-time artifact, men en ongoing practice.