Azure Pack
Do you have an idea or suggestion based on your experience with Azure Pack ? We would love to hear it! Please take a few minutes to submit your ideas about providing Azure technologies and services on-premises, or vote up an idea submitted by another customer. All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure Pack. Remember that this site is only for feature suggestions and ideas!
For further reading on Azure Pack, please see our TechNet Documentation and our Wiki (links to articles and blogs). If you have technical questions or need help with Azure Pack, please try our Discussion Forum.
Follow what’s happening from Microsoft in the Cloud:
@Azure, @MSCloud, @InTheCloudMSFT
The latest on Azure Pack:
#WAPack
-
43 votes
-
Manage AzurePack from VisualStudio Server Explorer (Like Azure)
To be able to manage individual services in Azure Pack via the Server Explorer in Visual Studio just as if it was like the public Azure solution.
37 votesHi! Thank you for your suggestion! Those of us on the feature team are reviewing how we could make this happen for you!
Stay tuned :)
Thanks.
Kylie Hurd
kyhu@microsoft.com -
Clarify error messages
Debugging Azure Pack services can be a huge pain because error messages are:
1: top level messages
2: global stack tracesIf errors are *more specific it would be easier to debug and would save me a lot of time on the azurepack forums
16 votesThis is very helpful feedback, we definitely want you to have as seamless experience as possible when using Azure Pack. Could you provide some examples of any error messages that were particularly cryptic or hard to debug for you?
-
Improve scaling of Azure Pack
Allow Azure pack to manage more resources across multiple datacenters. Having multiple Azure Pack deployments breaks the cloud paradigm.
7 votesThank you for the feedback! We hope to bring this functionality soon!
-
Simplify deployment of Azure pack into one unified deployment package
Deploying Azure Pack can be combersome using the current installation process. It requires multiple VMs or servers, SQL, pieces of Orchestrator, and so on. I recommend simplifying the deployment process of WAP.
6 votesThank you for this valuable feedback!
-
4 votes
Thank you for the suggestion; this would be a great feature and we are looking into it!
-
Friendly Logging in the WAP UI
Please update the UI for more friendly logging. Would be great to have the following: A more concise view, similar to Windows server event log UI with filters, etc. but within the WAP UI. A CSV(etc.) export function would be helpful (with filters applied of course). Holistic, segmented logging, i.e. see multiple components in the WAP logging UI, color-code the different component source providers and have the ability to set the refresh and filters. Maybe allowing an extension to write third-party log info into the UI from the application via system center or windows server nodes. As more IT Pros…
3 votesThanks for the feedback! We are working to improve how we log and present information to the user. These suggestions are helpful and we would like to hear more if you have them!
-
Provide load balancing information during installation/configuration
Provide load balancing information during installation/configuration
Currently, the only way to configure load balancing of components with an external load balancer in Azure Pack is to use Powershell only after WAP installation and configuration. It would be great to specify FQDNs and URI's during the config phase and would be even greater to be able to specify ports.
2 votesThank you for the suggestion. We will look into improving the configuration experience for WAP and adding these options.
- Don't see your idea?