Microsoft Technologies and Products

Microsoft is a platform decision before it is a technology choice. Picking .NET, Azure, or the Microsoft 365 stack means accepting a release cadence, a support lifecycle, a certification ladder, and a procurement reality that all flow from one vendor. The articles in this collection focus on those structural decisions rather than on feature announcements, because the structural decisions are what determine whether a team is comfortable on the platform three years later.

Release cadence is the most visible piece. .NET ships an LTS in even-numbered years and an STS in odd-numbered years, and Microsoft recently moved STS support from eighteen to twenty-four months — a change that sounds generous until you map it against actual upgrade cycles in enterprise software. For most organisations the right answer is still LTS-only, with STS reserved for greenfield work where the upgrade cost is low and the new APIs are worth it. The collection covers how to make that decision with numbers instead of vibes.

Certification is the other practical lever. Microsoft Learn, the role-based certification tracks, and the renewal model are designed to be self-service, but the assessment UI, the question formats, and the renewal cadence each have quirks that catch first-timers. The articles here are about preparing efficiently, choosing exams that reflect work the person actually does, and treating certifications as evidence rather than as a goal.

Beyond those, the collection touches the business decisions that affect .NET teams whether or not they care about them: Microsoft’s pricing model changes, partner-programme requirements, the constant rebranding of services that arrive every twelve months under a new name, and the support-contract maths that decide whether a Premier ticket is worth opening. Working on Microsoft technology is a relationship with Microsoft, not just a stack choice, and the articles here treat it that way.