Admin: Application Settings

Admin: Application Settings Governance

Use Application Settings to define tenant-wide guardrails for new application requests, metadata quality, ownership requirements, and secret/certificate governance in AZExecute.

Governance Objectives

• Improve request quality with consistent metadata requirements

• Enforce credential lifetime constraints for stronger security posture

• Require ownership coverage to prevent unmanaged applications

• Standardize environment and department classification

Metadata Strategy

Start with a minimal required set, then expand mandatory fields as your governance maturity increases.

• Keep Business Justification required for all requests

• Require Environment and Department/Team for reporting and ownership routing

• Require Elevated Permissions Justification when elevated access is enabled

• Require Contact Email for operational follow-up and incident response

Review required-field impact with application owners before enforcing additional required metadata to avoid request friction.

Available Metadata Fields

• Business Context: Project Name, Department/Team, Environment, Business Criticality, Intended Audience, Expected Go-Live Date

• Requirements: Technical Requirements, Data Access Requirements

• Compliance & Contact: Compliance Notes, Requires Elevated Permissions, Elevated Permissions Justification, Contact Email, Contact Phone

Recommended Rollout

1. Configure settings in a maintenance window

2. Validate with test requests from a non-admin account

3. Announce changes to application owners and requesters

4. Revisit required metadata quarterly based on audit findings

Validation checklist: test a new application request, verify required-field validation, verify environment/department picklists, and confirm ownership defaults are applied as expected.

If you encounter any issues or need further assistance, please contact us at

info@azexecute.com

. Our support team is here to help you.