Web connection not recognised as cloud source when refreshing data

[SteHext]

Whenever a user publishes a report to the Power BI Services which uses a web connection, the dataset settings expect it to be mapped in a gateway (as if it is not seen as cloud based). Other connection types to cloud sources work fine, and this has not been an issue in the past.  We are forced to use a gateway even when a web connection type is added to a report with other cloud based connection types, which were working (but issue is only for the web type connections).  We have tested this with connections to various sites.  Has anyone else had this issue / can anyone help?  Example screen shots below:

We get this in gateway connection when a web connection type is added:

Instead of 

It's strange as the gateways still see the connections as optional:

It all works if the web source is mapped, but this would add unneed load on the gateway if all our creators had to do this.

[v-robertq-msft]

Hi,

According to all my tests and research, if your data source does not contain any on-premise data source(merged with the cloud data source is also not allowed). Then the gateway option is optional for you. I think you should double-check if the data source contains any data from on-premise carefully.

https://docs.microsoft.com/en-us/power-bi/connect-data/refresh-scheduled-refresh

Thank you very much!

Best Regards,

Community Support Team _Robert Qin

[SteHext]

Hi Robert @v-robertq-msft , 

Thanks for the response, but even with one web data source we are being forced to use a gateway and are unable to turn the gateway option off or access the data source credentials. Which is really strange. Previously uploaded reports which just have web connections work fine its only happening on new ones. 

Example screen shot below showing one web connection. 

In this example we have just  gone to the bbc sports website and picked the first table on the premier league tables page, no other transformations or mergers. 

[SteHext]

Turns out this Issue was due to how I was connecting to the data. web.page function needs to use a gateway now and so does web.conetnts or webbowsercontents if its getting the data from a html page.  Other web functions like JSON work fine

Thank you to Satyam in support for spotting this.  Please see extract below. 

Every use of the Web connector to get data from an HTML page requires the use of an on-premises data gateway when published to a Cloud service.

Screenshot for reference:

Also providing you with a documentation for reference:
https://docs.microsoft.com/en-us/power-query/connectors/web/web-troubleshoot#using-a-gateway-with-th...

[v-robertq-msft]

OK, thanks for your acknowledgment!