Update workspace in public to private via az cli.
- This follows the principles that are discussed in create secure workspace doc.
- It extends from add private endpoint to workspace doc and have steps to update for all its sub-resources.
- Have a workspace deployed in public - with registry or no registry resource availability condition is taken care.
- It is better all private dns zones need to be created first. Then, user can refer to same while creating private endpoints for them.
- The file workspace-in-vnet.sh has logic to update private endpoints for aml workspace resource.
- The file storage-in-vnet.sh has logic to update private endpoints for storage resource.
- The file vault-in-vnet.sh has logic to update private endpoint for keyvault resource.
- The file reistry-in-vnet.sh has logic to update private endpoint for container registry resource.
- Before running the script, make sure to run: 1) az upgrade, 2) az login --identity.
- Fill all the required parameters such as workspace, resource_group, etc. details in secure-workspce.sh.
- The script file secure-workspce.sh need to be run to have all the child shell scripts run.
$ ./secure-workspace.sh
- Before running the script create-public-workspace.sh, make sure to run: 1) az upgrade, 2) az login --identity.
- Fill in required parameters in the script file.
$ ./create-public-workspace.sh