Because of the constant nature of Microsoft renaming products and reorganising their alignment, I am making some changes to this repo in order to make it more survivable. Additionally, some other changes are being made to help make it more integrateable into people's apps and services.
- Break free of product family categorisation hierarchy and its conflicts (e.g. does Power BI sit under Power Platform, or Fabric, or both?)
- Make it easier for logos to be found by their alternate and former names
- Create consistent logo sizes
Each product folder will contain a metadata.md file, which will contain the following fields:
| Field | Description | Required |
|---|---|---|
| name | Current name | Yes |
| type | Product / Family / Feature | Yes |
| status | Active / Retired / Renamed | Yes |
| altnames | Alternative or former names, abbreviations | No |
| prodfamilies | Product family (or families) it is associated with | No |
This metadata will be used by the workflow to build the front-end experience for the www.mscloudlogos.com site.
name: Viva Engage
type: Product
status: Active
altnames: Engage
prodfamilies: Viva Suite
The altname for Viva Engage lists "Engage" as it is sometimes being referred to without the "Viva" prefix.
The prodfamilies listing only shows Viva Suite, but should possibly also show Microsoft 365 - as Viva Engage can exist without Viva Suite licensing. So, is it part of both families?
name: Yammer
type: Product
status: Renamed (TO: Viva Engage)
altnames:
prodfamilies:
The folder for Yammer would sit underneath the Viva Engage folder.
Nothing is listed uner prodfamilies as it is not an active product, so therefore not part of a product family (as opposed to its replacement Viva Engage, which is part of a product family).
name: Viva Suite
type: Family
status: Active
altnames:
prodfamilies:
name: Graph
type: Feature
status: Active
altnames: Office Graph
prodfamilies:
Microsoft Graph covers many services, so can exist without being associated with any product families.
name: Microsoft 365 Admin Center
type: Feature
status: Active
altnames: MAC
prodfamilies: Microsoft 365
Not a product, but has a logo, and is part of a product family.
All files and folders will have their spaces replaced with an underscore (or hyphen, I haven't decided yet) to help with consistency around file names.
All files and folders will be changed to lowercase, to ensure consistency.
All product, family, and feature folders will sit at the top level of the repo (well, most likely under a "Logos" folder). This will help reduce the chance that any links created by users will not break due to a product reorganisation
All folders will need to contain within them sub-folders that contain the year of the logo. "Old" and "new" are too subjective.
All products will need to have some consistency around their size, and whether they are padded. For example, some logos say they are 256x256, but are actually closer to 200x200 if you take away the padding. Whereas others are 256x256 with no padding. Some files have just "256" or "512" in their file name, others have "256x256" or "512x512" in their file name, and others don't have any dimensions in their file name.
These two are a big hot mess, because there are a bunch of folders and images which are features and not actual products. Both of these will need to be sorted out to have some consistency like the other product families.
- Azure product logo cleanup
- Dynamics 365 product logo cleanup
- Metadata files have been created for all products and families
- Azure
- Copilot (not M365)
- Dynamics 365
- Entra
- Fabric
- Microsoft 365
- Power Platform
- Viva
- Other
- Former products
- Spacing removed from all file & folder names (although, the choice of character might be revisited)
- Lower casing of all file & folder names
- Constency of image padding
- Constency of file naming (in relation to padding, dimensions)
- Flattening of folder hierarchy
- Rebuild of website to utilise new functionality and structure
If there's anything unclear in this, it's because I've spent waaaaay too many hours on it today and my wife is glaring at me now as I have to go and make the kids beds!