We have faced this bug. I hope this would get fixed...

Hi,

we have the same issue in the same region as well. Dropping the database and recreating did not work. The views worked for a moment in between but then stopped working again.

We don't use private endpoints but we do use the firewall.

I have noticed that after waiting for some random period time (for example 20 minutes, but it seems to keep changing) I can make some OPENROWSET selects again. However, when calling one particular OPENROWSET it breaks again and nothing works. I don't believe that there should be anything special about this one openrowset. It is in the same datalake and container as the ones that work.

Hi,

we have the same issue. We a,so dropped the database and recreated it but it has not helped. Our views have worked for a few times in between but stopped working again.

That would be great, thanks! Using AD would be the preferred solution as well.

I have used them in a case. If I understand you correctly the suggestion is not to use special characters in a case but the far easier solution would be for special characters be allowed and then ADF cleaning the case before using it as a "name". Or the name being something else than the case. I believe this was the case before (no pun intended). For example, I would imagine quite a few need to use "/" or paths as a part of their case.

I have mitigated the issue by using replace for special characters but this is not a good long term solution.

Hi,

I can add that also letters like 'ä' and 'ö' do not work as a part of cases.

Still not working and haven't found a work around other than not changing data flow or running the data flow with a trigger (and having no preview).