Need substitute for network-profile option to access postgres image from webapp image

**Describe the bug**
There was a breaking change in 2.29 but no documentation provided regarding how to sustain required functionality. The line below used to create our container so that it could reach a postgres DB specified by the network profile below. Can you please point me to some work-around on how to deal with this breaking change?

**To Reproduce**
az container create -e DB_UserId={dbUser} {dbPswd} DB_SERVER={dbServer} -g rg-{mygroup} --name dev-xxx --image informpredictdev.azurecr.io/ipappweb --ports 80 --registry-username informpredictdev --registry-password xxx --**network-profile** /subscriptions/{xxx}/resourceGroups/rg-{mygroup}/providers/Microsoft.Network/networkProfiles/testaci-networkProfile

**Expected behavior**
Would expect some guidance near the "breaking change" documentation to help us upgrade

**Environment summary**
Azure DevOps
az container create -e DB_UserId={dbUser} {dbPswd} DB_SERVER={dbServer} -g rg-{mygroup} --name dev-xxx --image informpredictdev.azurecr.io/ipappweb --ports 80 --registry-username informpredictdev --registry-password xxx --**network-profile** /subscriptions/{xxx}/resourceGroups/rg-{mygroup}/providers/Microsoft.Network/networkProfiles/testaci-networkProfile