Unable to update email_address_sender for azurerm_cost_management_scheduled_action

[juicybaba]

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 and review the contribution guide to help.

Terraform Version

1.5.4

AzureRM Provider Version

3.69.0

Affected Resource(s)/Data Source(s)

azurerm_cost_management_scheduled_action

Terraform Configuration Files

resource "azurerm_cost_management_scheduled_action" "default" {
  name                 = "CostReportMonthToDateCostByService"
  display_name         = "CostReportMonthToDateCostByService"
  view_id              = azurerm_subscription_cost_management_view.default.id
  email_address_sender = "email@email.com"
  email_subject        = "hi"
  email_addresses      = local.contact_list
  message              = "Hi all, take a look at Cost Report - Month To Date Cost By Service!"
  frequency            = "Daily"
  hour_of_day          = 15
  start_date           = local.start_date
  end_date             = local.end_date
}

### Debug Output/Panic Output

```shell
The `email_address_send` doesn't change after a successful apply in portal, and new plan still shows `email_address_send` will be changed.

Expected Behaviour

The email_address_send should be updated with the new value.

Actual Behaviour

The email_address_send doesn't change after a successful apply in portal, and new plan still shows email_address_send will be changed.

Steps to Reproduce

No response

Important Factoids

No response

References

No response

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