startswith in filter expression returns bad request

[glenthomas]

The example filter shown causes the service bus to return "(400) Bad Request. Invalid Filter. StartsWith is not allowed in the filter expression"

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e3dc0f0b-ef56-7ffd-a0a4-70ec75ac8c30
• Version Independent ID: 125cff6f-a5ec-b488-3b82-907e0aff1834
• Content: NamespaceManager.GetSubscriptions Method (Microsoft.ServiceBus)
• Content Source: xml/Microsoft.ServiceBus/NamespaceManager.xml
• Service: service-bus
• GitHub Login: @CamSoper
• Microsoft Alias: casoper

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @axisc.

Issue Details

---

The example filter shown causes the service bus to return "(400) Bad Request. Invalid Filter. StartsWith is not allowed in the filter expression"

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e3dc0f0b-ef56-7ffd-a0a4-70ec75ac8c30
• Version Independent ID: 125cff6f-a5ec-b488-3b82-907e0aff1834
• Content: NamespaceManager.GetSubscriptions Method (Microsoft.ServiceBus)
• Content Source: xml/Microsoft.ServiceBus/NamespaceManager.xml
• Service: service-bus
• GitHub Login: @CamSoper
• Microsoft Alias: casoper

Author:	MrGlenThomas
Assignees:	-
Labels:	Client, Docs, Service Attention, Service Bus, customer-reported, needs-team-attention, needs-triage, question
Milestone:	-

[ramya-rao-a]

@DorothySun216, Can you please update the docs for the GetSubscriptions method?

@glenthomas Please note that a newer package Azure.Messaging.ServiceBus,is available as of November 2020 for Azure Service Bus. While the older WindowsAzure.ServiceBus will continue to receive critical bug fixes, we strongly encourage you to upgrade. Read https://aka.ms/azsdk/blog/msging/intro for more details.