Cloud Computing|Windows Client OS

Microsoft's Subtle Branding Changes to its Core Products

If you jumped in a time machine and went back about five years, at any Microsoft conference, you would hear the words Windows and Azure in every other sentence. But today, those words are used less often because of how Microsoft has quietly, and not so quietly, been changing the organizational chart of the company and restructuring some of its core assets.

The evolution of Microsoft’s sub-brands has been subtle but necessary as the market has changed and so has the direction of the company. That being said, the company is now placing its own name first, rather than its products for two of its foundational services.

Microsoft no longer promotes Windows directly, instead they talk about Microsoft 365. This became apparent at Build 2018 and flavors of this change showed up last year at Build 2017, but now the company is all in on Microsoft 365 instead of Windows.

Sponsored Content

Devolutions Remote Desktop Manager

Devolutions RDM centralizes all remote connections on a single platform that is securely shared between users and across the entire team. With support for hundreds of integrated technologies — including multiple protocols and VPNs — along with built-in enterprise-grade password management tools, global and granular-level access controls, and robust mobile apps to complement desktop clients.

Why? Windows has stagnated, it has reached its peak and is now in maintenance mode for Microsoft. Sure, they will continue to update it and add new features, but from a growth perspective, it comes up short when compared to other services offered by Microsoft.

Windows still has a massive user-base which the company hopes to use to leverage other services like Office 365. And because Office 365 is the company’s premier SaaS offering, creating Microsoft 365 which includes both Windows and Office (and a few other services), this helps to introduce users of these platforms to the entire suite of services offered by the company.

The other ‘re-branding’, if you will, is that Microsoft has subtly changed in the past year or so is how it refers to its cloud. Previously, the ‘cloud’ was referred to as Azure but now the company simply calls it Microsoft Cloud with Azure being a component of the larger offering.

The Microsoft Cloud branding makes sense when you look at how the company positions its cloud services. Azure is the development side of the ‘cloud’ but there are also other products that the company bundles in this area too, such as Office 365 and Dynamics 365.

But the notable thing here is that the company is now attaching it’s corporate branding to its products rather than trying to create new names under its umbrella.

It’s a strategy that makes sense and also lets the company leverage the easily recognizable name of Microsoft. Even though ‘Azure’ is well known in the developer community, the C-suite may not recognize that name but they surely know the Microsoft mark.


Don't have a login but want to join the conversation? Sign up for a Petri Account

Comments (0)

Leave a Reply

Brad Sams has more than a decade of writing and publishing experience under his belt including helping to establish new and seasoned publications From breaking news about upcoming Microsoft products to telling the story of how a billion dollar brand was birthed in his book, Beneath a Surface, Brad is a well-rounded journalist who has established himself as a trusted name in the industry.
The World’s Most Comprehensive Teams to Teams Migration Checklist

Whether you have just started thinking about migration or have already begun to move, our Microsoft Teams Migration Checklist can help guide you through the different phases for a Teams migration to another tenant.

This detailed six-step guide will walk you through key decision points while also providing more prescriptive best practice recommendations where appropriate.

Discover key insights for the following phases of a Teams migration: 

  • Discovery
  • Pilot
  • Planning
  • Communication
  • Execution
  • Validation

Sponsored by: