Contents
  1. What this logo question is actually about
  2. What a before-and-after reading can establish
  3. Vector artwork, embedded rasters and previews
  4. How to read the redesign without inventing a visual score
  5. Download, modification and trademark use
  6. Practical implications for people preparing artwork

What this logo question is actually about

The subject is the product mark for Microsoft Dynamics 365 Business Central: the symbol and lockup used to identify that ERP offering in product screens, documentation, partner materials and brand kits. A request for the new logo is a request to identify the current official identity, not a generic business-software icon and not a third-party recreation of the word “Business Central.”

A before-and-after evaluation in this setting compares the earlier Dynamics NAV / Business Central identity with the current Dynamics 365 family mark. The practical question for vector-logo readers is whether the current artwork is true editable vector, how it behaves at small and large sizes, and what you are allowed to do with it once you have a file.

What a before-and-after reading can establish

This brief does not include official source files, export logs, brand-guide pages or measured artwork. No path counts, colour values, stroke weights, clear-space rules or file-format tests are reported here. Those details belong to Microsoft’s current brand and product-icon guidance and to whatever files you obtain from an authorised kit. The evaluation below is therefore a method for reading a redesign, not a certified audit of a specific download.

In product-family redesigns of this type, the change is usually from a standalone application badge toward a shared Dynamics 365 visual system: a simplified geometric symbol, a tighter relationship to the suite’s colour and grid, and a lockup that can sit next to other Dynamics 365 product marks. The older Business Central / NAV identity read more as a discrete application icon. The current mark is meant to be recognised as one product inside a suite. That is the design intent to test against, not a claim about any particular file on disk.

  • Confirm you are looking at the Business Central product mark, not the Dynamics 365 suite logo, not the Microsoft corporate logo, and not a partner or independent-software-vendor badge.
  • Treat “new” as the currently published official identity. A file labelled new is not automatically current, and a current raster preview is not automatically vector artwork.
  • Compare like with like: symbol-only versus symbol-plus-wordmark, on-light versus on-dark, and UI glyph versus print lockup. Mixing those variants produces a false before-and-after.
  • Judge the redesign on recognition at small sizes, colour-system fit with other Dynamics 365 marks, and whether the artwork is constructed as paths rather than a placed bitmap.

Vector artwork, embedded rasters and previews

A logo file can look sharp on screen and still fail as vector artwork. True vector artwork is made of paths, anchors and fills (or equivalent live geometry) that scale without new pixels. A PNG, JPEG or screen capture of the Business Central mark is a raster image. An SVG, PDF or EPS container can hold either live paths or an embedded bitmap that only looks like a logo. The container name does not prove the contents are editable paths.

When you open a candidate file, check whether the mark selects as geometry you can outline, recolour and resize, or as a single placed image. A raster preview is useful for recognition and for checking the redesign’s silhouette. It is not a substitute for production artwork. If the only available “new logo” is a UI screenshot or a flattened icon from an app store listing, you still do not have vector artwork.

What you haveWhat it is good forWhat it does not prove
Official SVG, PDF or EPS with live pathsProduction lockups, colour changes, large-format and printThat you may modify or rebrand the mark
SVG or PDF that only embeds a PNG or JPEGOn-screen preview at the embedded resolutionEditability, clean scaling, or true vector delivery
App icon, favicon or marketing screenshotRecognising the current identityThat the file is the master artwork
Filename ending in .svg, .ai or .epsA hint about intended formatThat the artwork inside is paths rather than a raster

How to read the redesign without inventing a visual score

A measured before-and-after would place the retired mark and the current mark on the same grid, at the same optical size, in the same colour mode, and would record differences in geometry, palette and lockup. That comparison is not possible from this brief. What you can still do, once you have authorised files, is walk the same checklist on both versions.

  • Silhouette: does the current symbol remain identifiable when reduced to a favicon or a navigation glyph, and did the older mark fail or succeed at the same size?
  • Construction: are fills closed, are alignments on a consistent grid, and are there stray raster layers sitting under the paths?
  • Colour: is the mark built from the current product-family palette with defined one-colour and reversed versions, or only from a full-colour screen rendering?
  • Lockup: is the wordmark a live, specified type treatment or an outlined custom drawing, and is the gap between symbol and type specified?
  • Family fit: does the current Business Central mark sit on the same optical weight and corner language as neighbouring Dynamics 365 product marks?

Editorial judgment, not a lab result: suite-aligned product marks usually trade distinctive, application-specific ornament for consistency. If the current Business Central identity looks simpler and closer to other Dynamics 365 product icons than the earlier NAV-era badge, that is the expected direction of a family redesign. Whether that is an improvement depends on the use: in-product UI and partner decks gain consistency; a standalone print masthead may lose the older mark’s separate character. That trade-off is a use-case choice, not a score.

Download, modification and trademark use

Permission to obtain a logo file is separate from permission to redraw it, recolour it, combine it with other marks, or use it to imply partnership, certification or origin. Microsoft’s product names and logos are trademarks. A brand-centre download, a documentation image or a press rendering can be offered for accurate identification and for uses the rights holder lists. That offer does not, by itself, grant a right to alter the artwork, substitute fonts, or place the mark on merchandise or a competing product.

If you need the mark for a partner listing, an implementation guide, training material or a slide master, use the official lockup in the form the rights holder specifies, at a size that keeps the symbol intact, with required clear space and on an approved background. If you need a modified colourway, a combined logo or a custom wordmark, that is a brand-use question, not a file-format question. Vector editability in the file does not equal a licence to edit.

Practical implications for people preparing artwork

For production work, start from the authorised current Business Central mark in a format that contains live paths, keep a raster preview only as a visual check, and keep the Microsoft corporate logo and the Dynamics 365 suite logo on separate layers or in separate files so they are never swapped by accident. Do not rebuild the symbol from a screenshot. Do not treat an icon font glyph, a Teams app tile or a flattened PDF page as the master. If a supplier sends a file whose paths cannot be selected, request the vector master rather than tracing the preview.

Gaps that remain until you inspect official files: the exact path structure of the current mark; whether published SVGs are outlined or live; the specified colour values and minimum sizes; and the formal before-and-after geometry of the redesign. Those are documented in the rights holder’s current brand and product-icon materials, not in this assessment.