on
RE:
Quick heads up
It has been quite some time, but I just read a warning article online about microsoft.com and felt compelled to email you guys to disprove this nonsense.
It appears like there's some rumors circulating that could be potentially damaging.
Knowing how fast misinformation can spread and hoping not you to be taken by surprise, I thought it best to inform you.
Here's where I came across the info:
https://ibit.ly/JOeyW
My hope is it's all a simple confusion, but it seemed prudent you should know!
Wishing you all the best,
Dian
RE:
We had the same problem. The moment we customize the node with PyPi packages, we loose the StarterPools instant start feature and go back to old 3-4 minute start time.For sometime, used the pip to install the packages from inside the notebook.And one file day, all ETLs failed stating the %pip magic commands disabled inside pipeline. Finally i managed to install the pip packages into Lakehouse files space like below!pip install googleads -t /lakehouse/default/Files/PyPi Packages/and then in the notebook i add below line to include the Lakehouse folder into syspath so the package can be imported like local installed package.import syssys.path.append('/lakehouse/default/Files/PyPi Packages/')This is a workaround to avoid high start time and still work with custom packages.Hope there will be some native fix for this in the future fabric runtimes.
RE:
This information would be very helpful, and save a lot of time.
RE:
I am surprised that this is not on the Fabric roadmap. Would be nice to know when Microsoft plans to fix this issue.
RE:
I think its the most important functionality for pipelines.
RE:
Having keyvault technology baked into Fabric wouldn't go amiss either - for those of us who have a lot of political capital to navigate where spinning up Azure resource is concerned ;-). Also surprised this isn't gathering more votes quicker.
RE:
Not every role is as clear cut as the experiences present so having this feature is quite significant. Surprised this wasn't standard from Day 1.
RE:
This would be one step closer to something good. Connection management in general could do with lots of improvements..... but they are separate ideas :-)
RE:
Also, the guest users (if Admin) should receive emails whenever an access request is raised. The guest users (if admin) should be able to add emails in case of semantic model refresh failure.They should also be given an option to change the contact. Major loopholes are observed when B2B guest users are the admins of workspaces. In case of multi tenant organisations, the guest users are allowed to publish content to another tenant using a guest identity, be the workspace admin and dataset owners, but are not allowed to give access to another users - This restriction needs to be removed.