FutureOrders: SQLFilter - HighPriortyOrders: CorrelationFilter CorrelationID only - InternationalOrders: SQLFilter - Country NOT USA requires an SQL Filter HighQuantityOrders: SQLFilter - Need to use relational operators so an SQL Filter is needed. AllOrders: No Filter - SQL Filter: SQL Filters - A SqlFilter holds a SQL-like conditional expression that is evaluated in the broker against the arriving messages` user-defined properties and system properties. All system properties must be prefixed with sys. in the conditional expression. The SQL-language subset for filter conditions tests for the existence of properties (EXISTS), as well as for null-values (IS NULL), logical NOT/AND/OR, relational operators, simple numeric arithmetic, and simple text pattern matching with LIKE. Correlation Filters - A CorrelationFilter holds a set of conditions that are matched against one or more of an arriving message`s user and system properties. A common use is to match against the CorrelationId property, but the application can also choose to match against ContentType, Label, MessageId, ReplyTo, ReplyToSessionId, SessionId, To, and any user-defined properties. A match exists when an arriving message`s value for a property is equal to the value specified in the correlation filter. For string expressions, the comparison is case-sensitive. When specifying multiple match properties, the filter combines them as a logical AND condition, meaning for the filter to match, all conditions must match. Boolean filters - The TrueFilter and FalseFilter either cause all arriving messages (true) or none of the arriving messages (false) to be selected for the subscription. Reference: https://docs.microsoft.com/en-us/azure/service-bus-messaging/topic-filters