[FEATURE] return job_instance_id for cli job start/run command

[prasunbasak]

Use Case / Problem

fab cli job run/start command does not return the newly created jobId as a distinct token. instead it is embedded in the output 'message' . This requires extra scripts/regex etc to extract the jobId for further use, e.g. to find the job status of a long running job.
It would help to output jobId as an attribute in json output. (example below)

{
"timestamp": "2026-03-26T09:44:31.765080Z",
"id": "0a4e989f-7b7d-41d9-8fe5-b3ead1e35555",
"status": "Success",
"command": "job",
"result": {
"message": "Job instance '0a4e989f-7b7d-41d9-8fe5-b3ead1e35555' created"
}
}

Proposed Solution

fab cli job run/start command json output to return jobId as a distinct attribute. (example above in usecase description)

Alternatives Considered

regex script to extract jobId from output

Impact Assessment

• This would help me personally
• This would help my team/organization
• This would help the broader fabric-cli community
• This aligns with Microsoft Fabric roadmap items

Implementation Attestation

• I understand this feature should maintain backward compatibility with existing commands
• I confirm this feature request does not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cli's established patterns and conventions

Implementation Notes

src/fabric_cli/commands/jobs/fab_jobs_run.py gets the job_instance_id from rest call. can this be returned to the 'fab job start/run' call

[microsoft-github-policy-service]

Thank you for submitting this issue, @prasunbasak.
A member of the Fabric CLI team will review your submission and provide feedback shortly.

[github-actions]

AI Assessment: Valuable Enhancement

Directly exposing the job instance ID as a structured attribute in JSON output aligns with CLI output conventions and improves scripting/automation reliability. This avoids brittle parsing logic and is standard for job-launching commands in modern CLIs (per POSIX/GNU conventions and typical REST output patterns). The proposed change is backward compatible—the JSON structure is augmented, not altered, and users relying on textual output are unaffected.

The implementation is straightforward, as the job instance ID is already available after the REST call. Updating the output generation logic for fab jobs start and fab jobs run to include the id field will provide immediate value to automation users and is consistent with expected CLI data output practices.

Next Steps
📋 Backlog candidate — This enhancement has been triaged and will be considered for the team's backlog.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.