CmdID / az / az managedcleanroom / az managedcleanroom frontend / az managedcleanroom frontend analytics / az managedcleanroom frontend analytics query
az managedcleanroom frontend analytics query publish
Publish a query to the collaboration Azure CLI extensions reference
Publish a query configuration with SQL segments, execution sequence, and dataset mappings. Query segments can be provided as @file.json (full segment object including executionSequence) or as inline SQL strings (requires --execution-sequence parameter). The execution sequence defines which segments run in parallel (same number) or sequentially (different numbers). Cannot mix @file.json and inline SQL segments in the same command.
3 examples 9 options Its page in the Azure CLI extensions reference
Examples
Publish a query with segments from JSON files (segment files include executionSequence)
az managedcleanroom frontend analytics query publish --collaboration-id my-collab-123 --document-id my-query --query-segment @segment1.json --query-segment @segment2.json --query-segment @segment3.json --input-datasets "dataset1:view1,dataset2:view2" --output-dataset "output-dataset:results"Identify--collaboration-idCollaboration identifier--document-idQuery document identifier--query-segmentQuery segment SQL (@file.sql or inline).--input-datasetsComma-separated input datasets as datasetId:viewName pairs--output-datasetOutput dataset as datasetId:viewNameNote: Each segment JSON file should contain:data, executionSequence, preConditions, postFilters fieldsPublish a query with inline SQL segments (requires --execution-sequence)
az managedcleanroom frontend analytics query publish --collaboration-id my-collab-123 --document-id my-query --query-segment "SELECT * FROM table1" --query-segment "SELECT * FROM table2" --execution-sequence "1,2" --input-datasets "dataset1:view1" --output-dataset "output-dataset:results"Identify--collaboration-idCollaboration identifier--document-idQuery document identifier--query-segmentQuery segment SQL (@file.sql or inline).--execution-sequenceComma-separated execution sequence numbers (e.g., "1,1,2").--input-datasetsComma-separated input datasets as datasetId:viewName pairs--output-datasetOutput dataset as datasetId:viewNamePublish a query using a JSON body file (legacy mode)
az managedcleanroom frontend analytics query publish --collaboration-id my-collab-123 --document-id my-query --body @query-config.jsonIdentify--collaboration-idCollaboration identifier--document-idQuery document identifier--bodyJSON configuration file path (@file.json) or JSON string (legacy mode)Options
--api-versionAPI version to use for this request--bodyJSON configuration file path (@file.json) or JSON string (legacy mode)--cmdCLI command context--collaboration-id, -cCollaboration identifier--document-id, -dQuery document identifier--execution-sequenceComma-separated execution sequence numbers (e.g., "1,1,2").--input-datasetsComma-separated input datasets as datasetId:viewName pairs--output-datasetOutput dataset as datasetId:viewName--query-segmentQuery segment SQL (@file.sql or inline).