Azure AADconnect attribute filtering using custom attribute created using Schema extension

We have a string valued attribute which is attached to user class. This attribute is created using schema extension. When i use this custom attribute to implement a inbound AADconnect attribute filtering (negative) it doesnt work.

However if i am using a extensionattribute to achieve the same filtering it works flawlessly.

Does azure attribute filtering work with customer (extended) attributes ?