Dataflow Domains are Changing?

[BillyT_350]

Hello, a month or so ago I posted a question and filed ticket 2308040040007295 looking for help with a sudden lack of access to our PBI dataflows. In the end, this turned out to be some sort of weird DNS redirect issue for which our network guy had to do some manual DNS redirection. Now we seem to be having this issue again, but this time the target address for some of our dataflows have changed from

https://wabicancencdsa.blob.core.windows.net

to

https://wabicancencdsap1.blob.core.windows.net

Can anyone from the MSFT side explain what is happening here, and why?

My concern is that I do not want to have to play whack-a-mole every time our dataflow domains randomly change. Ain't nobody got time for that. I need a permanent and dynamic fix for this problem, or at the very least I need to understand what is going on here so that I can be prepared for and be able to anticipate when these changes will occur in the future.

And before you ask, no, I will not file a ticket on this this because I don't want to have to explain five times why Ctrl+Alt+Delete will not solve this issue. I wasted weeks going back and forth with support on this issue the first time, and they were never able to figure it out. It wasn't until our network guy was working with our MSFT partner on an unrelated issue that he noticed a similar problem, and when I brought this to his attention he recognized the similarity. I will file a ticket if MSFT wants to escalate the issue to someone who actually understands how this works.

[lbendlin]

Understand your sentiment but raising the new ticket is the only way to get traction. You don't have to like their process but it does (eventually) yield results (most of the time).