/explore
|
You are here 
|
www.ivobeerens.nl | ||
| | | | |
www.cloudninja.nu
Intro In the first blog post (here), I wrote the most basic Bicep code for deploying a host pool, application groups, and a workspace. The result will be the same resources in this part, but the code will be a bit more advanced, allowing us to customize the deployment. I will keep the code simple, and the goal is to make the part we change for each deployment as simple as possible, while the Bicep modules contain the more advanced code. |
|
| | | | | ||
| | | | |
www.rozemuller.com
All about Identity, AVD, Automation, DevOps, Monitoring, Intune and Security |
|
| | | | | ||
| | | | |
www.lucd.info
After we deployed our instances with the help of cloud-init, we want to use them to run our scripts. They are our 'cattle' after all. |
|
| | | | | ||
| | | | |
chrisreddington.com
A little while ago, I wrote a blog post on Using the GitHub self-hosted runner and Azure Virtual Machines to login with a System Assigned Managed Identity, which seems to get a good amount of views week on week. Reflecting on some questions that have popped up this week (and regularly received over my time in the DevOps space), I thought that it makes sense to write a post on how to use Azure DevOps self-hosted agents to deploy to private resources. So, that's what we'll be covering in this post! |
|
| | | |||
