Description
/area runtime
Hello everyone,
I've been working on integrating ACS (Azure Communication Services) into a DAPR-based distributed, event-driven architecture.
I encountered a significant limitation when trying to integrate ACS (Azure Communication Services) with DAPR : there is currently no native DAPR binding for ACS (Azure Communication Services), and the existing custom HTTP binding approach falls short due to authentication constraints.
Could you please confirm whether DAPR currently supports integration with ACS (Azure Communication Services) in any form? If such integration is already possible, I would appreciate guidance or documentation on how it can be achieved.
If DAPR does not currently support ACS (Azure Communication Services) integration, I would like to propose this as a feature request. Enabling seamless integration with Azure Communication Services would significantly enhance DAPR's capabilities in building communication-enabled distributed applications.
Similar to the existing support for AWS SES (Simple Email Service), an official DAPR's output binding for ACS(Azure Communication Services) would streamline email delivery in cloud-native applications.
This binding should support:
- Email sending via ACS
- Authentication via connection string
- Authentication via HMAC-SHA256 for the endpoint
POST https://{endpoint}/emails:send?api-version=2023-03-31
using custom http binding. - Configurable email metadata (e.g., sender, recipients, subject, etc.)
Benefits
Improved Developer Experience: Simplifies integration of ACS (Azure Communication Services) into DAPR-based microservices.
Security: Ensures secure communication with ACS (Azure Communication Services) using its native authentication mechanism.
This enhancement would significantly improve the developer experience and unlock the use of ACS (Azure Communication Services) in DAPR-based applications.