FinOps Hub 14 deployment fails with DeploymentScriptACIProvisioningTimeout

🐛 Problem

A FinOps Hub 14.0 deployment intermittently fails while provisioning the Azure Container Instances used by ARM deployment scripts.

The deployment reaches a terminal Failed state with:
DeploymentScriptACIProvisioningTimeout

The supporting resource: 'Azure Container Instance' did not provision during the expected time.

The failure occurs before the deployment script PowerShell content executes.

The issue has occurred across multiple FinOps Hub modules, including:
Microsoft.FinOpsHubs.Core
Microsoft.CostManagement.Exports
Microsoft.FinOpsHubs.Recommendations
Microsoft.FinOpsHubs.AzureResourceGraph

👣 Repro steps
Create an Azure resource group in East US or East US 2.
Assign the deployment user Owner on the resource group.
Deploy FinOps Hub version 14.0 using the Azure portal ARM template.
Enable recommendations and managed Cost Management exports.
Wait for the deployment-script resources to provision.
Observe that one or more nested deployment-script resources fail with DeploymentScriptACIProvisioningTimeout.
The issue has reproduced in both East US and East US 2.

🤔 Expected
The FinOps Hub deployment should complete successfully. Each Microsoft.Resources/deploymentScripts resource should provision its temporary Azure Container Instance, execute its script, and complete.

Environment
FinOps hub version: 14.0
Billing account type: Unknown / not relevant to the ACI provisioning failure
Power BI report type: Not applicable; deployment fails before report configuration
Cost Management export: Managed exports enabled
Azure regions tested: East US and East US 2
Deployment method: Azure portal ARM template deployment
Private routing: Disabled
Azure PowerShell deployment script version: 11.0
Deployment script kind: AzurePowerShell
Deployment script cleanup preference: OnSuccess
Deployment script retention interval: PT1H
Deployment script timeout: P1D

ℹ️ Additional context
A standalone Azure Container Instance can be created successfully in the same CX environment.

The deployment user is Owner on the target resource group.

Some FinOps deployment scripts succeed in the same deployment and region, while others fail. For example, during one attempt the following scripts succeeded:
Microsoft.FinOpsHubs.Core_ADF.StopTriggers
Microsoft.FinOpsHubs.IngestionQueries_ADF.StopTriggers
Microsoft.FinOpsHubs.AzureResourceGraph
Microsoft.FinOpsHubs.DeleteOldResources

Other attempts failed with the same ACI provisioning timeout in different modules:
Microsoft.FinOpsHubs.DeleteOldResources
Microsoft.FinOpsHubs.AzureResourceGraph_ADF.StopTriggers
Microsoft.CostManagement.Exports_ADF.StopTriggers
Microsoft.CostManagement.Exports_Storage.SchemaFiles.Upload
Microsoft.FinOpsHubs.Recommendations_UploadSchemas
Microsoft.FinOpsHubs.Core_ADF.StopTriggers

The failures are not limited to Data Factory trigger-management scripts. Schema upload scripts also fail, which suggests an issue with the shared ARM deployment-script / ACI provisioning mechanism rather than the script logic or ADF permissions.

The CX team confirmed that a standalone ACI deployment succeeds. The original deployment and resource group were deleted before retrying.

Known correlation IDs:
343992fb-f3bd-4108-8a4b-032113c9dcfe
9a188395-e2c2-4d44-9b60-dc3102e3e429
078c7cd6-2a54-4795-aac5-ccb96df9bf2c

Prerequisites verified: all required resource providers registered, user has owner role on the sub and RG, no policy restriction, the subscription has a policy exemption.

Start by reviewing the Azure portal ARM deployment details for the failed Microsoft.Resources/deploymentScripts resources and correlate them with the listed deployment IDs. Compare failed and successful Azure Container Instance provisioning across the affected modules and verify whether the failure occurs before PowerShell execution. Done means identifying an actionable shared provisioning cause or documenting the required Azure-side fix or workaround.