[GH-ISSUE #2203] [Feature Request]: Use {tokens} in Standards (and elsewhere?) #1137

New issue

Closed

opened 2026-03-02 13:41:53 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 13:41:53 +03:00

Owner

Originally created by @myitguycorp on GitHub (Mar 8, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2203

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.

I would love to be able to use tenant tokens, e.g. {tenantname} or {tenantdomain}, when editing standards.

e.g. sending all security emails to the same generic@mycompany.com email means I'm going to receive a lot of generic Microsoft emails that fail to mention which Tenant this is about.

However, I if could specify that my Security Contact email is {tenantdomain}@reports.mycompany.com, then each Tenant would end up delivering email to its own email address. I could then identify quickly which tenant this is for by looking at the recipient address.

Thanks!

PowerShell commands you would normally use to achieve above request

No response

Originally created by @myitguycorp on GitHub (Mar 8, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2203 ### 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. I would love to be able to use tenant tokens, e.g. {tenantname} or {tenantdomain}, when editing standards. e.g. sending *all* security emails to the same generic@mycompany.com email means I'm going to receive a lot of generic Microsoft emails that fail to mention which Tenant this is about. However, I if could specify that my Security Contact email is {tenantdomain}@reports.mycompany.com, then each Tenant would end up delivering email to its own email address. I could then identify quickly which tenant this is for by looking at the recipient address. Thanks! ### PowerShell commands you would normally use to achieve above request _No response_