What problem does it solve? Managing Microsoft Fabric Variable Libraries through the REST API involves subtle pitfalls: wrong definition part names, stringified override values that the API rejects, confusion between definition edits and active value set state, and incorrect consumer wiring. This Skill encodes the verified endpoints, payload shapes, and gotchas so Variable Library operations succeed on the first attempt. ## Core Features & Use Cases - Definition authoring: Create or update Variable Library items with variables.json, settings.json, and valueSets/<name>.json parts using base64-encoded updateDefinition calls, with correct native JSON types for overrides. - Consumer wiring: Generate the Variable Library side of references for pipelines (libraryVariables), notebooks (notebookutils.variableLibrary), Dataflow Gen2, copy jobs, shortcuts, User Data Functions, and Airflow jobs. - Active value set operations: Read and switch the active value set per workspace or deployment stage via GET/PATCH on /variableLibraries/{id}, and explain Git serialization and CI/CD behavior. - Use Case: After deploying to a prod stage, point the prod workspace at the prod value set with a single PATCH call, then verify the change landed by reading back properties.activeValueSetName. ## Quick Start Ask the AI to create a Variable Library named AppConfig with dev and prod value sets in your Fabric workspace, or to wire an existing variable into a pipeline or notebook.