Restrict serverless options to a subset of users

[RicksDB]

Hi,

It seems as if there is no way to restrict serverless options to only only a subset of users. If a user has no budget policy, I assumed he could not run a serverless workload. Unfortunately, this is not the case and it will become a cost governance issue. For now, we are trying enable serverless only for some service principals running certain jobs but by doing so, we bypass all compute policies we had in place.

I am sure I am missing something. If not, is there any plan to fix this?

Thanks!

[Alberto_Umana]

Hi @RicksDB,

You are correct in identifying a gap in the current serverless compute options regarding user restrictions and budget policies. As of now, there is no direct way to restrict serverless compute options to only a subset of users. If a user does not have a budget policy, they can still run serverless workloads, which can indeed lead to cost governance issues.

However, there are ongoing efforts to address these concerns. The introduction of budget policies for serverless compute, which is now available in Public Preview is one of them. I will check internally what other features are suggested.