I keep running into this and I need to know that the PowerApps team is aware/working on it.
It is not possible to create apps with CRITICAL location-based services because Location.Latitude and Location.Longitude do NOT work in the browser.
I've had to abondon 3 project requests this month that:
Search for the nearest hospital, the nearest cross-street, the nearest company asset, etc. based on users Lat/Long because of this.
Its no problem using Azure Maps (or internal) APIs to findthese things and bring back some results, but as identified in my tests here, Lat/Long does not work unless device has sensors. This causes my VPN users to appear in a centralized location (where our VPN servers reside) and thus bring back ERRONEOUS results. This is not a good look for things like hospitals, nearest cross-street (for emergency access) and company assets. I'm advocating for some way to deal with this in PowerApps (choose "Region Settings" or the like) or the removal of Lat/Long capabilities from Browser-based PowerApps (similar to offline storage) until this is addressed.