Be aware that Fabric has multiple URL's to enter, so port 1433 needs to be open on multiple of them, you notice this when running SSMS / ADS on prem sitting behind a corporate firewall instead of working from home. Microsoft has a support page for this.

if it is unfinished as current deployment pipelines (DP), I say keep it and cover first your base before moving on, at least take care that automatic binding isn't auto and could be FULLY parameter driven. Lots of folks using DFG2 would then happily also test this to, like me!

@Will Needham Thx for asking! Having different data streams from separate Service Bus queues for the Dev / Sta / Prd, I need to be able to make sure that pipelines and semantic models have bindings to the proper data sources. Likewise ADF I expected parameters to handle this. I am aware you can go the proxy route or hack beneath the given current gui, but it is ugly and it feels like the auto binding behavior is more a temporary bandage than a given solution. So don't get me wrong I am not bad mouthing here, else I would have waited for a year longer with already moving from ADF to Fabric. Nevertheless now it's just a very simple Bronze/Silver/Gold implementation. In short we are first going to test with hardcoding the source and there use variables which are tied to the parameters we do have available in the dev pipelines and take it from there until we have proven solutions for all our adventures on the road to implement the architecture we have in mind for our needs and wishes ;-)

You might want to have a look here: https://data-mozart.com/migrate-existing-power-bi-semantic-models-to-direct-lake-a-step-by-step-guide/

Do we need Fabric... Can't we do it with our Access licenses?