Automations and connectors

Use these guides to build reusable operations, schedule them, route their results, and connect all 18 implemented external destinations.

Automation workflows

Connector workflows

Start with Manage connector lifecycle. Provider recipes follow the same categories as the connector gallery:

The implemented type identifiers are teams, slack, outlook, email, jira, servicenow, pagerduty, splunk, grafana, securityhub, xsoar, sumologic, crowdstrike_ngsiem, servicebus, sqs, s3, logicapp, and webhook.

Test versus Send test

Test is configuration-only or a lightweight authentication/read probe. It does not intentionally create tickets, messages, incidents, findings, queue messages, or storage objects. A successful configuration-only test proves only that required values are present.

Send test performs a real delivery and can have downstream effects. The UI and API support it only for this allowlist: Teams, Slack, Email (SMTP), Outlook, Webhook, PagerDuty, Splunk, Grafana, Logic Apps, Sumo Logic, and CrowdStrike Next-Gen SIEM. The button is not available for Jira, ServiceNow, XSOAR, Service Bus, SQS, S3, or Security Hub; use each guide’s safe verification procedure instead.

Permissions

Connector management requires connectors.manage. Feature pages list their own permissions. Use least-privilege provider identities and non-production destinations while validating a new integration.

Table of contents

Back to top

Azure Support Agent is open source under the MIT License.

This site uses Just the Docs, a documentation theme for Jekyll.