Hi Lenz, Philipp
Thanks for sharing the error details. The failure was not due to network or authentication policy but specifically how the SAS token was generated.
Key points checked
- The Event Hub namespace and entity names were correct.
- Firewall/VNet restrictions were not in place.
- The SAS key itself was valid.
Root cause
The resource URI included in the SAS token did not exactly match the Event Hub namespace/entity. Event Hubs requires this string to match precisely (all lowercase, correct namespace + event hub path). If casing or path differs, the service rejects the request with authorization errors.
Resolution
As per our internal team, you have confirmed that the issue is now resolved. The fix was to regenerate the SAS token using the correct resource URI (matching the Event Hub namespace and entity name exactly). After applying the updated token, the Event Hub accepted the requests and events flowed successfully.
Official docs:
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.