Reached the maximum number of Synapse workspaces

Question

question

Alex-6843 asked Apr 5, '22 PetkovYordan-6952 commented May 10, '22

Reached the maximum number of Synapse workspaces

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"ReachedPerSubscriptionWorkspaceLimit","message":"Reached the maximum number of Synapse workspaces allowed for this subscription. Please contact Microsoft support to request an exception. Subscription: 15b7fc55-8548-4a87-bfca-cf87a0bdc4aa. Subscription offer type: PayAsYouGo_2014-09-01. Current maximum: 0."}]}

I had above error when I tried to create a new Azure Synapse Analytics resource. How can I fix it, many thanks,

azure-synapse-analytics

· 6

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PRADEEPCHEEKATLA-MSFT · Apr 06 at 04:22 AM

Hello @Alex-6843,

This is a known issue with PayAsYouGo subscriptions.

We are currently working with the product team to resolve the issue asap. I will be update you once I hear back from the team.

You will need to create a request to increase the quota for your subscription as shown below:

Hope this will help. Please let us know if any further queries.

0 ·

synapse-ws-quota.gif (794.0 KiB)

ArunPaluru-4068 · Apr 06 at 10:41 PM

Hi Pradeep,
Im having the exact same issue-
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"ReachedPerSubscriptionWorkspaceLimit","message":"Reached the maximum number of Synapse workspaces allowed for this subscription. Please contact Microsoft support to request an exception. Subscription: xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx. Subscription offer type: PayAsYouGo_2014-09-01. Current maximum: 0."}]}

Is there a work around for this? Because there are existing Synapse workspaces within this subscription.

0 ·

PRADEEPCHEEKATLA-MSFT · Apr 13 at 07:53 AM

Hello @Alex-6843, & @ArunPaluru-4068,

Could you please try to create a Synapse workspace and do let us know if still see the problem.

0 ·

ArunPaluru-4068 PRADEEPCHEEKATLA-MSFT · Apr 19 at 01:31 AM

Hi @PRADEEPCHEEKATLA-MSFT , I tried this again, and I am still getting the same error as below. We have followed your instructions and increased the quota to 50 from 20 as well, and we only have 7 workspaces created currently.

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"ReachedPerSubscriptionWorkspaceLimit","message":"Reached the maximum number of Synapse workspaces allowed for this subscription. Please contact Microsoft support to request an exception. Subscription: xxxxxxxx-xxxx-xxxx-x-xxxxxxxxxxxxxx. Subscription offer type: PayAsYouGo_2014-09-01. Current maximum: 2."}]}

0 ·

PetkovYordan-6952 · May 03 at 10:19 AM

Hello.

Our team is currently having the same issue.

The error is listed below:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"ReachedPerSubscriptionWorkspaceLimit","message":"Reached the maximum number of Synapse workspaces allowed for this subscription. Please contact Microsoft support to request an exception. Subscription: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx. Subscription offer type: PayAsYouGo_2014-09-01. Current maximum: 2."}]}

We reached to Microsoft Support, they increased our quota from 20 to 60 but it did not resolve the issue.

Currently, I am still waiting for another response/resolution and if the problem gets resolved, I will comment on this thread again.

0 ·

PetkovYordan-6952 PetkovYordan-6952 · May 10 at 11:20 AM

Hello again.

The solution to this problem was to open a ticket in the "Help+Support" tab and then after a technical engineer contacted us, they resolved the problem from their end.

To anybody whoever has the same problem, I do recommend to just open a ticket and Microsoft will solve it in a ~week's time.

0 ·

question