[Feature Request]: Modification to 'Allow users to send from their alias addresses' to allow for disabling for override

[HappyEarthDay]

Please confirm:

• I have searched existing feature requests (open and closed) and found no duplicates.
• **me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

We want to set this Allow users to send from their alias addresses standard by default, but 5% of our clients do not want this. Our options are:

• Remove the settings from standards templates and set it manually
• Exclude the clients from CIPP, automatically removing them from all standards
• Exclude the clients from the standards template that is deploying the standard, which also contains other vital standards that they would miss out on
• Create a separate standard template just for this standard, set it to, and explicitly exclude the tenants. This is what we ended up doing, but with this method, we could end up with a standard template for each and every standard we want to set, which is not ideal or easy to manage.

Some standards, like Quarantine notification interval, allow us to specify a different interval, which we can use to override in a separate standards template. The problem with this **Allow users to send from their alias addresses**standard is that it can only be set to Enabled and not Disabled. We'd like the ability to set this standard to Enabled or Disabled so we can use an override at the tenant level for specific clients as we do for other standards.

Benefits for MSPs

Gives the granularity we need to be able to effectively manage standards template overrides in the same way.

Value or Importance

This is nice to have, but having consistency in the methods we use to manage standards templates and ability to easily override is essential to our organization.

PowerShell Commands (Optional)

No response

[KelvinTegelaar]

I think this would work by setting a defined standard for that tenant to report only, I haven't tested that however. :)