Azure Cloud Shell roadmap 2023 and future investigations #322
theJasonHelmick
started this conversation in
General
Replies: 5 comments 1 reply
-
|
W.R.T. 'Improved editor experience' : Is there a way to use the CloudShell with vscode.dev? Screenshot
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Hi @Ayanmullick - thanks for the discussion. VSCode.dev is an excellent web based editor. While you can use this separately to edit scripts in your cloud shell drive, it is not integrated like the current editor. We are exploring upgrading our editor to provide a better experience, including investigating VSCode.dev. While I don't have anything to announce now, I really appreciate your comment in recommending VSCode.dev. |
Beta Was this translation helpful? Give feedback.
-
|
Hi J. The customer (large Bank) has restricted resource creation with an Azure resource policy by disallowing storage account creation for Cloud Shell (ms-resource-usage:azure-cloud-shell). However, the bank wants to be able to block the resource provider "Microsoft.CloudShell" altogether and also blocking this new roadmap feature. Is this possible and how? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Glenn – if the request is to disable cloud Shell for the customer tenant entirely – that is possible – is that the question?
From: Glenn Hunter ***@***.***>
Date: Monday, September 18, 2023 at 2:29 AM
To: Azure/CloudShell ***@***.***>
Cc: Jason Helmick ***@***.***>, Author ***@***.***>
Subject: Re: [Azure/CloudShell] Azure Cloud Shell roadmap 2023 and future investigations (Discussion #322)
Hi J. The customer (large Bank) has restricted resource creation with an Azure resource policy by disallowing storage account creation for Cloud Shell (ms-resource-usage:azure-cloud-shell). However, the bank wants to be able to block the resource provider "Microsoft.CloudShell" altogether and also blocking this new roadmap feature. Is this possible and how?
—
Reply to this email directly, view it on GitHub<#322 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADATMBQM4GZTM7FOWPIXR7LX3AIA5ANCNFSM6AAAAAAX6P5HXQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Jason
Thanks for your rapid response.
On the roadmap for Cloud Shell a solution where storage account is not required. CloudShell/roadmap/cs-roadmap-2023.md at master · Azure/CloudShell · GitHub<https://github.com/Azure/CloudShell/blob/master/roadmap/cs-roadmap-2023.md>
Currently the customer has restricted resource creation with an Azure resource policy by disallowing storage account creation for Cloud Shell
The Bank want to be able to block the resource provider "Microsoft.CloudShell" altogether.
***@***.***
So Yes, the customer would like to disable entirely.
Could you please let me know how this is done on the tenant level..? I haven’t found documentation around this.
Many Thanks
Glenn Hunter
From: Jason Helmick ***@***.***>
Sent: Monday, 18 September 2023 18:29
To: Azure/CloudShell ***@***.***>
Cc: Glenn Hunter ***@***.***>; Comment ***@***.***>
Subject: Re: [Azure/CloudShell] Azure Cloud Shell roadmap 2023 and future investigations (Discussion #322)
Hi Glenn – if the request is to disable cloud Shell for the customer tenant entirely – that is possible – is that the question?
From: Glenn Hunter ***@***.***>
Date: Monday, September 18, 2023 at 2:29 AM
To: Azure/CloudShell ***@***.***>
Cc: Jason Helmick ***@***.***>, Author ***@***.***>
Subject: Re: [Azure/CloudShell] Azure Cloud Shell roadmap 2023 and future investigations (Discussion #322)
Hi J. The customer (large Bank) has restricted resource creation with an Azure resource policy by disallowing storage account creation for Cloud Shell (ms-resource-usage:azure-cloud-shell). However, the bank wants to be able to block the resource provider "Microsoft.CloudShell" altogether and also blocking this new roadmap feature. Is this possible and how?
—
Reply to this email directly, view it on GitHub<#322 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADATMBQM4GZTM7FOWPIXR7LX3AIA5ANCNFSM6AAAAAAX6P5HXQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub<#322 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWJ6RTJIJ2VHPXSIC5E73P3X3BZDRANCNFSM6AAAAAAX6P5HXQ>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Glenn!
If they only need to restrict storage accounts and still want Cloud Shell access, next month we are releasing Ephemeral sessions (sessions that don’t require a storage account). Which may serve their purpose.
To initiate the disablement of Azure Cloud Shell from a customer tenant, the customer will need to contact support and have them issue an IcM to the cloud Shell team with the appropriate details.
From: Glenn Hunter ***@***.***>
Date: Monday, September 18, 2023 at 10:00 AM
To: Azure/CloudShell ***@***.***>
Cc: Jason Helmick ***@***.***>, Author ***@***.***>
Subject: Re: [Azure/CloudShell] Azure Cloud Shell roadmap 2023 and future investigations (Discussion #322)
Hi Jason
Thanks for your rapid response.
On the roadmap for Cloud Shell a solution where storage account is not required. CloudShell/roadmap/cs-roadmap-2023.md at master · Azure/CloudShell · GitHub<https://github.com/Azure/CloudShell/blob/master/roadmap/cs-roadmap-2023.md>
Currently the customer has restricted resource creation with an Azure resource policy by disallowing storage account creation for Cloud Shell
The Bank want to be able to block the resource provider "Microsoft.CloudShell" altogether.
***@***.***
So Yes, the customer would like to disable entirely.
Could you please let me know how this is done on the tenant level..? I haven’t found documentation around this.
Many Thanks
Glenn Hunter
From: Jason Helmick ***@***.***>
Sent: Monday, 18 September 2023 18:29
To: Azure/CloudShell ***@***.***>
Cc: Glenn Hunter ***@***.***>; Comment ***@***.***>
Subject: Re: [Azure/CloudShell] Azure Cloud Shell roadmap 2023 and future investigations (Discussion #322)
Hi Glenn – if the request is to disable cloud Shell for the customer tenant entirely – that is possible – is that the question?
From: Glenn Hunter ***@***.***>
Date: Monday, September 18, 2023 at 2:29 AM
To: Azure/CloudShell ***@***.***>
Cc: Jason Helmick ***@***.***>, Author ***@***.***>
Subject: Re: [Azure/CloudShell] Azure Cloud Shell roadmap 2023 and future investigations (Discussion #322)
Hi J. The customer (large Bank) has restricted resource creation with an Azure resource policy by disallowing storage account creation for Cloud Shell (ms-resource-usage:azure-cloud-shell). However, the bank wants to be able to block the resource provider "Microsoft.CloudShell" altogether and also blocking this new roadmap feature. Is this possible and how?
—
Reply to this email directly, view it on GitHub<#322 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADATMBQM4GZTM7FOWPIXR7LX3AIA5ANCNFSM6AAAAAAX6P5HXQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub<#322 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWJ6RTJIJ2VHPXSIC5E73P3X3BZDRANCNFSM6AAAAAAX6P5HXQ>.
You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub<#322 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADATMBVUKUG3EQKJ5TDMR3TX3B43BANCNFSM6AAAAAAX6P5HXQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The Azure Cloud Shell roadmap can be found here on our Github repository. We welcome discussions on our current and future plans.
Roadmap 2023 and future investigations
Azure Cloud Shell is an interactive, authenticated, browser-accessible shell for managing Azure
resources. As a web-based environment, Cloud Shell provides immediate management access to any
device with a network connection and provides a consistent and secure environment with
always-up-to-date tools. Users can work with their resources from any device, interactively, or
through automation
FY2023 roadmap
The Azure Cloud Shell team plans to release the following features and updates in the Sept-Oct 2023
timeframe.
sessions
Tenets
These are the Azure Cloud Shell guiding principles we use to evaluate and prioritize Cloud Shell
work activities:
range of tools and resources, including bash, PowerShell, Azure CLI, and Azure PowerShell.
environment for users to work in.
easy for users to manage their resources from anywhere.
beyond the cost of the underlying Azure resources used by the user. It also helps to reduce costs
by allowing users to automate tasks and work more efficiently.
Based on our tenets, these are the investment priorities for 2023.
Improved User Interface
The user interface refresh will help improve the customer experience, accessibility, and
functionality of Cloud Shell. This will make it easier for users to navigate and find the tools and
resources they need. Benefits include:
Ephemeral Sessions
Ephemeral sessions allow users to manage Azure resources faster without the overhead of creating and
associating Azure storage accounts. These temporary and disposable sessions are best for scenarios
where customers need to perform ad-hoc tasks without the need to persist data or files between
sessions. In addition, this provides a layer of security to scenarios to ensure that data or files
created during the session are not accessible to other users or processes after the session ends.
Benefits include:
storage account has never been configured
Improving VNET Configuration
Azure Cloud shell can be deployed to a local network (VNET) to gain access to local resources such
as virtual machines, databases, and other connected services. As popularity of VNET has increased,
so has a number of issues relating to configuration confusion and the need to improve both the
documentation and configuration of VNET scenarios.
The VNET refresh will address these issues by making improvements:
FY2024 Investments, Investigations and discussions
We are working with customers to investigate and discuss areas of improvement and new features as we
plan our roadmap for FY2024. Below are areas of investigation - We welcome your feedback! Please add
issues or discussions to our repository.
We look forward to hearing from you! Please join us in Discussions.
Beta Was this translation helpful? Give feedback.
All reactions