### Use Case / Problem Including API response or command details in a JSON output can make results clearer and more useful for both users and automation. ### Proposed Solution Place the API result or command details inside the `result.data` object for easy access and better integration. ### Alternatives Considered _No response_ ### Impact Assessment - [ ] This would help me personally - [x] This would help my team/organization - [x] This would help the broader fabric-cli community - [ ] This aligns with Microsoft Fabric roadmap items ### Implementation Attestation - [x] I understand this feature should maintain backward compatibility with existing commands - [x] I confirm this feature request does not introduce performance regressions for existing workflows - [x] I acknowledge that new features must follow fabric-cli's established patterns and conventions ### Implementation Notes This is already supported in the create command, and it should work in the others too. For example, in the exists command, putting the result in the response instead of the message would make it easier for users to parse the value.
Activity
microsoft-github-policy-service commentedon Jan 25, 2026
Thank you for submitting this issue, aviatco.
A member of the Fabric CLI team will review your submission and provide feedback shortly.