HTTP 403 when publishing NuGet package to VSTS Package Management

For one of our customers I am setting up CI builds that automatically publish NuGet packages to their private feed in VSTS Package Management (https://www.visualstudio.com/en-us/docs/package/overview). They are in the process of splitting up their monolithic Web Application into pieces and this is one of the steps we are taking.

Migrating a VSTS instance from MSA’s to AAD accounts

To setup a VSTS (Visual Studio Team Services) account initially is very easy. The default user directory that is behind VSTS is a directory based on Microsoft Accounts (MSA). Quite some companies start by using MSA’s to access their VSTS instance and then decide to make the move to Azure Active Directory (AAD) once relevant data is already stored, but then face some issues.

Web application not updated after deployment with PowerShell DSC

At a customer I’m implementing automated deployment for one of their web applications. We’re using a PowerShell DSC script that is kicked off by Release Management (which is part of Microsoft Team Foundation Server). Part of that script is a “File” resource which takes care of actually deploying the new files.

Custom VSTS Build Task doesn’t show up

When implementing a custom VSTS (or TFS) Build Task, it didn’t show up in the list of tasks after publish and install. Nor for Build, neither for Release. So I verified several options;