Semantic Model Certification: Making Power BI Safe for AI to Answer From

Last updated: 2026-07-31

Semantic model certification is the control that decides whether an AI answer is trustworthy, because Copilot grounds on model metadata, not on your reports. EPC Group is a Houston-based Microsoft consulting firm operating since 1997, with six Microsoft Solutions Partner designations. Certify against a numbered standard, or your AI inherits every modeling defect you never fixed.

Key facts

• Only reviewers explicitly authorized by a Fabric administrator can apply the Certified badge; any user with write permission can apply Promoted. (Learn)
• Certification enablement can be delegated to domain administrators, so each Fabric domain names its own certifiers. (Learn)
• Test as role does not validate Copilot. Microsoft states not all aspects of a report can be validated with it, "including Q&A visualizations, Quick insights visualizations, and Copilot." (Learn)
• Copilot grounds a data question on the full model schema and full linguistic schema, plus descriptions, data types, format strings and data category — including objects on no report. Hidden fields and private tables are excluded. (Learn)
• Sensitivity label downstream inheritance stops at 80 items — above that, no downstream inheritance occurs at all. (Learn)
• Scheduled refresh is capped at 8 per day on Pro and 48 per day on PPU, Premium, or Fabric capacity; XMLA refreshes are not subject to the 48 limit. (Learn)
• Marking a model Approved for Copilot removes the friction treatment standalone Copilot applies to its answers; it can take up to 24 hours to propagate. (Learn)

Quick facts

The semantic layer became a compliance surface, and nobody re-scoped the controls

For fifteen years the semantic model was an engineering artifact. A modeling defect produced a wrong number on a report, a human looked at the report, and a human caught it. The control was the reader.

That control is gone. When a business user asks Copilot "what was margin in the eastern region last quarter," the answer is generated from the model schema, the linguistic schema, measure DAX, field descriptions, format strings, and data category — a documented list of grounding inputs published by Microsoft. No human reads a report first. The model is the answer. A semantic model with an ambiguous field name used to be untidy. It now determines what an AI system asserts to an employee, a regulator, or a customer, with no intermediate review. A Fabric data agent honors row-level and column-level security faithfully — but it honors your definition, correct or not.

Governance frameworks written before 2024 govern workspaces, licences, and sprawl. They do not govern the specific properties of a model that determine whether an AI grounds correctly. That is the gap this standard closes. EPC Group's position across every Microsoft Fabric consulting engagement is four words: multiple models, one truth. Language models rotate quarterly. Governance and accountability are the constants.

What Microsoft actually ships, and where the standard has to start

Microsoft gives you three endorsement badges — Promoted, Certified, and Master data. Promotion requires only write permission. Certification requires authorization by a Fabric administrator, and can be delegated per domain so a Finance domain names Finance certifiers. Master data marks an item as the authoritative source for core entities such as customer or product, and is also restricted to named reviewers.

Microsoft also ships the surface that makes a model answerable: Prep data for AI, on the Home ribbon in Power BI Desktop and on the semantic model page in the service. It holds AI data schemas (deselect fields Copilot should not see), AI instructions (business context, terminology, prioritization), and verified answers (human-approved visual responses bound to trigger phrases, stored on the model so they apply to every report built on it). The model can then be flagged Approved for Copilot.

What Microsoft does not ship is the standard. Its own governance guidance goes no further than suggesting a certification policy "might" include data accuracy validation and a security review. That is a category list, not a control: an auditor has nothing to test and a data team has nothing to fail against. So the standard has to be yours, it has to be numbered, and every gate has to produce an artifact.

The Groundable Model Standard (GMS-9)

EPC Group certifies semantic models against nine gates. A model is either GMS-9 certified or it is not. There is no partial credit, and no gate is optional for a model that Copilot or a Fabric data agent is permitted to answer from.

Gate 1 — One named owner. A single person, not a team alias, accountable for the model's correctness, named in the item description and the certification record. Certification tooltips already surface the certifier's name in discovery; the owner must be equally visible.

Gate 2 — Single-definition KPIs with a written business definition. Every measure exposed to AI carries a description stating the definition, the grain, the exclusions, and the approving business owner. Two measures may not compute the same concept differently in one model, and no measure name may carry different logic across two certified models. This is where certification programs fail, and it is a business exercise, not a technical one.

Gate 3 — Tested RLS and OLS, with a named test method. RLS roles are validated with Test as role, including unexpected values, not only expected ones. Microsoft's guidance shows why: a rule written as IF(USERNAME()="Worker", [Type]="Internal", TRUE()) returns every row for any typo. OLS is defined through TMDL and tested per role. Test as role does not cover Copilot, Q&A, or quick insights, and fails for DirectQuery models with SSO — so the gate requires a second, manual test: sign in as a real Viewer-role user and run a fixed Copilot prompt set.

Gate 4 — Sensitivity label applied, with inheritance verified. The model carries a Microsoft Purview label. Downstream inheritance is verified in lineage view and the 80-item ceiling is checked — above 80 downstream items no inheritance runs at all, a silent failure in large estates. Inheritance from labelled upstream sources is enabled.

Gate 5 — Documented refresh SLA and freshness contract. The description states refresh frequency, expected data-as-of time, and the acceptable staleness window. Failure notifications go to a monitored alias, not only the owner. Platform limits set the boundary: 8 scheduled refreshes per day on Pro, 48 on PPU/Premium/Fabric capacity, effectively unlimited via XMLA. A model whose business promise exceeds its licensed refresh ceiling cannot be certified.

Gate 6 — AI instructions and verified answers configured. AI data schemas exclude helper columns, sort-order columns, and surrogate keys. AI instructions state vocabulary, synonyms, and priority tables. Verified answers cover the questions the business asks most. Only then is the model marked Approved for Copilot.

