Open rvbaast opened 3 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.
SQL team, please help to look into this question.
Hello @rvbaast Apologies for the delayed response. I see that this issue is opened a long time ago and no further activity had taken place. So wanted to check if you are still looking for assistance on this query? Please let us know.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.
Author: | rvbaast |
---|---|
Assignees: | - |
Labels: | `SQL`, `Service Attention`, `question`, `customer-reported`, `needs-author-feedback` |
Milestone: | - |
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!
I have since then learned that the SQL server and log analytics were in a different tenant. So no this is no longer relevant. Thanks for following up on this question.
Description
Using the Cloud shell in the azure portal I'm trying to test the Set-AzSqlServerAudit command to enable SQL Auditing to a Log analytics workspace. This works perfectly fine if the LogAnalytics workspace is in the same subscription as the Sql Server. However if I try to refer to a LogAnalytics workspace which is in a different subscription the command gives the following result :
Set-AzSqlServerAudit: One or more errors occurred. (Operation returned an invalid status code 'Conflict')
Steps to reproduce
Environment data
Module versions
Debug output
Error output