Email: Azure Communication Services
Provision Azure Communication Services email and copy the connection string so your OptixLog deployment can send transactional mail through your own Azure tenant.
OptixLog sends transactional mail (invitations, notifications) through an email provider that you own. Credentials are pasted once, verified with a real connection test, and stored encrypted inside your deployment. Mail flows directly from your OptixLog instance to your Azure resource; no OptixLog-operated service is involved.
What you'll need
- An Azure subscription with permission to create resources.
Create the email resources
In the Azure portal create an Email Communication Services resource, then add a domain under Provision domains. Use the free Azure-managed domain (...azurecomm.net) to start, or connect your own custom domain and finish its DNS verification.
Connect the domain to a Communication Services resource
Create (or reuse) a Communication Services resource and link the email domain under Email → Domains → Connect domain. Sender addresses are managed on the domain, e.g. DoNotReply@<your-domain>.azurecomm.net; add more under MailFrom addresses if needed.
Copy the connection string
On the Communication Services resource (not the Email Communication Services resource) open Settings → Keys and copy the Connection string for the primary key. It looks like:
endpoint=https://my-resource.communication.azure.com/;accesskey=BASE64KEY...Connect it in OptixLog
In OptixLog open Management → Integrations → Email delivery (or the Integrations step during first-install onboarding) and pick Azure Communication Services. Fill in:
| Field | Value |
|---|---|
| Connection string | The full endpoint=...;accesskey=... value |
| Sender address | A MailFrom address on the connected domain, e.g. DoNotReply@example.azurecomm.net |
Click Verify. OptixLog signs an authenticated request against the resource's email API to prove the endpoint and access key work, without sending mail. Save to store the credentials encrypted.
Troubleshooting
| Error | Fix |
|---|---|
| Azure rejected the access key | Re-copy the connection string from Keys; if the key was rotated, paste the new one and save. |
| Send fails with a domain error | The sender address must belong to a domain connected to the Communication Services resource. |
| Custom domain won't verify | Confirm the TXT/SPF/DKIM records from the provisioning page are published in DNS. |
Email: AWS SES
Create least-privilege AWS SES credentials so your OptixLog deployment can send transactional mail through your own AWS account.
Email: SendGrid
Create a restricted SendGrid API key and verified sender so your OptixLog deployment can send transactional mail through your own SendGrid account.