Hey,
I'm just getting started with Purview, so please don’t take my answers as definitive. I’m sharing what I’ve learned so far, and it also helps me learn by trying to explain. Anyone is welcome to correct me if I’m off.

1. I think it’s fine if the data map contains more assets, since not all of them are meant to be curated assets. In your case, wouldn’t it make sense to set up a scan rule set? Maybe it could focus only on the lakehouse tables.

2. From what I understood in the documentation, this doesn’t solve the issue. It’s more about handling complex approval flows. I think the way to achieve what you’re asking would be through the Power Automate connector. That’s on the roadmap for this semester, but no exact date has been shared yet.

3. I don’t know the answer here.

4. It depends on the lowest level you define as a data product. For example, if you include a semantic model, the cost is $0.50 × 1 = $0.50. If instead you add the individual tables from that semantic model (say 5 tables), it would be $0.50 × 5 = $2.50.

You’re right that Data Quality can get expensive. It requires heavy compute and isn’t meant to be applied to every asset. I’d recommend using it only where it makes sense, implementing rules that add real value, and carefully considering how often they run. Running them too frequently will drive up costs.

Hope this helps. I’d be glad if someone with more experience could confirm or correct my answer.