Setting SQL AD Admin for Azure Synapse fails.

[catalinpopa247]

I've noticed that on some Synapse workspaces (not all of them), when trying to set up SQL AD admin, it fails with the following error:
"Failure occurred while performing CreateOrUpdateAadAdmin operation in one of the subsystems of the workspace.".

This happens no matter how you push the change: via portal, via PS or via CLI. More than that, it seems that CLI also gives a false response sometimes. Although the command offers a response that it passed through, the change isn't actually implemented.

I'm guessing that this probably happens on older Synapse Workspaces which were created before the SQL AD admin feature was implemented.

Can anybody confirm/infirm this and resolve the bug?

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @wonner, @zesluo.

Issue Details

---

I've noticed that on some Synapse workspaces (not all of them), when trying to set up SQL AD admin, it fails with the following error:
"Failure occurred while performing CreateOrUpdateAadAdmin operation in one of the subsystems of the workspace.".

This happens no matter how you push the change: via portal, via PS or via CLI. More than that, it seems that CLI also gives a false response sometimes. Although the command offers a response that it passed through, the change isn't actually implemented.

I'm guessing that this probably happens on older Synapse Workspaces which were created before the SQL AD admin feature was implemented.

Can anybody confirm/infirm this and resolve the bug?

Author:	catalinpopa247
Assignees:	-
Labels:	Service Attention, question, customer-reported, needs-triage, Synapse
Milestone:	-

[jiasli]

Adding service team to take a look.

[wonner]

Hi @catalinpopa247 , it's more like a backend issue. I recommend you create an IcM ticket to track this. Paste the "x-ms-client-request-id" and the error messages of the failed request to the ticket would be helpful.
cc: @kevinzz6

[catalinpopa247]

Not sure I follow - by IcM ticket you mean a support ticket in Azure?

[LuitWagemaker]

Working with @catalinpopa247 on this issue, I found that it could be related to timing, as in, the setting of the AAD Admin takes longer to propagate to the actual synapse instance than is shown in the Azure Portal. I noticed this when re-visiting a workspace that I could previously not update (add AAD user) and now could.
Is this a plausible explanation for this issue? And is there any chance on improving the feedback on this or improving the mechanics of this setting?

[wonner]

Not sure I follow - by IcM ticket you mean a support ticket in Azure?

@catalinpopa247 Yes, you can create support ticket here.

[catalinpopa247]

Hi - is there any progress on this?
with all due respect, opening a ticket to support here I think it is irrelevant. I think this should be directly looked at by relevant PG people and not being passed around support teams because they have no clue on how this can be properly managed.

[wonner]

Hi @catalinpopa247, could you please provide the detail error message and the workspace name? But I do recommend you create a support ticket, support team will help to find the right person to fix it. Because it seems like a backend issue but not a client issue if this issue occurs in all clients.
cc: @yanjungao718 for further help.