Egress charges from scheduled refresh against source in same Azure region

We have been careful in tracking which region our Power BI tenant is in and placing the various scheduled refresh and live connect data sources in the same Azure region. Unfortunately our Azure subscription is still charged for egress bandwidth even though the data is not actually leaving the Azure region.

Now with regular Azure services, some North Central US VM in an Azure subscription owned by Company A can download a CSV from a North Central US blob storage account in a different Azure subscription owned by Company B. Company B will not be charged egress bandwidth since the data stays inside North Central US.

For some reason bandwidth to Power BI, even with my Power BI tenant is in the same Azure region gets charged to my Azure account. From what I can tell, this happens 100% of the time.

Please change this. For many companies, this egress charge adds up to a significant charge. For public content pack providers hosting their API on Azure, this egress charge definitely adds up.