Azure / Azure/azure-powershell

Add EventGridSystemTopicEventSubscription with deadletter not working

Open
#26,870 4 comments 0 reactions 0 assignees View on GitHub
act-codegen-extensibility-squad customer-reported Event Grid question Service Attention
Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
3d 14h
Merged PRs (30d)
54

Description

### Description

I want to create an event subscription for a FunctionApp on a SystemTopic but can not find how to define the DeadletterEndpoint. My pipeline has Az module v12.5.0 installed.

The following code is working but how can I define the storage account container for deadletter?

```
$funcid = "/subscriptions/$funcSubID/resourceGroups/$func_rg/providers/Microsoft.Web/sites/$funcapp/functions/$func_name" $func_evdo = New-AzEventGridAzureFunctionEventSubscriptionDestinationObject -ResourceId $funcid

New-AzEventGridSystemTopicEventSubscription -ResourceGroupName $resourceGroupName `   
-eventSubscriptionName $eventSubscriptionName `
-systemTopicName $systemTopicName `
-destination $func_evdo
```
I searched this documentation but couldn't find something about DeadletterEndpoint or destination: https://learn.microsoft.com/en-us/powershell/module/az.eventgrid/new-azeventgridsystemtopiceventsubscription?view=azps-12.5.0

### Script or Debug output

```PowerShell
The parameter cannot be found that matches name - I tried DeadletterEndpoint or DeadletterDestination
```

### Environment data

```PowerShell
PSVersion: 7.4.6
```

### Module versions

```PowerShell
Az.Accounts: 4.0.0
Az.EventGrid: 2.1.0
```

### Error output

```PowerShell

```

Contributor guide

Open the contributing guide

Research direction

Start with the New-AzEventGridSystemTopicEventSubscription cmdlet and its linked Az.EventGrid 2.1.0 documentation, checking the available destination and dead-letter parameters. Compare the documented interface with the reported command behavior and confirm that a storage account container can be configured; done means the supported configuration is exposed or the documentation clearly explains the limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.