↳ GitHub sourceAnalytics ruleHigh
Cloud Replica Permanent Failover Performed by Tenant
Description
Detects permanent failover of a cloud replica initiated by a tenant. This might indicate disaster recovery activity or issues with primary systems.
- Rule type
- Scheduled
- Version
- 1.0.1
- Declared status
- Available
- Query frequency
- 5m
- Query period
- 5m
- Trigger
- gt 0
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Connectors
Data types
KQL query
Original query, unchanged.
Veeam_GetSecurityEvents
| where instanceId == 27000
| extend VmRef = extract("VmRef=\"([^\"]*)\"", 1, SyslogMessage)
| extend TenantID = extract("TenantID=\"([^\"]*)\"", 1, SyslogMessage)
| extend TenantID = extract("TenantID=\"([^\"]*)\"", 1, SyslogMessage)
| extend HostID = extract("HostID=\"([^\"]*)\"", 1, SyslogMessage)
| project
Date = format_datetime(TimeGenerated, 'dd.MM.yyyy HH:mm'),
DataSource = original_host,
EventId = instanceId,
["Replica Name"] = VmRef,
["Tenant ID"] = TenantID,
["Data SourceID"] = HostID,
MessageDetails = Description,
Severity = SeverityDescriptionRelated content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
9800e51↗- Source identifier
1f1634e5-585e-4187-ac5b-6d0e157bd2ea
Additional source files 1
Solutions/Veeam/Analytic Rules/Cloud_Replica_Permanent_Failover_Performed_by_Tenant.yamlsource ↗GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC