Skip to content
Jooosi
Account
JM Jooosi Mail

Azure

Browse documentation
Overview
Contents
On this page
  1. Before you begin
  2. Supported transport and settings
  3. Create the connection
  4. Verify delivery
  5. Webhooks
  6. Troubleshooting

This profile sends through Azure Communication Services Email using its API transport. It needs the ACS resource name and an API key for that resource. The API transport needs the resource name and key for the Azure Communication Services account you will use.

Before you begin#

Have a provider account and credentials for the transport you chose. Copy credentials from the provider’s own console or account settings; never put secret values in documentation. Check the provider’s documentation for account requirements and sender acceptance.

Supported transport and settings#

  • Transport scheme: azure+api.
  • Required settings: Azure ACS resource name (text) and Azure ACS API key (secret).
  • Optional settings: Azure API version is optional; blank uses the profile transport default. Disable Azure tracking is optional and defaults to false.

Jooosi Mail marks password, token, key, and private-key fields as secrets in the connection form. Enter only the fields shown for the selected scheme.

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select Azure in Profile.
  3. Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
  4. Review the sender, routing, and advanced settings for this connection.
  5. Choose Create connection to save it.

For the shared form workflow, see Connect a provider.

Verify delivery#

Follow Send a test email and send to a mailbox you can check. A test sends a real email. Check the mailbox and Jooosi Mail → Logs for the attempt status.

Webhooks#

This profile does not declare provider webhooks. Use Jooosi Mail email logs to review delivery attempts.

Troubleshooting#

  • Check that the resource name and API key belong to the same Azure Communication Services resource.
  • If connection creation succeeds but a test fails, inspect the Jooosi Mail log entry and compare the selected API version and tracking setting with your ACS setup.

Provider reference: https://learn.microsoft.com/en-us/azure/communication-services/concepts/email/email-overview.