Documentation | AZExecute

AZExecute Docs

Practical docs for secure self-service operations

Explore how AZExecute helps teams govern Entra applications, handle application and permission requests, keep ownership in sync, automate operational work, and manage auto-shutdown across tenant-scoped roles.

Application requests, permission requests, and approvals

Synced ownership and administrator access models

Automation tasks, scripts, runbooks, and global variables

Auto-shutdown schedules and tenant governance

Choose your documentation path

Every section is implementation-focused and written for users, operators, and tenant administrators.

Getting Started

~10 min

Architecture, onboarding, installation, and access role setup before you automate.

Open Guide

Applications

~12 min

Manage app registrations, permission governance, secret rotation, and certificate lifecycle.

Open Guide

Auto-Shutdown

~8 min

Configure VM and VM Group schedules with cost-aware operational controls.

Open Guide

Automation Tasks

~18 min

Build reusable multi-step automations with parameters, event listeners, scripts, PowerShell modules, and execution history.

Open Guide

Administration

~11 min

Tune tenant-level settings for policy, backups, integrations, and governance.

Open Guide

API

~7 min

Authenticate and integrate securely with documented roles and supported endpoints.

Open Guide

Implementation Journey

Recommended sequence from first login to production-ready operations.

Step 1

Connect and assign access roles

Step 2

Review tenant system settings

Adjust base governance settings, automation defaults, and integration requirements before rollout.

Step 3

Build your first automation task

Create a multi-step task with scripts, parameters, and execution policies for predictable outcomes.

Step 4

Validate and run in production

Execute with history tracking, monitor outcomes, and iterate safely with audit visibility.

Common setup questions

Which role should start the implementation?

TenantAdmin should complete initial setup, consent, and governance settings. Operators then build and publish tasks, while Users execute approved self-service workflows.

Can AZExecute manage all app registrations in my tenant automatically?

No. Application management is scoped by ownership. AZExecute can only manage app registrations where its service principal is explicitly added as an owner.

Should we review system settings before building automation tasks?

Yes. Review tenant-level settings first so role behavior, governance defaults, approvals, and integration expectations are set before your first production task.

What is the fastest path to first value?

Import one application or configure one VM schedule, then create a small multi-step automation task and run it in a controlled scope before scaling out.

Where do we verify what happened after a run?

Use execution history and logs in the platform, and correlate with Entra ID audit/sign-in logs when needed for full operational and security traceability.

An unhandled error has occurred. Reload 🗙