# strapi-provider-email-azure > Strapi Email provider for Azure Communication Service Latest version **1.0.4** (published 2025-03-30) · MIT license · 0 weekly downloads ## Install ```sh npm install strapi-provider-email-azure pnpm add strapi-provider-email-azure yarn add strapi-provider-email-azure bun add strapi-provider-email-azure ``` ## Health **Score 25/100 (F)** — status: maintenance-mode. Positive: no vulnerabilities. Warnings: low downloads; no types; no esm support. Negative: stale; low maintenance score. ## Facts | | | |---|---| | Version | 1.0.4 | | Published | 2025-03-30 | | First published | 2023-04-24 | | Weekly downloads | 0 | | License | MIT | | TypeScript types | none | | Module format | CommonJS | | Dependencies | 1 | | Unpacked size | 10.9 KB | | Known vulnerabilities | 0 | | Install scripts | no | | GitHub stars | 6 | | Author | Balázs Frey | | Maintainers | balazsfrey | | Keywords | strapi, email, provider, azure, communication service | ## Links - npm: https://www.npmjs.com/package/strapi-provider-email-azure - Repository: https://github.com/Freyb/strapi-provider-email-azure - Homepage: https://github.com/Freyb/strapi-provider-email-azure#readme - Issues: https://github.com/Freyb/strapi-provider-email-azure/issues - npm.io page: https://npm.io/package/strapi-provider-email-azure ## Dependencies (1) - [@azure/communication-email](https://npm.io/package/@azure/communication-email.md) 1.0.1-alpha.20250318.1 ## Alternatives - [@expo/fingerprint](https://npm.io/package/@expo/fingerprint.md) — 6.2M weekly downloads - [@azure/monitor-opentelemetry-exporter](https://npm.io/package/@azure/monitor-opentelemetry-exporter.md) — 850.0K weekly downloads - [@azure/monitor-opentelemetry](https://npm.io/package/@azure/monitor-opentelemetry.md) — 624.0K weekly downloads - [@posthog/ai](https://npm.io/package/@posthog/ai.md) — 423.3K weekly downloads - [fakefilter](https://npm.io/package/fakefilter.md) — 63.9K weekly downloads ## Recent versions - 1.0.4 (latest) — 2025-03-30 - 1.0.3 — 2023-06-12 - 1.0.2 — 2023-05-24 - 1.0.1 — 2023-04-24 ## README # Strapi Email provider for Azure Communication Service ## Installation ```bash # using yarn yarn add strapi-provider-email-azure # using npm npm install strapi-provider-email-azure --save ``` Then in your `config/plugins.js`: ```js module.exports = ({ env }) => ({ // ... email: { config: { provider: 'strapi-provider-email-azure', providerOptions: { endpoint: env('AZURE_ENDPOINT'), }, settings: { defaultFrom: env('FALLBACK_EMAIL'), }, }, }, // ... }); ``` ## Usage ```js await strapi .plugin('email') .service('email') .send({ from: process.env.EMAIL_SERVICE_ADDRESS, to: [ { address: 'recipent@email.address', displayName: 'Display Name', }, ], subject: 'Hello world', text: 'Hello world', }); ``` You can also leave the `from` field empty to send the email from the fallback address. The following fields are supported: | Field | Description | | ----------- | ----------------------------------------------------------------- | | from | Email address of the sender (string) | | to | Array of recipients (string \| EmailAddress \| Array\) | | cc | Array of recipients who get cc (string \| EmailAddress \| Array\) | | bcc | Array of recipients who get bcc (string \| EmailAddress \| Array\) | | replyTo | Email address to which replies are sent (Array\) | | subject | Subject of the email (string) | | text | Plaintext version of the message (string) | | html | HTML version of the message (string) | | attachments | Array of attachments (Array\) | | disableUserEngagementTracking | Whether user engagement tracking should be disabled (boolean) | | headers | Custom email headers (Dictionary) | ```ts type EmailAddress { address: string, displayName: string } type Attachment { name: string, contentType: string, contentInBase64: string } ``` For more information, please refer to @azure/communication-email documentations: - [npm](https://www.npmjs.com/package/@azure/communication-email) - [EmailMessage interface](https://learn.microsoft.com/en-us/javascript/api/@azure/communication-email/emailmessage?view=azure-node-latest#@azure-communication-email-emailmessage-content) ## How to create Azure Communication Service ### 1. Create the Email Communications Service 1. Navigate to the [Azure portal](https://portal.azure.com/) to create a new resource 2. Create **Email Communication Services** ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/create_email_communication_services.png) 1. Complete the required information on the basics tab 2. Review the resource details. Click Create 3. Wait for the Deployment to complete ### 2. Create Communication Service 1. Navigate to the [Azure portal](https://portal.azure.com/) to create a new resource 2. Create **Communication Services** ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/create_communication_services.png) 3. Complete the required information on the basics tab 4. Review the resource details. Click Create 5. Wait for the Deployment to complete ### 3. Connect the services 1. Go to your newly created **Email Communcation Services** resource, and navigate to **Provision Domains** ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/create_provision_domains.png) 2. Add a new Azure managed domain or Custom domain ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/add_provision_domain.png) 3. Go to your **Communication Services** resource, and navigate to **Email/Domains** ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/connect_domains.png) 4. Connect to the domain you created in you Email Communication Services resource ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/fill_domain_details.png) ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/connected_domain.png) ### 4. Acquire access endpoint key 1. In your **Communication Services** resource, navigate to **Settings/Keys** 2. Copy your **Primary key/Connection string** ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/get_connection_string.png) 3. Store it in your environment variables\ `AZURE_ENDPOINT=` ### 5. (Optional) Create email addresses 1. In your **Email Communication Services** resource, go to **Provision Domains**, and click on the name of your domain 2. In **Email services/MailFrom addresses** you can create additional email addresses 3. By default DoNotReply@yourdomain is created, and you can store it as the fallback email address of `strapi-provider-email-azure` in your environment variables\ `FALLBACK_EMAIL=DoNotReply@yourdomain` ### 6. (Optional) Managed Identity if running on Azure instances #### Create and assign an identity 1. Refer https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp on creating and managing identities. 2. Assign the identity to Azure Communication Service with the role 'Communication and Email Service Owner' or create a custom role definition to restrict the permissions. ![](https://raw.githubusercontent.com/Freyb/strapi-provider-email-azure/main/images/connect_domains.png) #### Update plugins.js Then in your `config/plugins.js`: ```js module.exports = ({ env }) => ({ // ... email: { config: { provider: 'strapi-provider-email-azure', providerOptions: { endpoint: env('AZURE_ENDPOINT'), // ex: https://-acsendpoint..communication.azure.com useManagedIdentity: true, identityClientId: env('IDENTITY_CLIENT_ID') // GUID from the identity, ex : cf5c7b28-9eaa-47a1-b313-xxxxxxx }, settings: { defaultFrom: env('FALLBACK_EMAIL'), }, }, }, // ... }); ``` --- _Source: https://npm.io/package/strapi-provider-email-azure · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._