Environment Libraries missing or not found

[Kesahli]

As of today, when creating a new environment, Built-in Libraries are empty and all Public Libraries (Add from PyPi) show as "Library is not found". 

Are there any issues with this as a reault of the Native Execution Engine going to GA possibly? I can add this to an existing environment with a library, and I can create a new environment with Native Execution Engine, but I cannot add libraries, despite them showing in the drop down list when searching. 

Multiple workspaces. Am logged in as Workspace admin. 

[Anonymous · Accepted solution]

Hi @Kesahli,

Thanks for reaching out to the Microsoft fabric community forum. From what you’ve described it looks like new environments aren’t able to resolve or install public PyPI packages, while existing environments that already have libraries still work. Let’s go through a few quick checks to narrow downthe issue.

* Open an incognito/private browser window (or a different browser) and try adding a library to a newly created environment. This rules out a browser cache/UI issue.

* Create a brand-new environment, type the package name in the Public Library search, and when it shows in the dropdown try entering an explicit version (for example package==x.y.z) instead of the default. Note the exact error text and timestamp. Try the same steps in another workspace as you said you have multiple and confirm whether the behavior is identical.

* If you have the option, try adding the same package via Custom Library (upload a wheel/whl or a private package) to see if uploads work while PyPI lookup fails.

* Please confirm whether your tenant/network blocks outbound access to pypi.org or to the PyPI simple index. Some orgs restrict egress to external package repos and that will cause “Library not found” even though the UI shows the search suggestion. If you’re unsure, ask your network/security team to verify connectivity from your Fabric environment to pypi.org.

* Confirm there aren’t any tenant or admin settings that block installing public PyPI packages (if you don’t have tenant admin access, please ask your tenant admin to check Fabric/Power BI admin settings related to external package installs).

* Check Service Health / Fabric status for any current incidents that might affect library indexing or PyPI access.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.

[Kesahli]

Thanks Hammad. Your help is greatly appreciated.

[Anonymous · Accepted solution]

Hi @Kesahli,

Thanks for reaching out to the Microsoft fabric community forum. From what you’ve described it looks like new environments aren’t able to resolve or install public PyPI packages, while existing environments that already have libraries still work. Let’s go through a few quick checks to narrow downthe issue.

* Open an incognito/private browser window (or a different browser) and try adding a library to a newly created environment. This rules out a browser cache/UI issue.

* Create a brand-new environment, type the package name in the Public Library search, and when it shows in the dropdown try entering an explicit version (for example package==x.y.z) instead of the default. Note the exact error text and timestamp. Try the same steps in another workspace as you said you have multiple and confirm whether the behavior is identical.

* If you have the option, try adding the same package via Custom Library (upload a wheel/whl or a private package) to see if uploads work while PyPI lookup fails.

* Please confirm whether your tenant/network blocks outbound access to pypi.org or to the PyPI simple index. Some orgs restrict egress to external package repos and that will cause “Library not found” even though the UI shows the search suggestion. If you’re unsure, ask your network/security team to verify connectivity from your Fabric environment to pypi.org.

* Confirm there aren’t any tenant or admin settings that block installing public PyPI packages (if you don’t have tenant admin access, please ask your tenant admin to check Fabric/Power BI admin settings related to external package installs).

* Check Service Health / Fabric status for any current incidents that might affect library indexing or PyPI access.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.

[Kesahli]

Thanks Hammad, much appreciated. I hadn't though of network blocks but that seems to be the case. I can see and install packages from the public libraries if I use a non-priveleged machine.  
On our priveleged machine, which has recently been restricted from accessing internet sites in general (apart from explicit domains), I am unable to see the list of Built-in libraries either - would this be expected behaviour or should I at least be able to view the list?

[Anonymous · Accepted solution]

Hi @Kesahli,

Yes, that behavior is expected. The Built-in Libraries list is retrieved live from the service each time you open that pane. If the machine doesn’t have outbound access to the Fabric service endpoints that host that list, it won’t be able to display them — so on a restricted/privileged machine you’ll see it as empty.

To fix both the built-in list display and the ability to add from Public Libraries (PyPI), your network/security team will need to allow outbound access to the Fabric service domains and to pypi.org (and the PyPI package index URLs). The exact list of required endpoints is published here:
Add Fabric URLs to your allowlist - Microsoft Fabric | Microsoft Learn

Once those endpoints are whitelisted, you should be able to see the Built-in Libraries list and install public packages from any machine.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.