An item owner opens the endorsement settings on her semantic model of visitor-flow statistics, hoping to mark it Certified so other branches can trust it, but the Certified option is unavailable to her even though she has edit permission on the item. What is the most likely reason?
Select an answer to reveal the explanation.
Short Explanation
Certified isn't a self-serve badge — it's the tenant's way of saying 'this is officially trusted,' and that stamp is reserved for a specific, admin-designated list of reviewers, not just whoever owns the item.
Full Explanation
Certification in Fabric's endorsement system is deliberately gated: only accounts the tenant administrator has designated as certification authorities can apply the Certified badge, regardless of who owns or can edit the item. This is what distinguishes Certified from Promoted, which item owners with sufficient permission can apply themselves without any such gate. The owner not being on that designated list is the straightforward explanation for the option being unavailable to her, even with full edit rights on the item. Certified status has not been removed from Fabric or folded into Promoted — both levels remain distinct, with Certified carrying the stronger, reviewed trust signal. A sensitivity label has nothing to do with endorsement eligibility; the two features serve different governance purposes and aren't prerequisites for each other. Row-level security configuration is similarly unrelated to whether an item can be certified — endorsement is a quality/trust signal, not an access-control state. The operational path forward is for the owner to either request certification from someone on the tenant's certification-authority list or apply Promoted instead, which is within her own permission.