mapped my semantic model to the gateway but i dont think its mapped

[db042190]

Hi, my peer asked for help publishing his new report to an existing workspace.  i did so after "taking control" and then tried mapping his semantic model to our  gateway.   In the image below is what i was presented , i chose the second entry (gateway, you cant see it) and followed the prompts for setting up permissions etc, for now using my own creds.  In the future , hopefully i'll use a non expiring id's creds once i feel like i can explain this flow of steps to the folks who would be giving me such an id.

when i come back in to manage/settings for the semantic model , pbi shows (i think) it being mapped to the connector instead of the gateway.  but when i look at semantic model lineage i see the gateway referenced.

i'm still a bit confused and unsettled by gateways, connectors, licensing etc etc.  but right now in my mind a gateway is kind of like a tunnel to which you enlist/attach 1 or more connectors.  The idea being that its more secure than just using a connector (i think this is called personal mode) without a gateway possibly reaching a server that isnt even online.  this connector is ssas and not live.  the ssas db is coincidentaly called semanticmodel. 

so is the gateway being used or not?  

[v-xuxinyi-msft · Accepted solution]

Hi @db042190 

Thanks for the reply from @lbendlin .

The following steps are for your reference:

You need to create different connections depending on the data source.

For more details, you can read related document link:

Add or remove a gateway data source - Power BI | Microsoft Learn

Please feel free to let me know if you have any more questions.

Best Regards,
Yulia Xu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin]

you do not require a gateway for Azure cloud data sources, including Power BI Semantic models.

You only require a gateway for on-premise data sources, like a genuine OLAP cube or a SSAS Tabular instance hosted in your own network.