Azure DevOps PowerShell Module - Part 1
If you are like me - at least in terms of lazyness - you automate the stuff that you face more than once. Recently, I came accross the reoccuring task of creating Azure DevOps projects with several teams over and over again.
This is the first post of many other posts to come and I would really appreciate some feedback!
Since I'm a PowerShell guy, I started writing a little Module for this and the first version is now online!
You can get it directly from the PowerShell Gallery:
Install
Install-Module -Name AzDOps
The new Azure PowerShell module uses the prefix 'Az' (Microsoft Docs link) for the cmdlets - the cmdlets for Azure DevOps use 'AzDo'.
Connect-AzDo
Disconnect-AzDo
Get-AzDoGitRepository
Get-AzDoProcesses
Get-AzDoProject
Get-AzDoProjectHistory
Get-AzDoProjectProperties
Get-AzDoSecurityNamespace
Get-AzDoTeam
New-AzDoGitRepository
New-AzDoProject
New-AzDoTeam
Remove-AzDoGitRepository
Remove-AzDoProject
Remove-AzDoTeam
Connect
To connect to your Azure DevOps organization, you have to create a personal access token first. Open this link and follow the instructions. Afterwards, you can save both, the token as well as the name of your Azure DevOps organization as a string to a variable - then you can connect:
$token = "token"
$organizationName = "orgName"
Connect-AzDo -PersonalAccessTokens $token -OrganizationName $organizationName
In the future, there will also be an interactive way to connect using Oauth2 - it's planned for the next releases. Right now, the connection is being established using basic authentication.
When you're connected, you can start using the cmdlets:
Get-AzDoProject
Get-AzDoTeam -ProjectId '<projectId>'
New-AzDoProject -Name 'ProjectOne'
Azure Arc and Defender for Endpoint Ports & URLs
During the onboarding / rollout of Defender for Endpoint and Azure Arc Agent, the network plays a significant role. Communication via the Internet is usually restricted by segmented networks and secured by firewalls and proxies. To prevent errors or communication problems, the required ports & URLs should be opened to ensure seamless onboarding and operational processes.
Azure Networking - Hub-Spoke with NVA and Azure Firewall
When you plan on using Azure-Firewall in your Network-Infrastructure, you have to keep some things in mind - especially when it comes to Routing. In this article, I go over a specific scenario that involves a Hub-Spoke VNet architecture, a VPN or Express Route, a Network Virtual Appliance, User Defined Routes and last but not least, the Azure Firewall.