Forum Discussion
DFG2 w/On-Prem SQL Server
- 2 years ago
Thank you for the follow-up. I have not utilized support. Want to exhaust every other option, first.
We reviewed info here: Adjust communication settings for the on-premises data gateway | Microsoft Learn
Most of the "solutions" is to add *.datawarehouse.pbidedicated.windows.net to the windows FW or Fortinet in this case, we can do that via a custom URL category on the Palos but very limited otherwise.
The hostname has a randomly generated "host" section (<random hostname>.datawarehouse.pbidedicated.windows.net). Feels like there is no limit to the number of these than can exist. Is there a limit and are they created for each workspace? One thought is that we could build a list of those FQDNs that are needed, as long as the IP doesn't change often. We could possibly create some sort of automated import of new ones....hoping MS has a better solution, just brainstorming other things we could do. There is a list of IPs, subnets actually but it's a lot.
Hi jcampbell474 ,
We haven’t heard from you on the last response and was just checking back to see if your query has been resolved. Please let us know if you have any further queries.
Hi jcampbell474 ,
Following up to check whether you got a chance to create a support ticket for the issue you have been facing. If yes please share the ticket details here as it would help us to track for more information.
Thank you.
- jcampbell4742 years agoHelper IV
Thank you for the follow-up. I have not utilized support. Want to exhaust every other option, first.
We reviewed info here: Adjust communication settings for the on-premises data gateway | Microsoft Learn
Most of the "solutions" is to add *.datawarehouse.pbidedicated.windows.net to the windows FW or Fortinet in this case, we can do that via a custom URL category on the Palos but very limited otherwise.
The hostname has a randomly generated "host" section (<random hostname>.datawarehouse.pbidedicated.windows.net). Feels like there is no limit to the number of these than can exist. Is there a limit and are they created for each workspace? One thought is that we could build a list of those FQDNs that are needed, as long as the IP doesn't change often. We could possibly create some sort of automated import of new ones....hoping MS has a better solution, just brainstorming other things we could do. There is a list of IPs, subnets actually but it's a lot.
- Anonymous2 years agoNot applicable
Hi jcampbell474 ,
Thanks for the update. Regarding your question about limit to the number of hosts, I have taken help from internal team. I will update once I hear back from them.
Appreciate your patience.