Suddenly getting vague error on Azure Digital Twins Data History Connection deployments, no code changes

**Bicep version**
I deploy through `task: AzureResourceManagerTemplateDeployment@3` in my .yml file for a pipeline. This triggers a Bicep deployment of which I'm not sure what version it uses.

**Describe the bug**
Suddenly my Azure Digital Twins Data History Connection is no longer deploying with a very vague error. I have used this deployment script many times in the past without issues and suddenly it gives:
```
{
"status": "Failed",
"error": {
"code": "InternalServerError",
"message": "The resource could not ACT due to an internal server error."
}
}
```

I just checked and it is also currently impossible to deploy data history connections manually. It will give the same error. I'm now 99% sure it is an issue within Azure and likely not necessarily Bicep, but I have no clue how to get this issue to the right people because tickets made in the portal are usually being ignored.

**To Reproduce**
Steps to reproduce the behavior:
The script I use specifically for the data history connection is:
```bicep
@description('Name of the resource group containing the general resources')
param generalResourceGroup string

@description('Name of the resource group containing the new building resources')
param newResourceGroup string

@description('Existing Digital Twin resource name')
param digitalTwinsName string

@description('Existing Event Hubs namespace resource name')
param eventHubsNamespaceName string

@description('Existing event hub name')
param eventHubName string

@description('Existing Azure Data Explorer cluster resource name')
param adxClusterName string

@description('Name given to twin lifecycle event table')
param adxTwinLifecycleEventsTableName string = 'AdtTwinLifecycleEvents'

@description('Name given to relationship lifecycle event table')
param adxRelationshipLifecycleEventsTableName string = 'AdtRelationshipLifecycleEvents'

@description('Existing database name')
param databaseName string

@description('Name given to table in database')
param databaseTableName string

var eventHubEndpoint = 'sb://${eventHubsNamespaceName}.servicebus.windows.net'

// Gets Azure Data Explorer cluster resource
resource adxCluster 'Microsoft.Kusto/Clusters@2022-11-11' existing = {
scope: resourceGroup(generalResourceGroup)
name: adxClusterName
}

// Gets Event Hubs namespace resource
resource eventHubsNamespace 'Microsoft.EventHub/namespaces@2021-11-01' existing = {
scope: resourceGroup(newResourceGroup)
name: eventHubsNamespaceName
}

resource digitalTwins 'Microsoft.DigitalTwins/digitalTwinsInstances@2023-01-31' existing = {
name: digitalTwinsName
}

// Creates a time series database connection between the Digital Twin resource and Azure Data Explorer cluster table
resource tsdbConnection 'Microsoft.DigitalTwins/digitalTwinsInstances/timeSeriesDatabaseConnections@2023-01-31' = {
name: 'tsdb-${databaseTableName}'
parent: digitalTwins
properties: {
connectionType: 'AzureDataExplorer'
adxEndpointUri: adxCluster.properties.uri
adxDatabaseName: databaseName
adxTwinLifecycleEventsTableName: adxTwinLifecycleEventsTableName
adxRelationshipLifecycleEventsTableName: adxRelationshipLifecycleEventsTableName
eventHubEndpointUri: eventHubEndpoint
eventHubEntityPath: eventHubName
adxResourceId: adxCluster.id
eventHubNamespaceResourceId: eventHubsNamespace.id
}
}
```

**Additional context**
If anyone has tips on how to get this to actual ADT developers or whoever is responsible for the data history connection then I am all ears. Tested deploying to multiple subscriptions, with and without resource locks (previously did with, removed them just to make sure), tested manual deployment through multiple accounts, everything fails.

No repository file or test is identified; start by reviewing the supplied Bicep deployment for the Azure Digital Twins timeSeriesDatabaseConnections resource and reproduce it through the pipeline and manually. Done would require identifying the responsible Azure component and documenting a confirmed resolution or workaround.

Written by the indexing model from the issue text.