Skip to content
InvardiaInvardia
Why InvardiaProductsFeaturesPricingCommunity
Docs
All documentation
Product documentationPIM ManagerSecurityInsight
SettingsPIM Manager settingsSecurityInsight settingsEntra Policy Suite settings
ScriptsPIM Manager scriptsSecurityInsight scriptsEntra Policy Suite scriptsInvardia scripts
Error codesPIM Manager error codesSecurityInsight error codes
API and MCPPIM Manager APIPIM Manager MCP toolsSecurityInsight APISecurityInsight MCP tools
SecurityPIM Manager security packSecurityInsight security packEntra Policy Suite security pack
Network and designPIM Manager network guidesPIM Manager command wizardNetwork egressDesign your installationCalculate your cost
SupportSetup scriptsRemote support access
Search the docs
SupportAboutContactBook a demoCustomer portalDesign your installationFree Pro trial

SecurityInsight settings · Settings > Risk Analysis reports

Copy Risk Analysis report rows to Log Analytics (SI_RiskAnalysis_Detailed_CL)

KeySendToLogAnalytics
WhereSettings > Risk Analysis reports > Report mode and output
TypeOn / off
DefaultOff: the report rows are kept in the database only
EditionCommunity
ConfirmationSecurityInsight asks you to confirm before it is switched on.

What it does

Optional. After each Risk Analysis run, copies its report rows into your Log Analytics workspace (SI_RiskAnalysis_Detailed_CL, and SI_RiskAnalysis_Summary_CL when the Summary report runs; the day's trend row in SI_Trend_CL), for your own workbooks, Sentinel or KQL. SecurityInsight itself does not need it: its pages, the data sync, the vulnerability connectors and the trends read the results from its database. On a large estate the copy takes a long time and adds Log Analytics ingestion cost. Off by default.

When enabled

after every Risk Analysis run its report rows are also posted to SI_RiskAnalysis_Detailed_CL (SI_RiskAnalysis_Summary_CL for the Summary report), after the result is complete in the database, and the day's trend row to SI_Trend_CL. On a large estate that is close to an hour, and it costs ingestion for every row, every run.

When disabled

nothing is copied; the Excel reports, the mail and everything SecurityInsight shows are unchanged. The Azure workbook in preview\AzureWorkbook reads the copy, so it needs it on.

Risk and how to reverse it

Log Analytics ingestion cost for every report row, every run, and a longer run on a large estate. SecurityInsight itself does not need the copy: its pages, the data sync, the vulnerability connectors and the trends read the database. Reversible: turn it off and the next run copies nothing.

Requires

Read by: risk-analysis.

Recommended

Off, unless your own workbooks, Sentinel rules or KQL read the report rows in Log Analytics.

Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack

InvardiaInvardia

See the risk. Control the access.

Products

PIM ManagerSecurityInsightEntra Policy SuiteAll featuresPricingFree 60-day Pro trialBook a demoWhy Invardia

Docs

DocumentationSearch the docsPIM Manager settingsSecurityInsight settingsPIM network guidesCommand wizardNetwork egressPIM Manager design configuratorSecurityInsight design configuratorDesign your installationCalculate your cost

Company

AboutContactCustomer portalSupportHow support worksHow updates reach youSupport in numbersSetup scriptsRemote support accessContact: info@invardia.com

Legal

Terms of saleLicence termsData processingPrivacyCookiesCompany information
© 2026 Invardia – a brand of 2LINKIT, founded and owned by Morten Knudsen · Strandvejen 21A, 6000 Kolding, Denmark · VAT DK39208032 · Contact: info@invardia.com