Improve Cloud Shell onboarding for advanced scenario with VNET isolation
@mbifeld ci sta già lavorando.
Dal 10/12/2025.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
When onboarding Cloud Shell with VNET isolation the user's experience could be improved by clarifying the documentation for advanced scenario and relaxing some requirements:
- Expand the documentation at https://docs.microsoft.com/en-us/azure/cloud-shell/private-vnet with step by step installation guide, in particular the chapter "Deploy network resources". Currently it references two Quickstart ARM templates, but it takes additional time by investigating what needs to be done if some Azure resources are already in place, e.g. VNET with subnets.
- Clarify a requirement about how many different subnets are required (three according to the Quickstart ARM templates) and what requirements each subnet has if any, e.g. service endpoints, delegations, etc. Are three (3) subnets required, or could Private Endpoints be created within already defined subnets?
- Clarify requirements about RBAC permissions for different resources and service principals.
- Allow the storage account, relay namespace, virtual network and private endpoints be defined in different resource groups. As an example, networking resources could be managed by different teams and stay in different resource groups.
- Clarify best practices adopting Cloud Shell in multi-admin scenario. e.g., could one Storage Account with different File shares and RBAC access permissions be shared in multi-admin scenario? Are Relay namespace and Network profiles required to be created for each Cloud Shell user separately?
You did already a great job! Just an experience in higly governed and secured environment needs improvement.
- Lingua principale
- PowerShell
- Stelle
- 273
- Fork
- 116
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Azure/CloudShell
-
bug Triage-needed
Difficoltà 3/5 1-2 giorni Idoneità per principianti 30/100
Azure/CloudShell#655 ·
-
Blood TestAperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 5/100
Azure/CloudShell#654 · 2 commenti ·
-
bug Triage-needed
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
Azure/CloudShell#653 ·
-
bug Triage-needed
Difficoltà 4/5 3-5 giorni Idoneità per principianti 22/100
Azure/CloudShell#649 · 2 commenti ·
-
[BUG] Bash session falls back to ephemeral (“Failed to mount the Azure file share”) after $HOME image is attached; intermittent across 5 file shares, 3 storage accounts, 2 subscriptionsForse già presa @priyaananthasankar l’ha presa 21 giorni fa. Apertabug
Azure/CloudShell#648 · 1 commento · 1 assegnatario ·