Gate 7 — Lineage documented and impact analysis run. Upstream sources and downstream dependents are recorded from lineage view. Impact analysis runs before any change; it reports affected workspaces, reports, dashboards, and 30-day viewer counts, and provides the notify-contacts path. Composite models are enumerated, because Microsoft's guidance is that the single-version-of-truth model should not itself be one.

Gate 8 — A review cadence with a calendar owner. Quarterly at minimum, plus on-change review for schema, security, KPI, or data source changes, logged each time. An uninspected certified model is worse than an uncertified one, because the badge is what the catalog and the AI surface prioritize.

Gate 9 — A published decertification trigger. Six triggers, listed below. Any one fires and the badge comes off the same day, before remediation begins.

The GMS-9 certification checklist

What an uncertified model does to a Copilot answer

This is the section that governance frameworks skip. These are grounding failures, not report bugs, and they are silent — the answer looks confident and formatted.

Evidence and audit mapping

Certification is only worth building if it produces evidence someone else accepts. Each gate maps to a control family an internal auditor already tests — the same discipline EPC Group applies in SOC 2 readiness work across Microsoft 365.

The OneLake catalog's Govern tab does part of this reporting: label coverage, unlabeled item percentages, endorsement coverage, and freshness, scoped by domain. One limitation before you build a control on it — admin insights refresh once per day, so there is up to a 24-hour lag between the estate's real state and the reported state.

The six decertification triggers

Publish these before you certify anything. A standard without a revocation path is marketing.

1. Owner departure with no named successor within 10 business days.
2. KPI redefinition without a corresponding model change and re-review.
3. Any RLS or OLS change not re-tested under Gate 3.
4. Two consecutive refresh SLA breaches, or any breach exceeding the published staleness window by more than one refresh cycle.
5. Schema change published without impact analysis, evidenced by the activity log.
6. Review overdue by more than 30 days past the quarterly cadence.

The badge comes off first; remediation follows. Reversing that order is how estates end up with a hundred certified models nobody trusts, which is functionally identical to having none.

What certification costs

There is no honest hours-per-model figure, and any firm quoting one is averaging engagements that do not resemble yours. Effort is driven almost entirely by Gate 2 — how many KPIs have contested definitions and how many business owners must agree. The technical gates are fast; the margin-definition argument is not.

What can be stated precisely are the published platform constraints that bound what you are allowed to promise:

Two licensing consequences follow. A certified model with a sub-daily freshness promise cannot sit on Pro — compare the Premium and Premium Per User options and the full licensing and cost picture before publishing an SLA. And Copilot is a capacity feature, not a per-user one, which changes the business case alongside Microsoft 365 Copilot licensing.

What changed in 2026

• Prep data for AI is authorable in both Power BI Desktop and the service. AI data schemas, AI instructions, and verified answers now save to the model in either environment and are consumed everywhere Copilot exists.
• "Prepped for AI" was renamed "Approved for Copilot." Admins can also restrict standalone Copilot to approved items only.
• The Master data badge joined Promoted and Certified, restricted to reviewers named by the Fabric admin and applicable only to items containing data.
• Certification authority is delegable to Fabric domains, with a per-domain certifier list and documentation URL — which finally makes federated certification workable at scale.
• The OneLake catalog absorbed the Purview Hub security insights into its Govern tab: label coverage, DLP evaluation, endorsement coverage, and freshness, scoped by domain.
• Fabric data agents reached general availability and query semantic models with only Read permission on the model, no workspace access. RLS and column-level security still apply — which widens the blast radius of an untested security definition considerably.
• Direct Lake on OneLake does not fall back to DirectQuery. Direct Lake on SQL endpoints falls back silently when guardrails are exceeded or SQL-level RLS is detected; Direct Lake on OneLake returns an error and visuals fail to render. Certification must record which mode a model uses, because the failure behavior is opposite.

Get your models certified before your AI answers from them

EPC Group runs GMS-9 certification as a fixed-scope engagement: model inventory, gate-by-gate assessment, remediation backlog with owners, and a certification record your auditors can read. Start with the models Copilot can already answer from. Talk to our Power BI consulting team or see how this fits the wider data governance program.

Related: Power BI Premium · gateway configuration · GROUPBY in DAX · running totals in DAX · conditional formatting · Fabric consulting guide · Fabric vs Databricks · Copilot vs ChatGPT · CFO AI governance · Microsoft Frontier Company · Power BI consulting Houston.

Frequently asked questions

Sources and verification

1. Endorsement overview — Fabric
2. Endorse Fabric and Power BI items
3. Promote and certify Power BI content with endorsement
4. Prepare your data for AI to improve Copilot results
5. Prepare your data for AI: AI instructions
6. Prepare your data for AI: Verified answers
7. Use Copilot with semantic models (grounding data)
8. Copilot for Power BI overview: requirements
9. Row-level security (RLS) with Power BI
10. Row-level security guidance in Power BI Desktop
11. Object-level security (OLS)
12. Sensitivity label downstream inheritance
13. Sensitivity labels troubleshooting (80-item ceiling)
14. Information protection in Microsoft Fabric
15. Data lineage
16. Semantic model impact analysis
17. Govern Fabric data (OneLake catalog Govern tab)
18. OneLake catalog overview
19. Fabric domains
20. Configure scheduled refresh
21. Troubleshoot refresh scenarios
22. Fabric data agent concepts
23. Fabric data agent sharing and permission management
24. Integrate Direct Lake security
25. Microsoft Fabric adoption roadmap: Governance (the incumbent this article replaces)