Argument missing | azurerm_bot_channel_email_v3.33.0 module

[Hitesh-Kariya]

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

Terraform Version

1.4.0

AzureRM Provider Version

3.33.0

Affected Resource(s)/Data Source(s)

azurerm_bot_channel_email_v.3.33.0

Terraform Configuration Files

Module - azurerm_bot_channel_email_v3.33.0

Argument missing - "Authentication Type"

Debug Output/Panic Output

NA

Expected Behaviour

Argument - "Authentication Type" - must be there.

1. Modern Authentication (OAUTH)
2. Basic Authentication (disabling Oct'22)

Actual Behaviour

No Argument "Authentication Type"

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[manicminer]

@Hitesh-Kariya Thanks for opening this issue. Does this relate to a Terraform module rather than the AzureRM provider? If this is a provider issue, please confirm and provide more information about the exact error you are seeing and your configuration to reproduce it. Thanks!

[Hitesh-Kariya]

The issue is from Terraform module side.
Ref link : https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/bot_channel_email

Here, there is no argument for "Authentication Type".

Where as when we deploy in portal there are two authentication methods:

. Modern authentication (OAUTH)
. Basic authentication (disabling Oct'22)

I think terraform by default goes with Basic authentication.

[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.