Inquery About BYOC -Azure
Hi Team,
I wanted to follow up on the discussion around setting up a BYOC (Bring Your Own Cloud) environment in Azure. We're exploring this option primarily to optimize and reduce costs. Before proceeding, we would like your input—based on the current setup and usage trends, do you believe migrating to Azure could result in meaningful cost savings?
Additionally, I’ve observed that there is little to no usage outside of working hours. To further optimize costs, I’d like to explore the possibility of implementing a mechanism to automatically shut down the server during non-business hours.
Looking forward to hearing your thoughts on this.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 14 May, 2025 04:39 PM
You can do BYOC on Azure, or AWS, or GCE in two ways: 1) have an "always running" VM with AppVeyor agent installed on it or 2) create new VM for every build, on demand, like AppVeyor itself does. In the first scenario you pay 24x7 for the VM (or turn it off/on by schedule) and builds are running in non-isolated mode, meaning they share the same environment with other builds. In the second scenario you pay only for the time VM was running during the build. Once the build is finished its VM is destroyed. This scenario though requires more efforts to setup as you need to build your own image (VHD, AMI, etc.).