Admin: Tenant Integrations
Tenant Integrations connect AZExecute to the systems that your automations, application governance, DNS workflows, and certificate deployments need to reach. They keep credentials, validation status, agent bindings, and provider metadata in one tenant-admin area instead of scattering setup across individual tasks.
Why Integrations Matter
AZExecute is most useful when it can safely bridge cloud resources, on-premises agents, service-management systems, DNS providers, and deployment platforms. Tenant Integrations are the trust and discovery layer for that work.
• They make task steps easier to configure because operators select a validated connection instead of re-entering credentials.
• They centralize validation state, so stale credentials or offline agents are visible before production workflows depend on them.
• They give administrators a clean boundary between platform setup and reusable automation design.
• They support the smart parts of AZExecute: dynamic dropdowns, output variables, incident creation, DNS updates, certificate deployment, and cross-cloud secret delivery.
Available Integration Areas
Cloud and Application Delivery
• Amazon Web Services: connect AWS accounts through OIDC federation and role assumption for AWS Secrets Manager and Route 53 DNS workflows.
• Vercel: connect Vercel teams so application integrations can update environment variables and optionally trigger redeployments.
• NetScaler: configure API-driven certificate deployment and binding for Citrix ADC / NetScaler targets when preview features are enabled.
Agent-Based Enterprise Systems
• Active Directory: bind a connected Windows agent to directory lookup and object-management automation.
• SCOM: use a Windows agent with the OperationsManager module to look up managed computers and control maintenance mode.
• Windows DNS: query and manage Windows-hosted or AD-integrated DNS zones through an agent that can reach the DNS server.
• Cisco Umbrella: run internal domain and destination-list automation through a selected agent.
Service Management and DNS Providers
• TOPdesk: create, update, assign, close, or classify incidents and changes from task steps, event listeners, and application request workflows.
• Simply.com: manage zones and DNS records for ACME DNS authorization and reusable DNS automation.
Agent-Based Integration Pattern
Several integrations intentionally run through an AZExecute agent instead of calling the target system directly from the web application. This is important for internal systems such as Active Directory, Windows DNS, SCOM, and network-restricted tooling.
1. Install and connect the AZExecute agent on a machine that can reach the target system.
2. Configure the integration and select that machine as the execution or lookup agent.
3. Validate the integration from the admin page so connectivity issues are caught early.
4. Use the integration in task steps, custom integration parameters, event listeners, or certificate workflows.
Recommended Setup Order
1. Enable any required tenant-level feature flags in System Configuration, API Connections, Automation Settings, or Application Settings.
2. Configure provider credentials or agent bindings from TenantAdmin - Integrations.
3. Validate the integration immediately and record any provider-side prerequisites in the integration description.
4. Use the integration in one small task or application workflow before scaling it into production automations.
5. Revalidate after credential rotation, agent migration, DNS/server changes, or provider permission changes.