Error - parsing segment "microsoftRelay": expected the segment "Microsoft.EventHub" to be "Microsoft.Relay"

[mlcooper]

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 (and AzureRM Provider) Version

Terraform v1.0.11
on linux_amd64
+ provider registry.terraform.io/hashicorp/azurerm v2.88.1

Affected Resource(s)

• azurerm_monitor_aad_diagnostic_setting

Terraform Configuration Files

resource "azurerm_monitor_aad_diagnostic_setting" "audit_logs" {
  name                           = "ManagedLogging-DAML-AuditLogs"
  eventhub_authorization_rule_id = module.aad_logs_eventhub_namespace.eventhub_namespace_auth_rule_id["daml-aadlogs-diagnostic-setting"]
  eventhub_name                  = module.aad_logs_eventhub_namespace.eventhub_name["evh-daml-aadlogs-audit"]
  storage_account_id             = module.storage.id["stdaml${var.tenant_abbreviation}${var.environment}aadaudit"]
  log_analytics_workspace_id     = local.log_analytics_workspace

  log {
    category = "ADFSSignInLogs"
    enabled  = false

    retention_policy {
      days    = 0
      enabled = false
    }
  }
  log {
    category = "AuditLogs"
    enabled  = true

    retention_policy {
      days    = 0
      enabled = false
    }
  }
  log {
    category = "ManagedIdentitySignInLogs"
    enabled  = false

    retention_policy {
      days    = 0
      enabled = false
    }
  }
  log {
    category = "NonInteractiveUserSignInLogs"
    enabled  = false

    retention_policy {
      days    = 0
      enabled = false
    }
  }
  log {
    category = "ProvisioningLogs"
    enabled  = false

    retention_policy {
      days    = 0
      enabled = false
    }
  }
  log {
    category = "ServicePrincipalSignInLogs"
    enabled  = false

    retention_policy {
      days    = 0
      enabled = false
    }
  }
  log {
    category = "SignInLogs"
    enabled  = false

    retention_policy {
      days    = 0
      enabled = false
    }
  }
  log {
    category = "RiskyUsers"
    enabled  = false

    retention_policy {
      days    = 0
      enabled = false
    }
  }
  log {
    category = "UserRiskEvents"
    enabled  = false

    retention_policy {
      days    = 0
      enabled = false
    }
  }

  timeouts {}
}

Debug Output

Panic Output

Expected Behaviour

That I would not run into this error below.

Actual Behaviour

Error: parsing "/subscriptions/xxxxxxxx-c0af-4bfa-ac48-xxxxxxxxxxxx/resourceGroups/rg-daml-aad-logs-dqa/providers/Microsoft.EventHub/namespaces/evhns-daml-dqa-qa-aad-logs/authorizationRules/daml-aadlogs-diagnostic-setting-auth-policy": parsing segment "microsoftRelay": expected the segment "Microsoft.EventHub" to be "Microsoft.Relay"

Steps to Reproduce

1. terraform apply

Important Factoids

References

• Error - parsing segment "microsoftRelay": expected the segment "Microsoft.EventHub" to be "Microsoft.Relay" #14404
• Relay SDK Upgrade causes failure parsing EventHub AuthorizationRules #14269

[jpr-snl]

Also affects 2.88.0. It appears the fix in #14404 was ineffective, rather than a regression appearing in 2.88.1. The best workaround I've found is reverting the azurerm terraform provider to 2.85.0.

[mlcooper]

@tombuildsstuff I saw that you worked on the related issues to resolve this issue, however I'm still experiencing the error. This issue is a blocker for me to move to the azurerm provider past version v2.85.0.

[rcskosir]

Thanks for opening this issue. This was a problem in the 2.x version of the provider which is no longer actively maintained.
If this is still an issue with the 3.x version of the provider please do let us know by opening a new issue, thanks!

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