Support for [Email Communication Service]

[iusergii]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Email Communications Service

New or Affected Resource(s)/Data Source(s)

azurerm_email_communication_service

Potential Terraform Configuration

No response

References

No response

[aristosvo]

I'll take a look!

[aristosvo]

PR #21526 is filed.

@iusergii Do you have explicit wishes in domains, domain validation and coupling with the azurerm_communication_service you already know about? If that's the case, it makes sense to provide some details here to make sure we can realise this as well.

[iusergii]

@aristosvo I'm quiet a new to this azure service as well. Working on PoC and for now I use azapi provider to cover:

• Microsoft.Communication/emailServices
• Microsoft.Communication/emailServices/domains
• Microsoft.Communication/emailServices/domains/senderUsernames

And there is one for triggering domain verification which I didn't find in docs:

• Microsoft.Communication/emailServices/initiateVerification

[github-actions]

This functionality has been released in v3.54.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[GraemeMeyerGT]

@aristosvo / @iusergii do I correctly understand that the Azure APIs do not yet fully support this resource? It looks like there's no documented API/attribute (and thus no Terraform resource) to configure the actual domain that's being attached (e.g. example.com). Is that right?

Edit: I base this on this api documentation which does not appear to list a domain attribute like FQDN or similar

[FinOCE]

Any chance there has been an update to this? I would like to be able to connect an Email Communications Service to the Communications Service, as well as provisioning a domain to the ECS (since this in my case would be setup through Azure DNS which is already available with terraform). In the meantime, I think I will have to just manually create the resources and put the connection string into my function app's app settings, since there aren't data sources for them to retrieve these programmatically either.

[aristosvo]

Hi @FinOCE and @GraemeMeyerGT ! At the time of contribution a lot of the workflow and APIs around these resources were unclear to me.

Please file separate feature requests for the other resources to create your whole Communication setup via Terraform, happy to help if I can find some time :)

[timja]

Please file separate feature requests for the other resources to create your whole Communication setup via Terraform, happy to help if I can find some time :)

see #22549 and #22995

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.