Description
The [Flare](https://flare.io) connector provides the capability to ingest threat intelligence and exposure data from Flare into Microsoft Sentinel. Flare identifies your company's digital assets made publicly available due to human error or malicious attacks, including leaked credentials, exposed cloud buckets, darkweb mentions, and more.
- Declared status
- 1
- Declared author / publisher
- Flare Systems
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions are required.
Workspace
Workspace
Microsoft Entra
Permission to create an app registration in Microsoft Entra ID.
Microsoft Azure
Permission to assign Monitoring Metrics Publisher role on data collection rule (DCR).
Flare
Permission to configure Microsoft Sentinel integration in Flare.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
1. Create ARM Resources and Provide the Required Permissions
This connector enables Flare to send threat exposure data to Microsoft Sentinel. When data forwarding is enabled in Flare, raw event data is sent securely to the Microsoft Sentinel Ingestion API.
Deploy Flare connector resources
2. Configure Flare to Send Logs to Microsoft Sentinel
Use the following parameters to configure Flare to send logs to your workspace.
Entra Application (Client) ID
Entra Directory (Tenant) ID
Entra App Registration Secret
Log Ingestion URL
3. Configure Alert Channel in Flare
As an organization administrator, you can configure an Alert Channel in Flare to send data to Sentinel.
Related 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
FireworkPush
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC