New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to delete Threat Intelligence Upload Indicators API (Preview) dataconnector #10385
Comments
Hi @hakfo, |
@v-rusraut is there any update regarding this issue? |
Hi @hakfo, |
Hi @v-rusraut. I tried your solution of deploying the custom deployment. Unfortunately even after waiting several hours (even overnight), it still does not disconnect. Is there another fix we could try? |
Doesn't look like the template works either as I get the following error: {"code":"InvalidTemplate","message":"Deployment template validation failed: 'The template resource '/Microsoft.SecurityInsights/-dc-c6disteyi7k44' for type 'Microsoft.OperationalInsights/workspaces/providers/contentTemplates' at line '455' and column '87' has incorrect segment lengths. A nested resource type must have identical number of segments as its resource name. A root resource type must have segment length one greater than its resource name. Please see https://aka.ms/arm-syntax-resources for usage details.'."} |
Hi @ThePeteStore, Please verify that you provided correct value in below places like workspace,Region etc Thanks |
Hi @hakfo, |
I can confirm that we are still ingesting data after successfully running the script above |
Are you able to deploy mainTemplate now ? |
Please confirm on this. |
@v-rusraut I can also confirm that we are still ingesting data. It is still not possible to delete. |
@v-rusraut Yes, we deployed the mainTemplate the day of your suggestion and we are still ingesting data. |
Describe the bug
We are unable to delete the Threat Intelligence Upload Indicators API (Preview) dataconnector
It says we need to disconnect the dataconnector, but there is no disconnect button.
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: