Related command
it is unclear how to use --enable-managed-virtual-network --enable-managed-vnet
The flag indicates whether enable managed virtual network.
accepted values: false, true
Is your feature request related to a problem? Please describe.
I try this:
az synapse workspace create --name $synapseWorkspaceName --resource-group $resourceGroupName --storage-account $storageAccountName --managed-rg-name $synapseWorkspaceNameManaged \ --file-system $fileShareName \ --location $location \ --sql-admin-login-user 'sqladminuser' \ --sql-admin-login-password '' \ --repository-type AzureDevOpsGit --account-name $myGitProjectAccountName --project-name $myGitProjectName --tenant-id $tenantId --repository-name $myGitRepositoryName --collaboration-branch $myGitCollaborationBranch --enable-managed-virtual-network true --enable-managed-vnet true
Describe the solution you'd like
Must be understandable. With an example is already helpful.
Describe alternatives you've considered
Manually turning on. Azure CLI is not of full use.
Additional context
Nope.
Related command
it is unclear how to use --enable-managed-virtual-network --enable-managed-vnet
The flag indicates whether enable managed virtual network.
accepted values: false, true
Is your feature request related to a problem? Please describe.
I try this:
az synapse workspace create --name $synapseWorkspaceName --resource-group $resourceGroupName --storage-account $storageAccountName --managed-rg-name $synapseWorkspaceNameManaged \ --file-system $fileShareName \ --location $location \ --sql-admin-login-user 'sqladminuser' \ --sql-admin-login-password '' \ --repository-type AzureDevOpsGit --account-name $myGitProjectAccountName --project-name $myGitProjectName --tenant-id $tenantId --repository-name $myGitRepositoryName --collaboration-branch $myGitCollaborationBranch --enable-managed-virtual-network true --enable-managed-vnet trueDescribe the solution you'd like
Must be understandable. With an example is already helpful.
Describe alternatives you've considered
Manually turning on. Azure CLI is not of full use.
Additional context
Nope.