AI Platform: Known Issues and Open Points¶

This page collects what the sources state as known issues and what you should confirm for your own deployment. Items marked Confirm are differences or gaps seen in the sources, not verified behaviour.

Known issues (from the modules)¶

Issue	Effect	Workaround
Updating a capability host is not supported by the ARM API	A change to the host (for example another connection) fails	Not given in the source. Plan changes to connections before the first deployment.
`terraform destroy` fails with a subnet deletion error	The integration subnet is held by service association links of the agent service	Not given in the source. Expect to retry later, and see the next item.
The integration subnet cannot be deleted right after a destroy	Azure service dependencies release the subnet only after a delay	Wait and delete afterwards.

Open points¶

Topic	What the sources show	What to confirm
Public network access	The account module sets `publicNetworkAccess` to `Enabled`, also when it creates a private endpoint. The project module README says "private endpoints for secure access".	Whether public access is acceptable on your platform or is closed by policy or another setting.
Account diagnostics	The project module sets diagnostic settings on the account only in standalone mode. The account module sets none.	Where logs of the shared account go on your platform.
Hard-coded platform names	`platform_data` holds fixed names for one deployment. Its README and `main.tf` also differ in some names (container registry, platform storage account).	Use the code as the source of truth and replace the values for your deployment.
README examples out of date	The `platform_data` README shows `foundry_project` inputs (`resource_group_name`, `storage_account_id`) that the module no longer has, and lists a PostgreSQL Flexible Server that has no data source. The README of `project_data` links to specification files that are not in the repository.	Follow the module variables, not the README examples.
Project name	`project_name` has default `null` in the code but is required in practice.	Always set it.
Group inputs	The three group IDs default to `null`, but the role assignments are unconditional.	Always set all three.
Reader group	The reader group only gets a role on the search index.	Whether readers also need a role on the project or storage.
Deploy roots	Planned for a later phase.	How your platform deploys the modules today.
Container Apps environment, registry, Cosmos DB, AI Search	The reference design looks them up. The repository has no module that creates them.	Where and how they are deployed on your platform.
Models	Deployed at platform level, with `azurerm_cognitive_deployment` in the migration example. No deployment code is in the repository.	Which models, regions and quota exist, and who changes them.
Provider versions	AzureRM is pinned below 5.0.	Plan this before an AzureRM major upgrade.
Backup, restore, SLA, support hours	Not in the sources.	Your contract or onboarding document.

Compatibility¶

The project module is "backward compatible": existing standalone deployments keep working, new ones should pass account_id.
The module variable model_deployments was removed from the project module. A call that still sets it must drop it and manage model deployments separately at platform level.