set Command¶
Set a resource property.
Supported Resource Types:
- Workspace
- Item
- Capacity
- Domain
- Connection
- Gateway
- Spark Pool
- Folder
- Shortcut
Setting domain properties requires tenant-level Fabric Administrator privileges
When setting an item definition, it is set without its sensitivity label
Usage:
Parameters:
<path>: Path to the resource.-q, --query <jmespath_query>: JMESPath query to the property.-
-i, --input <input_value>: Input value to set.Working with JSON input
For guidance on providing JSON input values across different shells, see JSON Input Handling.
-
-f, --force: Force set without confirmation. Optional.
Example:
Limitations¶
- Only one property path can be specified per
--queryargument - Paths must map directly to JSON paths without filters or wildcards
- If the property path doesn't exist on the item definition, it will be added, provided it's valid according to the item's schema. The
setcommand supports creation of 1 level at a time (e.g., to seta.b.c, first seta.b, then seta.b.c) - Properties that expect a JSON string value are not supported - JSON input is always parsed as an object
- The following properties cannot be set for any Fabric resource:
id,type,workspaceId,folderId
Query Support¶
To discover the available properties of a Fabric resource, use the get command to retrieve the resource's current state. However, note that not all properties returned by get are settable.
To determine which properties can be updated via the set command, refer to the Microsoft Fabric REST API documentation and locate the Update API operation for your specific resource type. Only properties documented in the Update API are supported for modification.
Setting Item Definition Properties
For Items, you can set any explicit path within the definition structure using dot notation for nested properties (e.g. definition.parts[0].property).
Paths must map directly to JSON paths without filters or wildcards. Refer to the Microsoft Fabric item definitions for the complete definition structure.
Item-Specific Definition Path Aliasing¶
Note on definition path aliases
These definition path aliases may be deprecated in a future release. We strongly recommend using explicit JSON paths within the item's definition structure rather than aliases.
These are definition path aliases that map to specific paths in the item's definition structure. When using the set command, you can use these aliases directly (as the -query / --q argument value) as they map to the correct definition paths:
| Item Type | Definition Path Alias | Notes |
|---|---|---|
| Notebook | lakehouse, environment, warehouse |
|
| Report | semanticModelId |
Applies only to Report definition.pbir version 1. For other versions, check the correct property path in the Report definition documentation |
| SparkJobDefinition | payload |