github-actions[bot]
commented
1 month ago This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.
Resubmitting w/our sponsorship setup correctly (sponsoring as NeighborhoodIT-LLC):
We used to use MSPMagic before they went under in January of this year. One very helpful feature they had was the ability to use variables in the various policy templates. There was a mix of variables available, both auto-created from the client tenants (e.g. tenantID) and manually created by us (e.g. Duo tenant ID for use in CA policies, or Sharepoint library IDs to auto-sync). This allowed for editing the template's JSON to insert the variables which would then lookup those values upon deployment (and re-deployment at nightly intervals).
This allowed us to rapidly deploy new templates and update them all across our clients without having to enter the tenant's Azure portal and manipulate them by hand. Having the ability to leverage common tenant variables in policy JSON and create our own variables would add some great flexibility & automation options on deployments
PowerShell commands you would normally use to achieve above request
No response