Azure / Azure/azure-stream-analytics

ARM Template Generation Breaks Event Hub Configuration (Multi Subscription, Multi Event Hubs)

Open
#190 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
C#
Stars
229
Forks
920
PR merge metrics
No merged PRs in 30d

Description

Not sure if this is the right place to put this. I've been trying to figure out how to have two different Event Hub Namespaces in different subscriptions connected to the Azure Stream Analytics. When set up through the Azure portal, there are no issues. However, when I switch to using ARM templates and the azure-streamanalytics-cicd NPM package to create that ARM template, it consistently makes the Azure Stream Analytics resource break with this issue:

_The streaming job failed: Stream Analytics job has validation errors: Access to EventHub sb://XXXXX.servicebus.windows.net/XXXXX is not authorized. Exception Attempted to perform an unauthorized operation. For troubleshooting information, see https://aka.ms/azsdk/net/eventhubs/exceptions/troubleshoot_

I think that it has something to do with the fact that in the portal you can pass in a subscription to then tie the event hub to. But on the ARM template, I don't see an option to set the subscription for the event hub you wish to target. Any pointers on this one? Thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the azure-streamanalytics-cicd NPM package and its ARM template generation for Azure Stream Analytics Event Hub inputs. Compare the generated template with the portal-created configuration for Event Hubs in separate subscriptions, then verify that the resulting streaming job can authorize and connect to both namespaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, stream-processing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.