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 votes
Hi! Thank you for your suggestion! Those of us on the feature team are reviewing how we could make this happen for you!
Stay tuned :)
At present it only seems possible to schedule 'one time' or 'daily' for the frequency for runbooks.
Proposal : Add options for hours and minutes
Justifcation : (1) Many of our scripts need to run on a more frequent basis, such as scanning ftp file drop locations for new files and processing them accordingly. The limitation of this at the moment restricts our ability to use these.
(2) Dependancy on Orchestrator restricts full migration to SMA, adds additional development time and testing.
Current workaround : Make an Orchestrator runbook with a timer which calls the SMA runbook(s).37 votes
Just to confirm, you are looking for two additional frequencies: hour and minute. Our team can look into this.
Yes – you can have a monitor/long running runbook that triggers other runbooks on a timer as a workaround for the moment.
Include other languages, such as PT-PT, or document a way to extend the base product with other translations.35 votes
Thank you for the feedback. We will look into this.
Allow me to put a worker into 'maintenance mode’
Drain off all running jobs. If job type is workflow stop at the next checkpoint instead of running until drain time is reached and ‘hard’ stopping
Update the load balancing algorithm to incorporate a heartbeat idea. If a worker is not online don't put new jobs into its partition of the jobs table35 votes
Thanks for the feedback! Having this functionality would definitely help in the case a worker goes down or needs to be restarted. We will take this into consideration.
When a job suspends allow us to see and update all values of the variables in the script at the last checkpoint before resuming34 votes
Support hiding by configuration of sections such as:
a) My account
b) VM Function role
This is important when developing generic hosting services on the internet.30 votes
Thank you for the suggestion. We are unable to accommodate this in Azure Pack, but similar functionality is being investigated for Azure Stack.
It would be nice to be able to assign AD Users and or Groups to Plans in Azure Pack. Instead of just limiting access to the whole portal via a STS provider. That way we could re-use the same portal for various solutions internally, by utilizing Plans that are locked down to a certain subset of users in the organization.28 votes
We are looking into providing similar functionality. Thank you for the suggestion.
When an SMA runbook is edited there is no inbox possibility to revert to the previous version or select an older version. Combining this with approval will also prevent unwanted changes. This also fits in with RBAC.27 votes
We will look into this. Thanks for the feedback!
We need a way to allow our customers to import a database dump (.bak file) through the Windows Azure Pack portal.26 votes
Thanks for the suggestion and we are looking into this.
It would be good if DiscoverAllLocalModules would keep hash information about modules so when it goes through the discovery it would not need to process all the modules, that would increase speed exponentially, if the hash of the module has change then the DiscoverAllLocalModules would know that the module has been updated.24 votes
Thanks for the feedback! We can look into this.
The Windows Azure Pack Tenant Portal allows you to display Diagnostic information by pressing ALT + CTRL + A
It would be great to add the current user claims (UPN & Group Claims) to that screen.24 votes
Thank you for this idea. We are investigating.
For remote endpoints22 votes
Thank you, we will look into this.
Today SMA runbooks can be triggered when an "action" is taken. However there is no (synchronous) way to prevent the action to take place or to "modify" the parameters for the action. Examples where this would be helpful: Runbook that puts VM in maintenance mode for SCOM when tenant does shutdown from portal. Runbook that fetches a new computer name from custom database an injects into create VM action. Today these actions need to be done "after the fact" as a cleanup task (e.g. rename the server)16 votes
Thanks for the feedback! This is something that we have thought about and need to do some further investigating to figure out how it can be done.
Debugging Azure Pack services can be a huge pain because error messages are:
1: top level messages
2: global stack traces
If errors are *more specific it would be easier to debug and would save me a lot of time on the azurepack forums16 votes
This 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?
If tenant resources are spread across multiple datacenters, there should be a choice of datacenter as a unit of organization.15 votes
Thank you for your feedback! We too would love to bring this Azure-consistent functionality on-premise.
Ex: if the payment is overdue, user should not be allow to add more vm's, create new websites, etc. There is an API to do this for subscriptions, but it is not enough.15 votes
Thank you for the feedback. You are correct, you can now only do this via subscription changes (i.e. add-ons) but we will look into supporting this at the resource creation level.
Can you tell us more about the scenario you are trying to enable?
Setting up remote Management (e.g. console or remote Desktop Connection) for tenant portals is very tricky at the moment.
Struggling selving errors, weak documentation (explanations), setting up is not straight forward, so please provide detailed installation instruction.14 votes
Add support to add load balance between VM's like in public Azure (via trafic manager or VM load balancing feature)14 votes
Provision VMs without a template - point to sccm or pxe service or even ISO build to give flexiblity to provisioning.
Templates are great when you have a limited number, but can get cumbersome in large environments. Allow vm and os provisioning via other methods such as pxe, sccm, iso, etc to help streamline template management. - especially useful when trying to leverage dsc/puppet/chef for management.13 votes
- Don't see your idea?