An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
If events are accepted or published but not matching any subscription, the first thing to verify is the event subject value for the SAS-uploaded files versus the manually uploaded files.
For Blob Storage events, Event Grid subject filtering is based on the subject string, and matching only supports:
-
subjectBeginsWith -
subjectEndsWith - optional case-sensitive matching
No wildcards are allowed for subject filters. Blob event subjects use this format:
/blobServices/default/containers/<containername>/blobs/<blobname>
Checks to perform:
- Compare the actual
subjecton a working manual upload event and a non-matching SAS upload event.- If the SAS path, container name, folder prefix, or blob suffix differs, the subscription can stop matching even when publishing succeeds.
- If case-sensitive subject matching is enabled, verify casing is identical.
- Recheck the subscription’s subject filters against the exact Blob subject format.
- To match a specific container, use a prefix like:
/blobServices/default/containers/containername/ - To match a folder or blob prefix, use:
/blobServices/default/containers/containername/blobs/blobprefix - To match file suffixes, use
subjectEndsWithsuch as.jpgor.log.
- To match a specific container, use a prefix like:
- Verify whether the subscription is filtering by event type as well.
- Event Grid subscriptions can filter by included event types in addition to subject.
- If the SAS-based upload results in a different event pattern than the manual upload, the event may publish successfully but still not match the subscription.
- If this is an Event Grid Namespace topic scenario and
MatchedEventCountdropped to zero while publishing continues, this can also be a platform-side issue rather than a filter issue.- A documented Microsoft Q&A case describes events continuing to publish successfully while subscription matching stopped, and the resolution required backend mitigation.
About the SAS token specifically:
- The provided material does not indicate that a SAS token itself changes Event Grid subscription matching behavior.
- Matching is based on the event data, especially the subject and configured filters.
- If SAS uploads are producing events with a different subject path or event characteristics than manual uploads, that would explain accepted-but-unmatched behavior.
A practical end-to-end validation path is:
- Capture one event from a manual upload that matches.
- Capture one event from a SAS upload that does not match.
- Compare:
-
subject - event type
- container path / blob path
- filename suffix
- casing
-
- In the subscription, verify:
-
subjectBeginsWith -
subjectEndsWith - case-sensitive subject matching
- included event types
-
- If those values are identical in the event payloads and matching still does not occur, treat it as a service-side matching issue and open a support case.