-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Defender for Cloud Data Connector doc conflict on requirement for sub-level plans #9426
Comments
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal. |
Hi @deggis , Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 24Nov23. Thanks! |
Hi @deggis ,I am working on changes and will get back to you with updates by 29Nov23. |
Hi @deggis ,Apologies for the delayed response, Standard tier one has been removed ,but as per the connector configuration we need to select subscriptions where Microsoft defender plans are enabled, Please let me know if its 5n, I am proceeding with the changes and will have an internal review(https://github.com/Azure/Azure-Sentinel/tree/users/v-muuppugund/CloudDataConnector). |
Hi @deggis ,Gentle Reminder, Please let me know if you have issues on above mentioned changes, otherwise will proceed with changes, Thanks. |
At least the removal of "standard tier is no longer required." looks good to me. |
@deggis ,Will update you once PR completed,Thanks. |
@deggis ,Its a 1p connector and don't have permissions, Will update you, Thanks. |
Hi @deggis ,Pushing the PR as we have the process for 1p connector and will keep you updated once pr is completed |
Hey @deggis, PR has been merged, and the new changes will get reflect in upcoming solution version. Thanks! |
Describe the bug
Documentation for Defender for Cloud Data connector has conflicting statements and does not cover subscriptions with only per-resource enabled Defender for Cloud plans.
To Reproduce
Steps to reproduce the behavior:
There seems to be inconsistency between the lines 58 and 69:
Expected behavior
If this text stays, "that have at least one Microsoft Defender plan enabled in Microsoft Defender for Cloud", I would expect the documentation to updated to cover subscriptions that don't have per sub plans, but only per resource enablements (like Defender for Storage) for some resources.
The text was updated successfully, but these errors were encountered: