Description
This Data Connector installs an Azure Function app to download GreyNoise indicators once per day and inserts them into the ThreatIntelIndicators table in Microsoft Sentinel.
- Declared status
- 1
- Declared author / publisher
- GreyNoise, Inc. and BlueCycle LLC
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
write permissions are required.
Workspace
Workspace
read and write permissions on the workspace are required.
Workspace
Workspace
Microsoft.Web/sites permissions
Read and write permissions to Azure Functions to create a Function App is required. [See the documentation to learn more about Azure Functions](https://docs.microsoft.com/azure/azure-functions/).
GreyNoise API Key
Retrieve your GreyNoise API Key [here](https://viz.greynoise.io/account/api-key).
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
You can connect GreyNoise Threat Intelligence to Microsoft Sentinel by following the below steps:
> The following steps create an Azure AAD application, retrieves a GreyNoise API key, and saves the values in an Azure Function App Configuration.
1. Retrieve your API Key from GreyNoise Visualizer.
Generate an API key from GreyNoise Visualizer https://docs.greynoise.io/docs/using-the-greynoise-api
2. In your Azure AD tenant, create an Azure Active Directory (AAD) application and acquire Tenant ID and Client ID. Also, get the Log Analytics Workspace ID associated with your Microsoft Sentinel instance (it should display below).
Follow the instructions here to create your Azure AAD app and save your Client ID and Tenant ID: https://learn.microsoft.com/en-us/azure/sentinel/connect-threat-intelligence-upload-api#instructions
NOTE: Wait until step 5 to generate your client secret.
Workspace ID
3. Assign the AAD application the Microsoft Sentinel Contributor Role.
Follow the instructions here to add the Microsoft Sentinel Contributor Role: https://learn.microsoft.com/en-us/azure/sentinel/connect-threat-intelligence-upload-api#assign-a-role-to-the-application
4. Specify the AAD permissions to enable MS Graph API access to the upload-indicators API.
Follow this section here to add **'ThreatIndicators.ReadWrite.OwnedBy'** permission to the AAD App: https://learn.microsoft.com/en-us/azure/sentinel/connect-threat-intelligence-tip#specify-the-permissions-required-by-the-application.
Back in your AAD App, ensure you grant admin consent for the permissions you just added.
Finally, in the 'Tokens and APIs' section, generate a client secret and save it. You will need it in Step 6.
5. Deploy the Threat Intelligence (New) Solution, (v3.0.14 or later) which includes the Threat Intelligence Upload Indicators API (Preview)
See Microsoft Sentinel Content Hub for this Solution, and install it in the Microsoft Sentinel instance. Note that you do not need to do any configuration in this step.
6. Deploy the Azure Function
Click the Deploy to Azure button.
[](https://aka.ms/sentinel-GreyNoise-azuredeploy)
Fill in the appropriate values for each parameter. **Be aware** that the only valid values for the **GREYNOISE_CLASSIFICATIONS** parameter are **benign**, **malicious** and/or **unknown**, which must be comma-separated.
7. Send indicators to Sentinel
The function app installed in Step 6 queries the GreyNoise GNQL API once per day, and submits each indicator found in STIX 2.1 format to the [Microsoft Upload Threat Intelligence Indicators API](https://learn.microsoft.com/en-us/azure/sentinel/upload-indicators-api).
Each indicator expires in ~24 hours from creation unless found on the next day's query. In this case the TI Indicator's **Valid Until** time is extended for another 24 hours, which keeps it active in Microsoft Sentinel.
For more information on the GreyNoise API and the GreyNoise Query Language (GNQL), [click here](https://developer.greynoise.io/docs/using-the-greynoise-api).
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.
- File
- Solutions/GreyNoiseThreatIntelligence/Data Connectors/GreyNoiseConnector_UploadIndicatorsAPI.json ↗
- Commit
9800e51↗- Source identifier
GreyNoise2SentinelAPI
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC