I am not suggesting that all the technology of managed disks should be possible on Stack although this would clearly be useful. I think that, at the very least, Azure Stack should be able to deal with the managed disks schema in ARM templates without erroring thereby allowing for templates to be deployable seamlessly between Stack and Azure.22 votes
We are investigating adding Managed Disks to Azure Stack.
As of currently, 9/01/2019, one cannot use Microsoft Bot Framework in a docker environment or Azure Stack environment. This means that even though LUIS is has the ability to be deployed in a docker container a major associated use case, Microsoft Bot Framework w/ direct line api, is not available to use on-premise in a fully dockerized solution.
A service, such as the MBF, would be vitally important to have the ability to have low latency and high throughput to match with the other cognitive services in which it would use.6 votes
The Azure Stack Kubernetes Template should be current in Versions of Kubernetes with Azure, and should at least support 1.12.4.
karsten@Azure:~$ az aks get-versions --location eastus --output table
1.12.4 None available
1.11.5 1.11.6, 1.12.4
1.10.12 1.11.5, 1.11.6
1.10.9 1.10.12, 1.11.5, 1.11.64 votes
I would like to be able to report on the web hook functionality in Azure DevOps (i.e. when a webhook has changed to a disabled state or when errors are encountered while data is being processed)3 votes
I would like to monitor the usage metrics per node with the monitoring system for checking whether a node runs normally. But Get-AzsScaleUnitNode.Properties only returns capacity not usage. and Get-AzsLocationCapacity.UsageMetrics only returns total capacity and total usage
I would be happy if Get-AzsScaleUnitNode.Properties returns not only the capacity but also the usage.3 votes
Right now I use Terraform to create an entire stack within a Resource Group. With Azure Stack there doesn't seem to be a way to use an API or another automated method to create the customer accounts in Azure Stack. Right now I'd have to manually create the customer's account and subscription and create a service user in AD to be able to have an access key, client id, subscription id, etc to be able to automatically create infrastructure within that customer's space.2 votes
Just like we have policy center in Azure public, it would be nice to have it on azure stack for governance purposes1 vote
Posted on behalf of TheOnlyWei (https://github.com/MicrosoftDocs/azure-docs-powershell/issues/1424).
Error messages from ARM are not always user-friendly and there is room for improvement here that would enhance the customer experience as well as decrease troubleshooting difficulty.
Example screenshot attached.
Get-AzsAzureBridgeActivation returns "The resource namespace 'Microsoft.AzureBridge.Admin' is invalid.", which in this case is caused by not being in the "Default Provider Subscription" however this is not made clear to the user.1 vote
We would like to migrate a subscription to a different offer.1 vote
- Don't see your idea?