Skip to main content

Explore by topic

Toolkits

Reusable starter kits, checklists, and templates for faster engineering execution.

ChecklistsPatternsTemplates20 posts

What you will find here

  • Authorization checklists that keep chat, browse, and citation paths on the same entitlement model.
  • Refresh and Direct Lake decision guides so semantic freshness is a contract, not a portal checkbox.
  • Fabric CI/CD templates for stable item identities and explicit blast-radius boundaries.
  • Modeling readiness gates for Genie-style analytics before you tune prompts.

Posts tagged Toolkits, including operational checklists and patterns from the newer publishing backlog.

Rename the estate once: workspace naming is architecture

Argue that inconsistent workspace display-name prefixes create operational tax and that a one-time rename with stable catalog names is cheaper than perpetual translation layers.

Env files are not environments: isolate with Azure CLI discipline

Show how collapsing redundant env templates and treating Azure CLI subscriptions/resource groups as the real isolation boundary prevents POC/MVP config drift.

Language gates belong in CI, not in code review folklore

Argue for native CI linters and language test gates so white-label and locale regressions fail the build before demos do.

Feature toggles beat hard-coded agent IDs

Replace hard-coded agent catalogs with product feature flags plus per-agent overlay rows for scope, starters, export prefixes, and access arrays.

Genie readiness is a modeling problem, not a prompt problem

What has to be true in naming, modeling, and catalog descriptions before conversational analytics tools like Genie produce trustworthy answers.

Type each column once, as early as you dare

Argue for typing published columns in bronze (or the earliest stable layer) and banning ritual CAST in silver and gold.

AI import UX is governance: default-deny uncertain rows

Generalize section-aware AI import so uncertain matches stay deselected by default and users must opt in to incomplete rows.

Row counts lie: validate MLVs column by column

Push migration checklists to per-column tables and type-aware aggregates so MLV cutovers catch semantic drift early.

Fabric CI/CD blast radius: when no changes still deploys

Why Fabric deployment tooling can republish unchanged notebooks and how to design for stable identities and smaller blast radius.

Semantic refresh architecture: notebooks, pipelines, and Direct Lake

How to choose notebook, pipeline, or scheduled refresh for lakehouse semantics, and when Direct Lake beats a SQL endpoint for heavy facts.

Knowledge RBAC for enterprise agents: same gates for chat, browse, and citations

How to design folder-scoped knowledge access for enterprise agents so chat, library browse, downloads, and citation PDFs share one entitlement model.

Consolidate Fabric monitoring into one operable skill

Show why scattered Fabric monitor scripts should become one skill/runbook interface for humans and coding agents.

Bulk reload is an orchestration problem, not a bigger VM wish

Explain batched parallel page ingest for large ledger entities so full reloads finish without driver OOM.

If you cannot explain the tool calls, you do not have an agent product

Argue that activity timelines must reconcile Foundry traces, MCP knowledge searches, and UI tool-call counts, or support will never trust the product.

The AI shell proxy is a security boundary

Compare hardening options for browser-to-API proxies in front of agent backends, including runtime mismatch and Front Door failure modes.

PII redaction belongs in the notebook config, not in tribal knowledge

Show how a reusable notebook-level redaction contract (flags, tokens, regex, known-name UDF) makes free-text exports safe without blanking legitimate addresses and codes.

Matching relationship types is cheaper than debugging blank visuals

Show how int64 vs string mismatches across role-playing dims silently break relationships and how to align gold SQL with TMDL.

When warehouse views time out, materialize the trunk not the leaves

Propose a layered performance playbook: drop orphans, cheap rewrites, then materialize the two or three consolidations everything else depends on.

Variable Library is your environment map, not a sticky note

Use a Git-tracked Fabric Variable Library with per-stage value sets so rebind notebooks and pipelines stop hard-coding workspace IDs.

Lineage explorers beat tribal notebooks

Argue for a small lineage explorer over ad-hoc pipeline docs so engineers can see dependencies before they break them.