Unable to delete Azure Synapse Workspace even through Powershell force deletion

vaddi_dataengineer 20 Reputation points
2024-11-06T21:31:49.4833333+00:00

Hello Team,

I am unable to delete synapse analytics even though following up post through webUI or powershell. I tried following the steps mentioned in the link below :-

https://learn.microsoft.com/en-us/answers/questions/1465756/i-cannot-delete-azure-synapse-workspace?source=docs

but getting error -

Remove-AzResource: DeleteWorkspaceOrchestrationException : Workspace deletion failed due to unexpected exception.Check error message for exception details

CorrelationId: d406f6f6-7ca8-4901-9e4a-443db692eac8

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
5,031 questions
PowerShell
PowerShell
A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
2,657 questions
{count} votes

Accepted answer
  1. Ganesh Gurram 1,825 Reputation points Microsoft Vendor
    2024-11-13T00:41:52.0333333+00:00

    @vaddi_dataengineer - I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer

    Ask: Unable to delete Azure Synapse Workspace even through Powershell force deletion

    Solution: The issue is resolved, after following the step :-

    1. Grant the SQL Server Contributor Azure RBAC role to the principal named Microsoft Azure Synapse Resource Provider at the subscription containing the Synapse workspace to be deleted.
    2. Delete the Synapse workspace.
    3. Wait for the deletion operation to complete.
    4. Remove the Azure RBAC role assignment created as part of step 1.

    The issue was majorly due to SQL Server role assignment which was missing in subscription level.

    If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information. 

    If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue. 

     

    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members. 

     

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.