@merill@IAMERICAbooted you could add a security attribute to trackownership. But a sponsor would be good to. But then again let them be assigned to AU/RMAU’s
@I_Am_Jakoby Can’t wait to see it! I’ve been following you since you first stepped into @PowerShellpod! It feels great to see the success you are having now!
@PrzemyslawKlys isnt that mosty hardware dependant, ie running openai oss. Its the context size that consuming all the vram and overflows to ram/cpu if you only have 16gb vram. Lowering the context size works, but then you loosing the context. And ofc depends om the amount of parameters to
@NathanMcNulty in another perspective, if you create your azure rbac and use accesspackages you could add azure powershell/cli as a resource to add those who always should have it, then as you said request when needed for maybe lesser permissions etc
@NathanMcNulty And on another side not i know users that is using powershell as data manipulation/processing and using importexcel etc. And of they wasnt allowed with that, is installing python any better to do the same thing ”just cause it isnt powershell”? :)
@NathanMcNulty I agree that constrained language mode, nuking powershell 2.0 etc is a good help on the security posture and signing scripts and so forth. And even JEA is a great thing if you implement that.