Application Requests

This page explains how to submit complete Application Requests in AZExecute so approvals and delivery move faster. It focuses on what requestors should enter, what approvers look for, and how to avoid common reasons for delays.

Some options and requirements are managed centrally by your organization. If a field appears required, hidden, or read-only, that is expected tenant policy behavior.

How To Use This During a Request

When you submit a new Application Request, these four areas affect outcome and approval speed: General, Metadata, Request Context, and Ownership. Use them as a checklist to submit a complete, review-ready request.

General affects request availability and credential lifetime limits

Metadata captures business, security, and support context

Request context defines the environment and team ownership you select

Ownership requires maintainers so applications do not become unmanaged

General: What Users Should Expect

General controls can affect whether request submission is available, whether approvals are required, and which secret/certificate lifetimes you can choose.

• If request creation is disabled, contact your platform team for onboarding path

• If approval is enabled, include detailed business justification to reduce back-and-forth

• Secret lifetime choices are capped by tenant policy

• Certificate lifetime choices are capped by tenant policy

Impact: If requested lifetimes are longer than policy allows, you must select lower values. This is expected and helps enforce credential hygiene.

Metadata: How To Fill It Well

Metadata provides the context approvers and operators need to validate risk, route ownership, and support your workload. Complete, precise metadata is the fastest way to reduce request delays.

If your tenant needs policy changes (for example additional fields or approval behavior), ask your administrators to review Administration settings.

Always Required: Business Justification is always included and required for every application request.

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

If a field is marked required, you must provide it before submission. Missing or vague metadata is one of the most common reasons requests are delayed.

Request Context: Choosing Correctly

Environment and Department/Team selections are used for governance, routing, and reporting. Choose values that match real ownership and deployment intent.

Environments

Pick the environment that reflects actual runtime usage (for example Development, Test, Production).

Departments

Pick the team that will own operations and incident response for this application.

Hidden meaning: These values are often used in dashboards, ownership reports, and triage filters. Inconsistent choices reduce operational visibility.

Ownership: Why It Matters for Users

Every application needs clear ownership to support rotations, permission review, and incident handling. During request flow, expect ownership rules to enforce minimum maintainers.

• Add co-owners early to avoid submission or approval delays

• Ownership checks can trigger governance notifications if requirements are not met

• Some administrator assignments may be applied automatically by policy

Impact: Strong ownership setup improves approval speed and reduces long-term operational risk for your application.

Application Request Ownership Assignment

Recommended User Workflow

1. Start request with accurate app purpose and business justification

2. Complete all required metadata with concrete technical details

3. Select correct environment and responsible team

4. Add required co-owners and verify operational contacts

5. Submit and monitor approvals/feedback until completion

Pro tip: The best requests are explicit about owner responsibility, data access intent, and production impact. This reduces review cycles significantly.

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

info@azexecute.com

. Our support team is here to help you.