Admin: Operations & Audit

Tenant administration is more than settings. AZExecute also gives administrators operational views for user access, pending requests, security reporting, tenant statistics, and audit logs. These pages help teams understand who can do what, what changed, and where governance attention is needed.

Use these pages when you need to review tenant health, investigate activity, onboard users, validate access boundaries, or inspect permission exposure.


Administrative Work Areas

Users: review tenant users, roles, and user-level access state.

User Requests: handle access or onboarding requests that require tenant-admin attention.

System Access: review the roles and access model that controls what users, operators, and tenant admins can do.

Statistics: inspect tenant-level usage and operational metrics.

Logs: search tenant activity and troubleshoot operational events from a central audit trail.

Permission Scanning: create and review application permission reports so administrators can see granted scopes, exposed scopes, and security scan output.


How This Supports Governance

These operational pages make AZExecute smart to use because they connect self-service with control. Users and operators can move faster, while tenant admins still have a way to inspect access, understand changes, and catch risky permission patterns.

• Use user and access views before rollout to verify who should be able to request, operate, publish, or administer.

• Use logs when investigating task runs, application changes, request approvals, credential updates, or failed integrations.

• Use statistics to spot growth, adoption, and areas that may need cleanup or more automation.

• Use permission scanning before approving sensitive application requests or when reviewing existing application exposure.


Recommended Review Rhythm

1. Review pending user and application-related requests daily or as part of your service desk workflow.

2. Check logs after changing tenant settings, integrations, approval policy, or automation schedules.

3. Run permission scans before major governance reviews and after onboarding high-privilege applications.

4. Use statistics during monthly platform review to identify stale applications, underused features, or automation opportunities.

The goal is not to slow operators down. The goal is to make high-trust self-service measurable, reviewable, and easy to explain later.


An unhandled error has occurred. Reload 🗙
An unhandled error has occurred. Reload 🗙