Saketh Chandra

This is the code I want to run: ## Source Code ```python3 from qiskit import QuantumCircuit, ClassicalRegister, QuantumRegister, transpile from azure.quantum.qiskit import AzureQuantumProvider provider = AzureQuantumProvider( resource_id="My_ID", location="japaneast" ) print([backend.name()...

> Looks like Qiskit is expecting the configuration of all backends to extend [BackendConfiguration](https://qiskit-test.readthedocs.io/en/latest/api/qiskit.providers.models.BackendConfiguration.html#qiskit.providers.models.BackendConfiguration) to report the required configuration settings. Our backends should do the same. > > Similarly, our...

> I took a closer look to our Backends, and they are already using `BackendConfiguration`, even more, the configuration already includes `memory`, for example, [here](https://github.com/microsoft/qdk-python/blob/b75676967a952763bd565b84ddc983de8d25809d/azure-quantum/azure/quantum/qiskit/backends/ionq.py#L141) and [here](https://github.com/microsoft/qdk-python/blob/b75676967a952763bd565b84ddc983de8d25809d/azure-quantum/azure/quantum/qiskit/backends/quantinuum.py#L185). > > Since...

I got the solution, It is not the issue with the backend. **The Backend supports the `memory` object,** We can get the data from each count/shot **Using:** > `job._azure_job.get_results()` >...