Improve Cloud Shell onboarding for advanced scenario with VNET isolation
@mbifeld já está trabalhando nisso.
Desde 10/12/2025.
Avaliação
Esta issue ainda não foi avaliada.
Descrição
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.
- Linguagem predominante
- PowerShell
- Estrelas
- 273
- Forks
- 116
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de Azure/CloudShell
-
bug Triage-needed
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 30/100
Azure/CloudShell#655 ·
-
Blood TestAberta
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 5/100
Azure/CloudShell#654 · 2 comentários ·
-
bug Triage-needed
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 38/100
Azure/CloudShell#653 ·
-
bug Triage-needed
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 22/100
Azure/CloudShell#649 · 2 comentários ·
-
[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 subscriptionsTalvez já em andamento @priyaananthasankar assumiu há 23 dias. Abertabug
Azure/CloudShell#648 · 1 comentário · 1 responsável ·