# CloudQuery concurrency spec parameter behavior with Azure API calls

**URL:** <https://community.cloudquery.io/t/cloudquery-concurrency-spec-parameter-behavior-with-azure-api-calls/668>\
**Category:** CloudQuery Plugins\
**Created:** [October 15, 2023, 12:27pm UTC](https://community.cloudquery.io/t/cloudquery-concurrency-spec-parameter-behavior-with-azure-api-calls/668 "2023-10-15T12:27:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thorough-bear](https://avatars.discourse-cdn.com/v4/letter/t/f08c70/32.png) [@thorough-bear](https://community.cloudquery.io/u/thorough-bear)\
**Post date:** [October 15, 2023, 12:27pm UTC](https://community.cloudquery.io/t/cloudquery-concurrency-spec-parameter-behavior-with-azure-api-calls/668/1 "2023-10-15T12:27:21Z")

</div>

Hi, quick question regarding the `concurrency` spec parameter using the Azure plugin.

When syncing only one subscription and two tables with a relation (for instance, `azure_storage_accounts` and `azure_storage_containers`), does the `concurrency` spec parameter matter? If I have 100 StorageAccounts, and `concurrency=100`, will it make 100 API calls concurrently to `azure_storage_containers`?

---

<div class="post-metadata">

**Author:** ![yevgenyp](https://avatars.discourse-cdn.com/v4/letter/y/3be4f8/32.png) [@yevgenyp](https://community.cloudquery.io/u/yevgenyp)\
**Post date:** [October 15, 2023, 3:21pm UTC](https://community.cloudquery.io/t/cloudquery-concurrency-spec-parameter-behavior-with-azure-api-calls/668/2 "2023-10-15T15:21:35Z")

</div>

Hi! I’m not sure on top of my head, but I think it has some tree-like/logarithm algorithm that spreads those 100 across the max depth of resources. So, probably, it’s something like 80 concurrent calls for the top level and 20 concurrent calls for the child tables.