October 28 & 29: Experts share their secrets on how to pass the Fabric Analytics Engineer certification exam—live. Learn more
My company has started discussing the use of MPE's in Fabric, for the sake of Spark workloads.
It is probably a minefield of bugs, so I wanted to move ahead cautiously. One of the primary features we would need is some way to connect to a "private link service" in our azure subscription. However I have not been able to make that work this morning, and nor have I found public documentation saying it is unsupported. Do they intend me to invest a week trying to make something work, when it is not even supported yet? I don't think the Fabric team cares about the time it takes their customers to struggle thru this sort of topic.
If anyone can refer me to Microsoft docs, please let me know. I found this discussion in the community:
https://community.fabric.microsoft.com/t5/Data-Engineering/InvalidRequest-when-adding-quot-Private-L...
... but I also hoped to also see a clear statement in the Microsoft docs that PLS is not available yet. I don't see that where I expected to find it:
https://learn.microsoft.com/en-us/fabric/security/security-managed-private-endpoints-overview#limita...
Please let me know. Any authoritative guidance would be appreciated.
Solved! Go to Solution.
I opened a case, and they pointed me to the list of currently supported endpoints here:
There are some unusual things in that list. Unfortunately private-link-service is not one of the available connection types as-of now.
It is really strange when Microsoft encourages customers to migrate their workloads to Fabric from Synapse, given the significant gaps that still remain in something as basic as network connectivity. I think it is very premature for them to be doing that. If I had to guess, they are still six to twelve months away from adding private-link-service to Fabric.
We may have to find a workaround, to run the small portion of the python activity that relies on connectivity to a private-link-service.
I opened a case, and they pointed me to the list of currently supported endpoints here:
There are some unusual things in that list. Unfortunately private-link-service is not one of the available connection types as-of now.
It is really strange when Microsoft encourages customers to migrate their workloads to Fabric from Synapse, given the significant gaps that still remain in something as basic as network connectivity. I think it is very premature for them to be doing that. If I had to guess, they are still six to twelve months away from adding private-link-service to Fabric.
We may have to find a workaround, to run the small portion of the python activity that relies on connectivity to a private-link-service.
User | Count |
---|---|
11 | |
3 | |
3 | |
3 | |
2 |
User | Count |
---|---|
18 | |
11 | |
7 | |
7 | |
4 |