feat(integrations): add Azure Communication Email integration example#3102
feat(integrations): add Azure Communication Email integration example#3102rahulbhadja wants to merge 3 commits intoresend:canaryfrom
Conversation
- Added documentation for Azure Communication Email integration. - Created example for sending emails using Azure Communication Email. - Updated integrations list and snippets to include Azure Communication Email.
|
|
@rahulbhadja is attempting to deploy a commit to the resend Team on Vercel. A member of the Team first needs to authorize it. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
3 issues found across 8 files
Confidence score: 3/5
- There is a concrete regression risk around the new
beginSendflow: bothapps/docs/integrations/azure-communication-email.mdxandexamples/azure-communication-email/src/index.tsxomit an explicit production credential permission check, which could lead to failed sends or misconfigured deployments. - I’m scoring this as moderate merge risk because the top findings are medium-high severity (7/10) with high confidence (9/10), and they affect guidance and sample implementation that users are likely to copy.
examples/azure-communication-email/tsconfig.jsonis a smaller but real correctness issue: missing Node ambient types while usingprocess.envcan cause type errors and confusion in local builds.- Pay close attention to
apps/docs/integrations/azure-communication-email.mdx,examples/azure-communication-email/src/index.tsx, andexamples/azure-communication-email/tsconfig.json- permission-check guidance forbeginSendand Node typing should be fixed before broad adoption.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="apps/docs/integrations/azure-communication-email.mdx">
<violation number="1" location="apps/docs/integrations/azure-communication-email.mdx:77">
P1: Custom agent: **API Key Permission Check SDK Methods**
This new Azure SDK send flow (`beginSend`) is documented without a required permission check for production credentials. Add an explicit note to verify the `AZURE_EMAIL_CONNECTION_STRING` has email-send permissions before deployment (API Key Permission Check SDK Methods rule).</violation>
</file>
<file name="examples/azure-communication-email/src/index.tsx">
<violation number="1" location="examples/azure-communication-email/src/index.tsx:21">
P1: Custom agent: **API Key Permission Check SDK Methods**
This change adds a new Azure Communication Email send operation (`beginSend`) but does not include a permission confirmation step for production credentials. Confirm the existing `AZURE_EMAIL_CONNECTION_STRING` used in production has rights to perform email send operations to avoid post-deploy authorization failures.</violation>
</file>
<file name="examples/azure-communication-email/tsconfig.json">
<violation number="1" location="examples/azure-communication-email/tsconfig.json:21">
P2: Missing Node.js types in tsconfig.json while using `process.env` Node global. The `types` array only includes `vitest/globals`, excluding Node.js ambient types needed for `process.env` usage in `index.tsx`. Add `@types/node` to the types array to ensure proper type-checking.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| await poller.pollUntilDone(); | ||
| ``` | ||
|
|
||
| <Info>Azure Communication Email expects the sender in the `senderAddress` field.</Info> |
There was a problem hiding this comment.
P1: Custom agent: API Key Permission Check SDK Methods
This new Azure SDK send flow (beginSend) is documented without a required permission check for production credentials. Add an explicit note to verify the AZURE_EMAIL_CONNECTION_STRING has email-send permissions before deployment (API Key Permission Check SDK Methods rule).
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/docs/integrations/azure-communication-email.mdx, line 77:
<comment>This new Azure SDK send flow (`beginSend`) is documented without a required permission check for production credentials. Add an explicit note to verify the `AZURE_EMAIL_CONNECTION_STRING` has email-send permissions before deployment (API Key Permission Check SDK Methods rule).</comment>
<file context>
@@ -0,0 +1,88 @@
+await poller.pollUntilDone();
+```
+
+<Info>Azure Communication Email expects the sender in the `senderAddress` field.</Info>
+
+## Try it yourself
</file context>
| }, | ||
| }; | ||
|
|
||
| const poller = await client.beginSend(message); |
There was a problem hiding this comment.
P1: Custom agent: API Key Permission Check SDK Methods
This change adds a new Azure Communication Email send operation (beginSend) but does not include a permission confirmation step for production credentials. Confirm the existing AZURE_EMAIL_CONNECTION_STRING used in production has rights to perform email send operations to avoid post-deploy authorization failures.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/azure-communication-email/src/index.tsx, line 21:
<comment>This change adds a new Azure Communication Email send operation (`beginSend`) but does not include a permission confirmation step for production credentials. Confirm the existing `AZURE_EMAIL_CONNECTION_STRING` used in production has rights to perform email send operations to avoid post-deploy authorization failures.</comment>
<file context>
@@ -0,0 +1,23 @@
+ },
+};
+
+const poller = await client.beginSend(message);
+
+await poller.pollUntilDone();
</file context>
| "lib": ["ESNext", "DOM", "DOM.Iterable"], | ||
| "module": "ESNext", | ||
| "target": "ESNext", | ||
| "types": ["vitest/globals"], |
There was a problem hiding this comment.
P2: Missing Node.js types in tsconfig.json while using process.env Node global. The types array only includes vitest/globals, excluding Node.js ambient types needed for process.env usage in index.tsx. Add @types/node to the types array to ensure proper type-checking.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/azure-communication-email/tsconfig.json, line 21:
<comment>Missing Node.js types in tsconfig.json while using `process.env` Node global. The `types` array only includes `vitest/globals`, excluding Node.js ambient types needed for `process.env` usage in `index.tsx`. Add `@types/node` to the types array to ensure proper type-checking.</comment>
<file context>
@@ -0,0 +1,25 @@
+ "lib": ["ESNext", "DOM", "DOM.Iterable"],
+ "module": "ESNext",
+ "target": "ESNext",
+ "types": ["vitest/globals"],
+ },
+ "include": ["."],
</file context>
1 participant
Summary
Adds new Azure Communication Email integration example to React Email.
Changes
Notes
@azure/communication-emailAZURE_EMAIL_CONNECTION_STRINGSummary by cubic
Adds an Azure Communication Email integration example and docs. Lets users render with
@react-email/componentsand send via@azure/communication-emailusingAZURE_EMAIL_CONNECTION_STRING.examples/azure-communication-emailshowing render +EmailClient.beginSend(polished with single quotes and cleanedtsconfig).Written for commit 7ac0008. Summary will update on new commits.