Skip to content
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

💡 Feature Request - Add 2 Required Log Analytics Solutions for SQL Assessments for MDFC #248

Closed
jtracey93 opened this issue May 26, 2022 · 0 comments · Fixed by #264
Closed
Assignees

Comments

@jtracey93
Copy link
Collaborator

jtracey93 commented May 26, 2022

See upstream issue Azure/Enterprise-Scale#979

Describe the solution you'd like

Add 2 Required Log Analytics Solutions for SQL Assessments for MDFC.

Missing Solutions:

  • SQLVulnerabilityAssessment
  • SQLAdvancedThreatProtection
"product": "OMSGallery/SQLAdvancedThreatProtection",
"publisher": "Microsoft"

&

"product": "OMSGallery/SQLVulnerabilityAssessment",
"publisher": "Microsoft"

Describe alternatives you've considered

N/A

Additional context

Raised from customer engagement wash-up call and also mentioned here https://youtu.be/o9wHIS_QLJE?t=1279

@ghost ghost added the Needs: Triage 🔍 Needs triaging by the team label May 26, 2022
@jtracey93 jtracey93 changed the title 💡 Feature Request - PLEASE CHANGE ME TO SOMETHING DESCRIPTIVE 💡 Feature Request - Add 2 Required Log Analytics Solutions for SQL Assessments for MDFC May 26, 2022
@jtracey93 jtracey93 removed the Needs: Triage 🔍 Needs triaging by the team label May 26, 2022
@jtracey93 jtracey93 self-assigned this Jun 17, 2022
@jtracey93 jtracey93 mentioned this issue Jun 17, 2022
9 tasks
jtracey93 added a commit that referenced this issue Jun 17, 2022
@ghost ghost added the Status: Fixed label Jun 17, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jul 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant