This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Stop Azure Application Gateway via a schedule/policy to reduce costs when back-end pools are off line or shutdown.
Azure Application Gateways cannot be stopped/started via the Azure Web Portal, but they can be stopped or started using Azure CLI or Powershell. There is also a POST command API method to start/stop an Application Gateway that can be found in the Azure Resource Explorer.
We run many DevTest Lab workloads for our Quest Presales teams. In several labs we provide access to web applications via an Application Gateway. However, these environments/VMs typically only need to be running during the assigned user's normal business hours. So, the VMs for the backend pools are often turned off nights and weekends. But our Application Gateways remain running and costing us for each hour of run time.
We would like the ability to use the Turbonomic Parking Scheduler or some other method to schedule the Stop/Start commands so we can take these Application Gateways offline when not needed, and started at the appropriate time for the region timezone/business hours in question.
Do not place IBM confidential, company confidential, or personal information into any field.