You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mac OS Big Sur 11.2.2.
PowerShell version: 7.1.2
Module version: 0.6.21
Steps to reproduce
I am trying to configure the Azure Defender data connector inside Sentinel. As far as I know, you need to refer to this data connector as AzureSecurityCenter when configuring it programmatically.
I expect the Azure Defender enabled subscription to be connected within the data connector. Like can be seen in the image below.
Actual behavior
The command executes without any output. No success or error message, nothing seems to happen. When looking in the Azure portal, no changes have been applied.
I have been successful using the Sentinel REST API directly. That works just fine.
The docs of the AZSentinel module doesn't describe what should be in the settings file. So I am guessing that the contents should be the same as the JSON payload that's used by the Sentinel REST API. For reference, below is the contents of the settings.json file that I used in the command.
Environment
Steps to reproduce
I am trying to configure the Azure Defender data connector inside Sentinel. As far as I know, you need to refer to this data connector as
AzureSecurityCenter
when configuring it programmatically.I am using the following command:
Expected behavior
I expect the Azure Defender enabled subscription to be connected within the data connector. Like can be seen in the image below.
Actual behavior
The command executes without any output. No success or error message, nothing seems to happen. When looking in the Azure portal, no changes have been applied.
I have been successful using the Sentinel REST API directly. That works just fine.
The docs of the AZSentinel module doesn't describe what should be in the settings file. So I am guessing that the contents should be the same as the JSON payload that's used by the Sentinel REST API. For reference, below is the contents of the settings.json file that I used in the command.
The text was updated successfully, but these errors were encountered: