Azure-docs: Advanced filtering limitation for some data.claims properties

[romankiss]

In the document is missing (in the limitations section) a limitation of the advanced filtering for some properties of the data.claims object.

There is no way to filter for some claims properties where their name is represented by JWT specification, for instance:
we can not filtered it based on the emailaddress, name, etc., the reason is the name of the properties, which is a uri format, for instance:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

Question:
Is there some undocumented workaround to use these properties in the advanced filtering or it will be fixed in the next version?

Thanks
Roman

---

Document Details

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

• ID: 1b572f63-312f-4567-5f06-d09bcccf303e
• Version Independent ID: df817c5f-24e4-bdc7-511c-141d07a53d15
• Content: Event filtering for Azure Event Grid
• Content Source: articles/event-grid/event-filtering.md
• Service: event-grid
• GitHub Login: @spelluru
• Microsoft Alias: spelluru

[DixitArora-MSFT]

Hi @romankiss Thanks for reaching out. We will review and update as appropriate.

[DixitArora-MSFT]

@spelluru Any inputs in this ?

[spelluru]

@banisadr - could you please take a look at it when you get a chance? Thanks

[DixitArora-MSFT]

@banisadr Just following up again in case missed the previous communication.

[DixitArora-MSFT]

@romankiss I have assigned this to content author for further review and update as appropriate.

[banisadr]

Oh, interesting question @romankiss, thanks for bringing it up. I actually don't know if we have a way of doing this at the moment. Let me get back to you shortly.

[banisadr]

@romankiss unfortunately we do not have an escape character built into key definitions for advanced filters and barring that, this is not possible today. I've added it to our backlog for consideration during future improvements of filtering.

So that I can include it, are there any other details of your use case you can share and what is being blocked from a functional standpoint?

[romankiss]

Thanks Bahram,

• have a look at the following https://stackoverflow.com/questions/60611974/azure-event-grid-resource-write-success-filter-by-email-address

[ajomathew]

Email based filtering would be more accurate than that of name based filter. It would be great if there is a way to get this implemented.

[banisadr]

@ajomathew what do you mean by that? Is there a technical difference in what string == [email protected] and email == [email protected] accomplishes?

[ajomathew]

@banisadr Sorry for the confusion, it would be great to have a filter work with email address.
Right now only
data.claims.http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress data.claims.http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
has email address as a value.
It would be great to have a filter to work with email address as there can be peoples with same names john.[email protected] and john.[email protected] can have same name
John Doe. Hence filter based on name wouldn't work as expected.