Improve Cloud Shell onboarding for advanced scenario with VNET isolation
@mbifeld y travaille déjà.
Depuis le 10/12/2025.
Évaluation
Cette issue n'a pas encore été évaluée.
Description
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.
- Langage dominant
- PowerShell
- Étoiles
- 273
- Forks
- 116
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Préparer son environnement
Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de Azure/CloudShell
-
bug Triage-needed
Difficulté 3/5 1-2 jours Accessibilité débutants 30/100
Azure/CloudShell#655 ·
-
Blood TestOuverte
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 5/100
Azure/CloudShell#654 · 2 commentaires ·
-
bug Triage-needed
Difficulté 4/5 3-5 jours Accessibilité débutants 38/100
Azure/CloudShell#653 ·
-
bug Triage-needed
Difficulté 4/5 3-5 jours Accessibilité débutants 22/100
Azure/CloudShell#649 · 2 commentaires ·
-
[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 subscriptionsPeut-être pris @priyaananthasankar l’a pris il y a 22 jours. Ouvertebug
Azure/CloudShell#648 · 1 commentaire · 1 personne assignée ·