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 scripts

Reset-SIData

Start the data again from nothing

Purpose

Empties the install's data in place -- every table of the Pro database's data schemas and the run history that describes that data -- and keeps the install itself: the databases, users, roles, grants, settings, templates, the change journal, the audit trail and, by default, the identity ledger (stable ids; an object out of scope makes no CI). Plans by default: the rows and MB per table that would go, and what is kept.

When to run it

When the data should start again from nothing, for example after a scope mistake collected objects that were never wanted, and nobody uses the data yet. The scheduled pipeline fills the data again from the sources.

Who may run it

KindRoleScopeWhy
otherthe install identity (service principal + certificate), or the Invardia Support sessionthe Pro database (and the identity ledger database with -IncludeIdentityLedger)to read the tables and empty the data tables
azureRbacReaderthe Pro SQL serverto check the server's public network access first (a private install is refused, nothing is opened)

What it changes

WhereActionWhatPermission / roleScopeWhyUndo
Pro SQL databaseremoveevery row of the data schemas' tables and of the connectors' run and change log and the data-out items and batchesthe Pro databasea fresh start: the pipeline fills the data again from the sourcesnone: the rows are not kept; the next pipeline runs collect the data again
identity ledger SQL databaseremoveonly with -IncludeIdentityLedger (opt-in): every row of the identity ledger (its schema record is kept)the identity ledger databasethe objects get their ids again from the fresh datanone: the ledger is filled again by the next CI correlation
Pro SQL databaseupdatethe install lock (cfg.PipelineLock 'install'), held during the reset and released at its endthe Pro databaseno pipeline run, update or index build starts while the tables are emptiedreleased at the end; a lock left behind frees itself 15 minutes after its last sign of life
Pro SQL databasecreatean audit trail row (data.store.reset) with the rows per tablethe Pro databasewho started the data again, when and whynone: audit rows are kept

What it only reads

  • the tables of both databases with their rows and size
  • whether a pipeline run, an update, the clean-up or the index build is running
  • whether a live ServiceNow / REST output holds SecurityInsight's keys
  • the identity scope settings SI_Identity_SkipNeverSyncedDisabledAd and SI_Identity_SkipDeletedGroups
  • the SQL server's public network access

Parameters

ParameterRequiredDefaultWhat it does
-ReasonyesWhy (required, at least 10 characters): on the audit trail.
-ApplynoEmpty the tables. Without it the script only plans.
-AcceptExternalKeysLostnoGo on although a live ServiceNow / REST output holds SecurityInsight's keys (the fresh data gets new keys).
-IncludeIdentityLedgernoOpt-in: empty the identity ledger database too (default: kept -- stable ids; an object out of scope makes no CI).
-SqlServerno[string]$global:SI_ProSqlServer
-Databaseno[string]$global:SI_ProSqlDatabase
-IdentityDatabasenoThe identity ledger database (default: the install's SI_LedgerDatabase setting, else sqldb-si-identity) and its server.
-IdentitySqlServerno
-ResourceGroupNameno[string]$global:SI_Bootstrap_ResourceGroupNameThe install's resource group: its database server's public network access is read first (a private install is refused).
-SubscriptionIdno
-InsideNetworknoThis runs INSIDE the install's network (a machine in it, or the install's own job): the private check is not needed.
-SupportSqlnoReach the databases through the Invardia Support app's audited SQL (Invoke-InvardiaSupportSql; open the session first).
-AppIdno[string]$global:SI_SPN_AppId
-TenantIdno[string]$global:SI_SPN_TenantId
-CertThumbprintno[string]$global:SI_SPN_CertThumbprint
-StorenoThe databases, already open (New-SIProSettingsStore -Invoke ...): a test's fake, or a caller's store.
-IdentityStoreno
-NetworkAccessnoTEST SEAM: { } -> the database server's public network access ('Enabled' | 'Disabled' | ...), instead of reading it from Azure.
-PausenoTEST SEAM: { param([int]$ms) } -- the pause between two batches.
-PassThruno

Preview with -WhatIf

The preview: per table the rows and MB that would go, what is kept, and anything that would hold the reset; nothing is changed (same as without -Apply).

Undo

None: the emptied rows are not kept. The configuration is untouched, and the scheduled pipeline collects the data again from the sources.

Network

It connects to: *.blob.core.windows.net, *.queue.core.windows.net, *.table.core.windows.net, *.vault.azure.net, 169.254.169.254, api.loganalytics, api.loganalytics.io, api.msrc.microsoft.com, api.security.microsoft.com, api.securitycenter.microsoft.com, api.securityplatform.microsoft.com, database.windows.net, entra.microsoft.com, graph.microsoft.com, invardia.com, licenses.nuget.org, login.microsoftonline.com, management.azure.com, monitor.azure.com, nvd.nist.gov, outlook.office.com, outlook.office365.com, portal.invardia.com, storage.azure.com, vault.azure.net, www.powershellgallery.com

Download and run

Run these lines in PowerShell: the first downloads the script into the current folder, the second runs it.

Invoke-WebRequest https://invardia.com/support/si/Reset-SIData.ps1 -OutFile Reset-SIData.ps1
.\Reset-SIData.ps1 -Reason <Reason>

To check the download first, compare its SHA-256 with the published one:

SHA-256 878055bb756a8230635b229887a1a5c5970d777cf5b5e8a32cb4b96db8d6da36

Checksums: SHA256SUMS.txt · Version 3.0.79

Before you run it, compare the file's SHA-256 with its line in SHA256SUMS.txt.

Every parameter: Get-Help .\Reset-SIData.ps1 -Full · Source: Reset-SIData.ps1

Every script, identity and permission for your security review: SecurityInsight

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