> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Event Grid source plugin

> Configure the Azure Event Grid source plugin in Palo Alto Networks Telemetry Pipeline to ingest logs for processing and routing.

export const entity_0 = "Azure Event Grid source plugin"

export const plugin_0 = "Azure Event Grid source plugin"

<Info>
  This information is for Palo Alto Networks Telemetry Pipeline, which is a standalone
  product separate from Palo Alto Networks Cortex XCOR.
</Info>

The Azure Event Grid [source plugin](/ingest/pipeline/plugins/source-plugins)
(name: `azeventgrid`) lets you receive data from Azure and ingest it into a
telemetry pipeline using the [pull delivery](https://learn.microsoft.com/azure/event-grid/pull-delivery-overview)
API.

This is a
[pull-based](/ingest/pipeline/plugins/source-plugins#push-based-and-pull-based-source-plugins)
source plugin.

<Note>
  This plugin doesn't support the use of a
  [descriptive metadata name](/ingest/pipeline/plugins#descriptive-names) in the
  Pipeline Builder interface.
</Note>

<Note>
  This plugin doesn't support duplicates of itself within the same pipeline.
</Note>

## Supported telemetry types

The {plugin_0} for Palo Alto Networks Telemetry Pipeline supports these telemetry types:

| Logs | Metrics | Traces |
| :-: | :-: | :-: |
| <Icon icon="circle-check" color="green" /> | <Icon icon="ban" color="red" /> | <Icon icon="ban" color="red" /> |

## Configuration parameters

Use the parameters in this section to configure the {entity_0}. The
Palo Alto Networks Telemetry Pipeline web interface uses the items in the **Name** column to
describe these parameters. [Pipeline configuration files](/ingest/pipeline/v2/configure/config-files)
use the items in the **Key** column as YAML keys.

### General

| Name | Key | Description | Default |
| - | - | - | - |
| **Endpoint** | `endpoint` | Required. The endpoint URL of your Event Grid instance's namespace. | *none* |
| **Shared Key** | `key` | Required. The shared key used for authentication. | *none* |
| **Topic Name** | `topicName` | Required. The topic name from which to receive events. | *none* |
| **Event Subscription Name** | `eventSubscriptionName` | Required. The event subscription name. | *none* |

### Advanced

| Name | Key | Description | Default |
| - | - | - | - |
| **Memory Buffer Limit** | `mem_buf_limit` | Sets a limit for how much buffered data the plugin can write to memory, which affects backpressure. This value must follow Fluent Bit's rules for [unit sizes](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit#unit-sizes). If unspecified, no limit is enforced. <p />For v2 pipelines, this parameter affects only pipelines with the Deployment or DaemonSet [workload](/ingest/pipeline/v2/configure/kubernetes/workloads) type. To learn more, see the v2 [backpressure](/ingest/pipeline/v2/configure/backpressure) guide. <p />For v3 pipelines, this parameter is independent from the [OpenTelemetry `memory_limiter` and `batch` processors](/ingest/pipeline/v3#route-data-from-fluent-bit-to-opentelemetry). | *none* |

## Example configuration

```yaml theme={null}
service:
  log_level: error
pipeline:
  inputs:
    - name: azeventgrid
      endpoint: https://myNamespaceName.westus-1.eventgrid.azure.net
      key: ${SECRET_AZEVENTGRID_KEY}
      topicName: myTopic
      eventSubscriptionName: myEventSubscription
  outputs:
    - name: stdout
      match: "*"
```


## Related topics

- [Azure Event Hubs source plugin](/ingest/pipeline/plugins/source-plugins/azure-eventhub.md)
- [Azure Event Hubs destination plugin](/ingest/pipeline/plugins/destination-plugins/azure-eventhub.md)
- [Kubernetes Events source plugin](/ingest/pipeline/plugins/source-plugins/kubernetes.md)
- [Microsoft Intune - Audit event source plugin](/ingest/pipeline/plugins/source-plugins/intune.md)
- [Ingest telemetry data with source plugins](/ingest/pipeline/plugins/source-plugins.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.