Improve Cloud Shell onboarding for advanced scenario with VNET isolation
@mbifeld ya está trabajando en esto.
Desde el 10/12/2025.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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.
- Lenguaje dominante
- PowerShell
- Estrellas
- 273
- Forks
- 116
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Azure/CloudShell
-
bug Triage-needed
Dificultad 3/5 1-2 días Aptitud para principiantes 30/100
Azure/CloudShell#655 ·
-
Blood TestAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 5/100
Azure/CloudShell#654 · 2 comentarios ·
-
bug Triage-needed
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
Azure/CloudShell#653 ·
-
bug Triage-needed
Dificultad 4/5 3-5 días Aptitud para principiantes 22/100
Azure/CloudShell#649 · 2 comentarios ·
-
[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 subscriptionsPosiblemente ocupada @priyaananthasankar la tomó hace 22 días. Abiertobug
Azure/CloudShell#648 · 1 comentario · 1 asignado ·