Offer Microsoft 365/Office 365 on Azure Stack Hub in disconnected mode for organizations that cannot be connected to anything.

Azure Stack Edge(ASE) only has limited monitoring tools without Azure Kubernetes cluster admin access. More tools should be available for ASE without having admin access.

The Persistent Volume Claim (PVC) cannot be bound to Persistent Volume (PV) once it is deployed, deleted and then deployed and Helm Chart is stuck in a pending state. Persistent Volume should be released after deleting the deployment of the Helm Chart to bind to the PV without issue when the chart is re-deployed.

When deploying MongoDB container onto Azure Stack Edge with Persistent Storage, the Persistent Volume Claim (PVC) cannot be bound to Persistent Volume due to incompatibility with POSIX-compatible storage. Add the ability to deploy MongoDB with a persistent storage on Azure Stack Edge.

A small but very useful feature in the classic release pipeline of the Azure DevOps is the rectangular marker to indicate which deployment is currently active in a particular stage. This is gone with the introduction of multi-stage pipelines. Can we have this back?

It would be great if we could enable boot diagnostics right at creation of AKS and AKS node pools. Right now it seems only be possible after creation of scalesets. So we have first to create AKS and then manually enable boot diagnostics.

Should required a elaborated session

we are aware that if the NTP is not reachable, the system will run with the last synced date, but we would love to configure a fallback address in case of not availability of our primary NTP.

Currently any published gallery items are seen publicly and must be created by cloud operators.

We would like to have these following features added:

1- Ability to create private gallery items for our customers (tenants) and share them as necessary.

2- Ability for customers to publish their own gallery items and share them as necessary.

I had a working build of 1811 and redeployed 1901 twice with fails of both. I'd like to be able to download the 1811 build to get server working again.

Once Excel Deployment Worksheet retires, we only use powershell deployment worksheet. I want to save "Subnet Summary" and "IP address Usage" information as a CSV or Excel file to review easily.
If powershell worksheet has export function as CSV or Excel format, we can share IP Subnet information easily.

At this point updating an Integrated Stack is very cumbersome. It takes days to finish updating the stack. It adds to the woes that we cant skip an update to jump to the most current update level. We should consider being able to skip and install the most recent update. Stack anyways wipes and reloads the complete infra layer. It is more difficult to understand why this is not possible.

We ran through this process and Microsoft and the partner did a great job in estimating and validate the business case. Eventually we decided otherwise, but the process is stable and solid.

Filtered access in Marketplace:

In a multi-tenancy environment, it would be great to control which Marketplace items each tenant can use. This could be used to tier customers or tier 2 providers based on contract level.

Example: add Marketplace items only for designated images supported for a certain customer in a managed services contract.

When Azure site recovery is enabled to replicate VMs from Azurestack to Azure, and the VMs are failed iver to azure. it's impossible to failback to Azure Stack. It wil be great to have this feature

Azure Stack is a great concept but is still quite large for smaller environments. It would be great if a two-node minimum cluster was achievable for ROBO/manufacturing environments that require local infrastructure where something like IoT Edge does not fit.
Being able to have multiple smaller Azure Stacks centrally managed through a single pane of glass would be awesome.

To install Powershell for Azure Stack, PowerShell 5.0 is required.
Is it in plan to support v6?
See https://github.com/MicrosoftDocs/azure-docs/issues/11030

Support upgrade for ASDK.

It is just not realistic for developers to rebuild ASDK each time when there is a new build. Microsoft should allow the upgrade of ASDK just like the integrated system. It is just like SQL Developer edition vs Enterprise edition, all features and upgrade are supported in the same way, just Developer edition is for dev/test.

When we rebuild the ASDK for evaluation, not only do we have to re-deploy the ASDK, but also re-build all POC scenarios as well, it could be weeks of effort.