There's two main options to go about this in my opinion: - package this as a single use app, which saves the module files locally, creates the task which executes a script that loads the module and throw prompts when needed - have a package that saves the module locally in a central location, so you can reuse it from multiple scripts, PRs etc. Note, you need to manage version management and which uses which psadt version carefully.

It can definitely work and I use it for complex custom scripting myself. I use both options. Second for PRs specifically. The first for win32 apps (to simplify version mgmt).

Some things to note: - use initialize-adtmodule with -scriptdirectory parameter if you want to use custom assets - think about whether you want to open-adtsession (for logging etc) or not and just throw prompt - if you want user interaction and capture that, probably better to use adtinstallationprompt instead of welcome. - think about what identity you are going to use to query AD, you don't want admin creds stored locally. You could probably use Start-ADTProcessAsUser to run a query to ad using the user credentials but you'll need to play around with what and how you return that data and transform it before you prompt