Quantum: update create new workspace template, fix e2e tests

[rigidit]

Description

• Updated workspace create command to support job submissions with disabled access keys on linked storage account
• Updated new storage account to be v2 in workspace creation because of the retirement of General-Purpose v1 (GPv1) storage accounts in October 13, 2026
• Added new e2e test, fixed test_get_provider and test_submit e2e tests

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @rigidit,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[github-actions]

Hi @rigidit

Release Suggestions

Module: quantum

• Please log updates into to src/quantum/HISTORY.rst
• Update VERSION to 1.0.0b13 in src/quantum/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema

[Copilot]

Pull request overview

This PR updates the Quantum extension to better support secure, managed-identity-based storage access during workspace creation and fixes storage selection behavior during job submission.

Changes:

• Update the workspace creation ARM template to disable shared-key access and add RBAC assignments needed for user delegation SAS scenarios.
• Fix job submission to pass an explicit storage connection string through to the Workspace client (instead of relying on linked-storage discovery).
• Bump extension version to 1.0.0b13 and add release notes.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
src/quantum/setup.py	Bumps extension package version to 1.0.0b13.
src/quantum/azext_quantum/operations/templates/create-workspace-and-assign-role.json	Disables shared-key access on the storage account and adds an additional storage RBAC role assignment.
src/quantum/azext_quantum/operations/job.py	Passes storage into the Workspace constructor so explicit connection strings are honored.
src/quantum/HISTORY.rst	Adds 1.0.0b13 changelog entry describing the storage and job submission changes.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 7 comments.