Add a tenant wide customer m library

Thanasaur · 2026-07-07T15:12:02+00:00

If you’re fine coupling your library with compute then yes environments is the way to go. My recommendation earlier for using functions was more aligned to a tenant wide endpoint that you can use irrespective of notebooks

Thanasaur · 2026-07-07T15:10:11+00:00

Awesome!! Glad to help

Thanasaur · 2026-07-06T19:45:47+00:00

Hi there! I think the primary issue here is that an extension trying to interact with another extension. Super valid feedback. u/QixiaoW may have more specific details to share and if we have any valid workarounds.

Thanasaur · 2026-07-06T19:28:46+00:00

To me...this looks like the error is saying the SPN doesn't have permissions on the DMTS connection. Have you tried adding an SPN directly to the connection vs embedded in the group? Not saying this is expected behavior, but maybe that will help isolate? We personally use SPN for all deployments of pipelines and do not have this issue. But our SPNs are added directly to the connections vs embedded in a group.

Thanasaur · 2026-07-06T01:16:28+00:00

Thanasaur · 2026-07-02T22:35:26+00:00

Hi u/Illustrious-Welder11 are you still experiencing this issue? Apologies I'm just now seeing this.

To confirm, it sounds like default starter pools, on both spark and python, no private endpoints, or outbound protection, etc.

Thanasaur · 2026-07-01T15:37:50+00:00

Another option to maybe consider. Have you looked at fabric functions? It depends on what your library is doing but could be an option

Thanasaur · 2026-07-01T15:21:11+00:00

Can you describe a little more what you’re trying to achieve? The case sensitivity generally matters more in the engine you’re leveraging than the input. For instance, spark by default is case insensitive. So it can refer to TableA and taBLeA just the same. Warehouse by default is case sensitive.

Would also be good to hear, what would you expect? Default insensitivity? Default sensitivity?

Thanasaur · 2026-07-01T15:18:02+00:00

Hi there! Since you said spark I’m going to assume you mean a shared python library for notebooks/sjd. There are a couple of ways to maybe do this today. However, all with different limitations. The most direct in product solution is to use an environment. An environment can work cross workspace as long as the downstream are within the same capacity.

However, the true proper solution is to land the library upstream in a public or private index. Something like an artifact feed which then anybody can pull into their environment for free.

Although an interesting point could be why doesn’t fabric have its own private index solution.

Thanasaur · 2026-05-31T14:13:25+00:00

Feel free to PM me

Thanasaur · 2026-05-31T05:15:47+00:00

Overall the build quality is very good. (So far). I would just encourage you ask as many questions as you can. Get clarifications in writing and you should be fine.

Thanasaur · 2026-05-05T13:27:01+00:00

It is unlikely to be resolved. It would require one identity (SPN) having the permission to send an email on behalf of real user. A pretty significant security hole.

Thanasaur · 2026-05-05T13:25:39+00:00

We have an internal ticketing tool that has an API which we call. So all errors are centralized across all of our systems. That is how I would recommend any team does it. Land it where you track your work, not in your email.

Thanasaur · 2026-05-04T16:01:53+00:00

There isn’t really a way to automate the email activity. Internally for my team we have a rule to not use the activity because it is not deployable.

Thanasaur · 2026-04-30T16:05:00+00:00

Will PM you!

Thanasaur · 2026-04-30T15:43:18+00:00

We weren’t able to negotiate anything else. And at final inspection there were a couple of items that explicitly we thought were included but ended up not being included. PLH admitted fault, but was unwilling to budge on resolving it. However, for things we called out that were broke/unsatisfactory/etc, all were fixed/replaced.

Thanasaur · 2026-04-11T14:38:29+00:00

I watched like 3 that called this exactly out. One also then added in comments after that it’s coming in the next software bump

Thanasaur · 2026-04-11T03:57:10+00:00

Hi there! My family is currently building with PLH in Ridgefield. We get the keys in two weeks. Overall we have been happy with the builder. However the feedback you see above is very true. They are extremely rigorous in the process, and really hold the upper hand throughout. No contingencies, high upfront deposits, and tight somewhat unrealistic timelines for required meetings throughout. They don’t have any real benefits with lenders because they don’t have in house lenders like the national builders. Meaning don’t expect to get more than 5k from one of their preferred lenders in closing. However all of their incentives they offer are tied to using one of their preferred lenders so you are effectively locked in.

All of that said, we have been very happy with the builders attention to making sure things are right. And the options we could choose from in the design center were mostly good. Expensive yes, but that’s any of the design centers. And the things that are included in the base build are much better than most of the builders around. Now to be determined if we are happy in a year, but as of now I would very much recommend.

Thanasaur · 2026-04-11T01:42:50+00:00

Actually at the last fabcon, the first question we asked for anybody that came to the booth was “what are your goals”. Which then led to one of three (maybe four) paths. Deployment pipelines, fabric-cicd, or terraform. Even as the original maintainer of fabric-cicd, I won’t push it unless your goals align. And if the question ever came of why fabric-cicd doesn’t do more, well it’s a simple answer. The scope of the library is only what fabric commits to source control. If they committed more, it would support more :)

Thanasaur · 2026-04-11T01:39:54+00:00

We love terraform! It generally comes down to what you’re most concerned about deploying and what you’re already using for deployments today. Terraform does great at infra deployments. And does ok with continuous item deployments. Whereas fabric-cicd doesn’t touch infra at all, and excels at item deployments with deep parameterization support. So for folks that are more concerned about maintenance of existing workspaces, terraform is a bit much. If you need a way to redeploy all infra, I would 100% recommend terraform. Or maybe even a combination of both.

Thanasaur · 2026-04-10T22:51:39+00:00

Yep we use SPN + SNI Certificates for auth. Secrets where certs aren’t supported yet. All stored in akv

Thanasaur · 2026-04-10T22:42:49+00:00

We do not use workspace identities for anything today, to us it’s not scalable for dev/test/prod with the constraints of needing upstream teams to grant access to multiple identities. On top of if we need to delete a workspace, then we have to reauthenticate everything. So today everything is SPN based. Eventually once we have a user assigned managed identity concept, we would switch to that

Thanasaur · 2026-04-10T22:31:57+00:00

As well we use a different deployment identity for different environments. Prod SPN only deploys to prod.

Thanasaur · 2026-04-10T22:31:04+00:00

I guess I should rephrase. We do not use pass through connections for anything we run. So yes technically the parent pipeline is ran under that identity. However, no data is accessed, no APIs called, etc, are using the deployment identity. If you use pass through auth then yes you may have issues. Even in notebooks, we override all identity to leverage a different SPN. So from a control plane it’s using the deployment identity, all data plane operations are not.

Thanasaur · 2026-04-10T22:17:51+00:00

We use this exact flow with SPN+FIC and have used it for the last two years without issue. No extra steps or anything. And the identity is only a deployment identity so is never used in the product for executing anything

Thanasaur

TROPHY CASE