I think he meant ads on Bing itself, not ads from some "Bing ads network" that may show up on other sites, analogously to Google AdSense.
With that said, I tried it for myself and found that the filter ##.b_ad
in EasyList does hide the ad in Chrome (I tested in uBlock Origin, but ABP should be similar), but it doesn't hide the ad in Edge...at least not when using the ordinary search box from the bing.com homepage, which in my region has the locale en-us: https://www.bing.com/search?q=lol&mkt=e ... lang=match
It did hide the ad in both Chrome and Edge when using this page from a custom search URL that set my locale to en-ww: https://www.bing.com/search?q=lol&mkt=e ... lang=match
Anyway, a similar filter worked, even in the local-locale version of the Bing search for lol
All elements of this filter need to be there (maybe something about specificity, or the different treatment of generic vs. specific hiding rules): the domain specifier, the element selector, and the attribute selector as opposed to the special class-selector syntax.
This probably points to a bug in ABP for Edge, or a limitation of Edge, because the special class-selector syntax should be more
effective than an attribute selector, because it has higher specificity.
There's a buzzin' in my brain I really can't explain; I think about it before they make me go to bed.